owner: gmikcon status: active last_reviewed: 2026-09-21 review_interval: 90d confidence: high
Internal proxy VPS that receives traffic from the external VPS through OpenVPN and forwards it to internal services.
internal-proxy-vps.ovpn_reserv.hp-proliant-dl380-g6.5.4.0-216-generic.nginx/1.18.0.192.168.1.226.192.168.105.181/24.gnexus.space traffic.nginx.serviceopenvpn@client.servicenavi.service (Navi server, agent system API)ssh.servicenavi.service (systemd, Type=simple, user ubuntu, enabled)./etc/systemd/system/navi.service./home/ubuntu/navi-1./home/ubuntu/navi-1/.venv/bin/navi-server.8099 (uvicorn, 0.0.0.0:8099).http://127.0.0.1:8099/health./home/ubuntu/navi-1/.env (contains OLLAMA_API_KEY, OLLAMA_HOST=https://ollama.com, embedding settings; no raw key values documented here).ollama_backends.json file exists in the working directory.22804438099 (navi.service)The nginx proxy handles the gnexus.space domain family.
Enabled nginx sites (verified 2026-09-21):
auth.gnexus.spacebugtrail.gnexus.spacecloud.gnexus.spacecreds.gnexus.spacefiles.gnexus.spacefuckjira.gnexus.spacegit.gnexus.spacegnexus.spacejellyfin.gnexus.spacenavi.gnexus.spacetasks.gnexus.spacetranscribe-demo.gnexus.spacetransmission.gnexus.spacevmk-marginator.gnexus.spaceAvailable nginx site files that are not currently confirmed as enabled:
anicusi.gnexus.spacecats.gnexus.spacefdroid.gnexus.spaceferumina.gnexus.spacelytvak.gnexus.spacemail.gnexus.spaceminecraft.gnexus.spaceollama.gnexus.spacesups.gnexus.spacetopics.gnexus.space| Domain | Upstream |
|---|---|
auth.gnexus.space |
http://192.168.1.167 |
bugtrail.gnexus.space |
http://192.168.1.177:80 |
cloud.gnexus.space |
http://192.168.1.152 |
creds.gnexus.space |
http://192.168.1.173 |
files.gnexus.space |
http://192.168.1.157 |
fuckjira.gnexus.space |
http://192.168.1.175:8080 |
git.gnexus.space |
http://192.168.1.156 |
gnexus.space |
http://192.168.1.151 |
jellyfin.gnexus.space |
http://192.168.1.153:8096 |
navi.gnexus.space |
http://192.168.1.168:8000 |
tasks.gnexus.space |
http://192.168.1.179:8135 |
transcribe-demo.gnexus.space |
http://192.168.1.75:5173 |
transmission.gnexus.space |
http://192.168.1.154:3000 |
vmk-marginator.gnexus.space |
http://192.168.1.178:8080 |
Known available but not confirmed enabled mappings:
| Domain | Upstream |
|---|---|
lytvak.gnexus.space |
http://192.168.1.167 |
minecraft.gnexus.space |
tcp://192.168.1.218:25565 |
Proxying is mixed by hostname, path, and ports. SSH forwarding to the internal alex VPS on a custom port is believed to exist and still needs confirmation from nginx or firewall configuration.
bugtrail.gnexus.space issued 2026-09-18 (nginx authenticator, http-01). Files: /etc/letsencrypt/live/bugtrail.gnexus.space/fullchain.pem and privkey.pem, valid until 2026-12-17, CN=bugtrail.gnexus.space, issuer Let's Encrypt (YR2).bugtrail.gnexus.space nginx site has both an HTTP :80 block (no redirect) and an HTTPS :443 block using the dedicated certificate, both proxying to http://192.168.1.177:80 with standard proxy headers.tasks.gnexus.space issued 2026-09-21 (nginx authenticator, http-01). Files: /etc/letsencrypt/live/tasks.gnexus.space/fullchain.pem and privkey.pem, valid until 2026-12-20. Site tasks.gnexus.space proxies to http://192.168.1.179:8135 (gntodo stack): :80 block (no redirect) + :443 block with the dedicated certificate, client_max_body_size 12m, proxy_set_header Host $host (required — /mcp Host check), X-Forwarded-Proto https, and proxy_buffering off + proxy_read_timeout 300s on /api/ and /mcp/ (SSE). Site created by the Proxy navi instance, :443 block completed by rei (2026-09-21).gnexus.space multi-SAN certificate (10 SANs, unchanged by this work).No raw credentials are documented here.