Newer
Older
gnexus-book / 10-systems / servers / internal-proxy-vps.md

owner: gmikcon status: active last_reviewed: 2026-10-08 review_interval: 90d confidence: high

source_of_truth: ssh-host-verified

Internal Proxy VPS

Internal proxy VPS that receives traffic from the external VPS through OpenVPN and forwards it to internal services.

Identity

  • Inventory id: internal-proxy-vps.
  • VM id: ovpn_reserv.
  • Hypervisor: hp-proliant-dl380-g6.
  • OS: Ubuntu 20.04.6 LTS.
  • Kernel: 5.4.0-216-generic.
  • nginx: nginx/1.18.0.
  • GHard panel id: 33 (server name internal-proxy).

Addresses

  • LAN address: 192.168.1.226.
  • Libvirt/internal address: 192.168.105.181/24.

Roles

  • OpenVPN client.
  • Internal nginx reverse proxy.
  • Main internal entrypoint for public gnexus.space traffic.
  • Host of the navi Proxy instance (port 8099).

Active Services

  • nginx.service
  • openvpn@client.service
  • navi.service (Navi server, agent system API)
  • ssh.service
  • Service: navi.service (systemd, Type=simple, user ubuntu, enabled).
  • Unit file: /etc/systemd/system/navi.service.
  • Working directory: /home/ubuntu/navi-1.
  • ExecStart: /home/ubuntu/navi-1/.venv/bin/navi-server.
  • Listening port: 8099 (uvicorn, 0.0.0.0:8099).
  • Health endpoint: http://127.0.0.1:8099/health.
  • Configuration: /home/ubuntu/navi-1/.env (contains OLLAMA_API_KEY, OLLAMA_HOST=https://ollama.com, embedding settings; no raw key values documented here).
  • No ollama_backends.json file exists in the working directory.
  • Container: navi-postgres, image pgvector/pgvector:pg16 (Postgres 16 + pgvector).
  • Compose project: deploy, file /home/ubuntu/navi-1/deploy/docker-compose.yml, service postgres (container_name: navi-postgres, image: pgvector/pgvector:pg16).
  • Container created 2026-09-09T17:42:17Z; recreated 2026-10-08T11:25 UTC (GHard panel events: container_removed 11:25:00Z → container_added 11:25:20Z, same image pgvector/pgvector:pg16); healthy after restart.
  • Only postgres container and only postgres-family image (pgvector/pgvector:pg16, id 9b05db12a354) on this host — no legacy plain postgres image present; the pgvector image was already in use before the 2026-10-08 recreate.
  • Docker restart policy поднял контейнер после ребута хоста: removed 11:25:00 → added 11:25:20, healthy с 11:25:01, volume цел, restarts=0.
  • SSH access: user ubuntu (root login denied), docker requires sudo (password in gnexus-creds, secret internal-proxy-vps-creds).
  • Verified via SSH 2026-10-08.

Host Reboot 2026-10-08 (navi rei)

  • Причина recreate контейнера: полная перезагрузка VM. Чистый shutdown по ACPI power-key 11:24:20 UTC (journalctl -b -1: Power key pressed + штатная Power-Off последовательность; last -x: shutdown system down Thu Oct 8 11:24), boot 11:24:50 UTC. Краш/OOM/питание/unattended-upgrades исключены.
  • Восстановление проверено: navi.service active, health 200 (embed 401 при старте — хроническое, см. ниже); nginx-путь снаружи — auth/synapse/tasks/hpanel/bugtrail/creds все 200 (11:34 UTC); панель services_overview 6/6 up.
  • Побочные наблюдения (не инцидент): (1) embed_unavailable (401) при каждом старте navi-server — хроническое (10/16/23 сен, 8 окт). (2) После ребута возобновился цикл disconnect/reconnect MCP navi-3d/navi-web (30 за 5 мин; после бута 23 сен такой цикл шёл до 26 сен, ~22.4k disconnect'ов, сам прекратился). Конфиги mcp_servers.d не менялись с 2026-09-09; navi-3d/navi-web указывают на несуществующий путь /home/gmikcon/Projects/navi-1/... (Errno 2), navi_ui — на localhost:8001 (не слушается).
  • Открытый вопрос: инициатор ACPI power-key на гипервизоре bserv (virsh/Cockpit/сессия владельца) не установлен — gntodo задача 455.

Listening TCP Ports

  • 22
  • 80
  • 443
  • 8099 (navi.service)

Proxy Scope

The nginx proxy handles the gnexus.space domain family.

Enabled nginx sites (verified 2026-10-05):

  • auth.gnexus.space
  • bugtrail.gnexus.space
  • cloud.gnexus.space
  • creds.gnexus.space
  • files.gnexus.space
  • fuckjira.gnexus.space
  • git.gnexus.space
  • gnexus.space
  • hpanel.gnexus.space
  • jellyfin.gnexus.space
  • navi.gnexus.space
  • synapse.gnexus.space
  • tasks.gnexus.space
  • tgclientmcp.gnexus.space
  • transcribe-demo.gnexus.space
  • transmission.gnexus.space
  • vmk-marginator.gnexus.space

Available nginx site files that are not currently confirmed as enabled:

  • anicusi.gnexus.space
  • cats.gnexus.space
  • fdroid.gnexus.space
  • ferumina.gnexus.space
  • lytvak.gnexus.space
  • mail.gnexus.space
  • minecraft.gnexus.space
  • ollama.gnexus.space
  • sups.gnexus.space
  • topics.gnexus.space

Confirmed Proxy Mappings

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
hpanel.gnexus.space http://192.168.1.176:8000
jellyfin.gnexus.space http://192.168.1.153:8096
navi.gnexus.space http://192.168.1.168:8000
synapse.gnexus.space http://192.168.1.172:8013
tasks.gnexus.space http://192.168.1.179:8135
tgclientmcp.gnexus.space http://192.168.1.171:8710
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.

TLS Certificates (certbot)

  • Separate certbot certificate for 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).
  • Separate certbot certificate for 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).
  • Separate certbot certificate for tgclientmcp.gnexus.space issued 2026-10-05 (nginx authenticator, http-01, by navi rei). Files: /etc/letsencrypt/live/tgclientmcp.gnexus.space/fullchain.pem and privkey.pem, valid until 2027-01-03. Site tgclientmcp.gnexus.space proxies to http://192.168.1.171:8710 (tgclient-mcp): :80 block (no redirect) + :443 block with the dedicated certificate, client_max_body_size 32m (media 20 MB + base64 overhead), proxy_set_header Host $host, X-Forwarded-Proto https, and proxy_buffering off + proxy_read_timeout 300s on /mcp-protocol/ (MCP streamable HTTP). Deploy note: first certbot run glued the :443 directives into the :80 server block — the site was rewritten into two clean blocks (tasks.gnexus.space style).
  • Other sites use the shared gnexus.space multi-SAN certificate (10 SANs, unchanged by this work).

No raw credentials are documented here.