owner: gmikcon status: active last_reviewed: 2026-09-16 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:
git.gnexus.spacejellyfin.gnexus.spaceauth.gnexus.spacecloud.gnexus.spacefiles.gnexus.spacegnexus.spacenavi.gnexus.spacetransmission.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 |
cloud.gnexus.space |
http://192.168.1.152 |
files.gnexus.space |
http://192.168.1.157 |
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 |
transmission.gnexus.space |
http://192.168.1.154:3000 |
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.
No raw credentials are documented here.