diff --git a/10-systems/traffic-routes/public-gnexus-space-to-internal-nginx.md b/10-systems/traffic-routes/public-gnexus-space-to-internal-nginx.md index 7d66755..9a759fb 100644 --- a/10-systems/traffic-routes/public-gnexus-space-to-internal-nginx.md +++ b/10-systems/traffic-routes/public-gnexus-space-to-internal-nginx.md @@ -57,8 +57,8 @@ ## Known Hosts -- External VPS: `external-vps`, s-host.com.ua, Ukraine, Ubuntu Server 22.04. -- Internal proxy VPS: `internal-proxy-vps`, VM `ovpn_reserv`, LAN address `192.168.1.226`, libvirt address `192.168.105.181/24`. +- External VPS: `external-vps` (public IP `51.83.131.93`, OVH, France — DNS target of `*.gnexus.space`). +- Internal proxy VPS: `internal-proxy-vps`, VM `ovpn_reserv`, LAN address `192.168.1.183` (static via netplan inside the guest; was `192.168.1.226` until the 2026-10-16/17 blackout — `.226` no longer responds, see `10-systems/servers/internal-proxy-vps.md`), libvirt address `192.168.105.181/24`. ## Confirmed Enabled Proxy Targets @@ -91,7 +91,7 @@ ## Verification Notes -- 2026-10-04 (navi rei): the external VPS catch-all forwards unknown `*.gnexus.space` subdomains to the internal proxy — verified by fetching a probe file from the default site of `.226` through `http://synapse.gnexus.space`. HTTP-01 challenges therefore reach certbot on `.226` (LE certificate issued for `synapse.gnexus.space` the same day). nginx site configs live in `/etc/nginx/sites-available/` on `internal-proxy-vps` (root access required). +- 2026-10-04 (navi rei): the external VPS catch-all forwards unknown `*.gnexus.space` subdomains to the internal proxy — verified by fetching a probe file from the default site of `.226` through `http://synapse.gnexus.space`. HTTP-01 challenges therefore reach certbot on `.226` (LE certificate issued for `synapse.gnexus.space` the same day). nginx site configs live in `/etc/nginx/sites-available/` on `internal-proxy-vps` (root access required). Address note (2026-11-08, navi Eris): the internal proxy then lived on `.226`; since 2026-10-17 it is on `.183` — historical mentions of `.226` in older notes refer to that era. - 2026-10-04 (navi rei): added `hpanel.gnexus.space` → `http://192.168.1.176:8000` (GHard Monitor panel). nginx site on `internal-proxy-vps`: port 80 → 301 to https, port 443 → TLS proxy with `Host`/`X-Real-IP`/`X-Forwarded-For`/`X-Forwarded-Proto`, `proxy_buffering off`, `proxy_read_timeout 300s`, `proxy_http_version 1.1`. LE certificate issued via `certbot --nginx` (valid until 2027-01-02). The `/mcp` location is blocked at the proxy (403): the panel has no auth yet (GHARD_AUTH_* unset, admin token empty), so the MCP endpoint must not be public. Verified externally: DNS → 51.83.131.93, health `{"status":"ok"}`, UI 200 over HTTP/2, HTTP→HTTPS 301. - 2026-10-25 (navi rei): Minecraft public path verified end-to-end. MC status ping via `minecraft.gnexus.space:25565` and `51.83.131.93:25565` returned MOTD `A Minecraft Server`, version 26.2 (proto 776), 0/40 players; TCP connect from 3 external check-host.net nodes (BR/MD/RU) OK. Internal chain: ovpn VM (192.168.1.150) nft DNAT (tun0 tcp 80/443/25565 → 192.168.1.183, SNAT to 192.168.1.150; counters ~2.85M packets) → nginx stream on .183 (listen 25565 → 192.168.1.160:25565). Legacy leftovers left in place: disabled `sites-available/minecraft.gnexus.space` on .183 (stale .218 upstream), redundant socat `minecraft-tcp-forward.service` on the ovpn VM (→ 192.168.68.218:25565, mine's second NIC; receives no tun0 traffic — PREROUTING DNAT intercepts first). diff --git a/90-maintenance/pending-changes/20261108182931-5c546b06.json b/90-maintenance/pending-changes/20261108182931-5c546b06.json new file mode 100644 index 0000000..9c921e8 --- /dev/null +++ b/90-maintenance/pending-changes/20261108182931-5c546b06.json @@ -0,0 +1,19 @@ +{ + "id": "20261108182931-5c546b06", + "kind": "doc", + "target": "10-systems/traffic-routes/public-gnexus-space-to-internal-nginx.md", + "summary": "Fix stale internal proxy LAN address .226 → .183 in Known Hosts and add external VPS public IP", + "reason": "Cross-check against 10-systems/servers/internal-proxy-vps.md (ssh-verified 2026-10-25): after the 2026-10-16/17 blackout the internal proxy VM moved from DHCP .226 to netplan-static .183; .226 no longer responds. The Known Hosts line still said .226 — a wrong target for the planned pfSense Host Overrides (gntodo 456).", + "payload": { + "content": "---\nowner: gmikcon\nstatus: active\nlast_reviewed: 2026-10-25\nreview_interval: 90d\nconfidence: high\nsource_of_truth: owner-confirmed-and-live-verified\n---\n\n# Public gnexus.space Traffic To Internal nginx\n\nThis route describes the main public traffic path into the local infrastructure.\n\n## Route\n\n```text\nInternet\n -> gnexus.space\n -> external VPS\n -> external OpenVPN server\n -> OpenVPN tunnel\n -> internal OpenVPN client\n -> internal proxy VPS\n -> internal nginx reverse proxy\n -> target VPS or internal machine\n -> target service\n```\n\nNote (2026-10-25, navi rei): the OpenVPN client terminating the tunnel is the ovpn VM (192.168.1.150, tun0 10.8.0.2), not the internal proxy VPS itself. Inbound tun0 traffic for tcp 80/443/25565 is DNAT'd on the ovpn VM to 192.168.1.183 (internal proxy VPS) with SNAT to 192.168.1.150.\n\n## Exposure\n\n- Exposure: public.\n- Public-facing entry: `external-vps`.\n- Internal routing: OpenVPN tunnel to `internal-proxy-vps` (via DNAT on the ovpn VM, 192.168.1.150).\n- Proxy layer: `internal-nginx-proxy`.\n- Main public web ports: `80`, `443`; plus tcp `25565` (Minecraft, nginx stream module).\n\n## Purpose\n\nThe route lets public traffic terminate on an external VPS and then pass into selected internal services through a VPN tunnel. The internal nginx proxy decides which target VPS or machine receives the request.\n\n## Known Public Domains\n\n- `git.gnexus.space`\n- `hpanel.gnexus.space`\n- `jellyfin.gnexus.space`\n- `lytvak.gnexus.space`\n- `minecraft.gnexus.space`\n- `auth.gnexus.space`\n- `cloud.gnexus.space`\n- `files.gnexus.space`\n- `gnexus.space`\n- `navi.gnexus.space`\n- `synapse.gnexus.space`\n- `transmission.gnexus.space`\n\n## Known Hosts\n\n- External VPS: `external-vps` (public IP `51.83.131.93`, OVH, France — DNS target of `*.gnexus.space`).\n- Internal proxy VPS: `internal-proxy-vps`, VM `ovpn_reserv`, LAN address `192.168.1.183` (static via netplan inside the guest; was `192.168.1.226` until the 2026-10-16/17 blackout — `.226` no longer responds, see `10-systems/servers/internal-proxy-vps.md`), libvirt address `192.168.105.181/24`.\n\n## Confirmed Enabled Proxy Targets\n\n| Domain | Upstream |\n| --- | --- |\n| `auth.gnexus.space` | `http://192.168.1.167` |\n| `cloud.gnexus.space` | `http://192.168.1.152` |\n| `files.gnexus.space` | `http://192.168.1.157` |\n| `git.gnexus.space` | `http://192.168.1.156` |\n| `gnexus.space` | `http://192.168.1.151` |\n| `hpanel.gnexus.space` | `http://192.168.1.176:8000` |\n| `jellyfin.gnexus.space` | `http://192.168.1.153:8096` |\n| `navi.gnexus.space` | `http://192.168.1.168:8000` |\n| `synapse.gnexus.space` | `http://192.168.1.172:8013` |\n| `transmission.gnexus.space` | `http://192.168.1.154:3000` |\n\n## Stream-Level TCP Mapping (verified 2026-10-25)\n\n| Domain | Upstream | Mechanism |\n| --- | --- | --- |\n| `minecraft.gnexus.space` | `tcp://192.168.1.160:25565` | nginx stream module, `/etc/nginx/stream-conf.d/minecraft.gnexus.space.conf` on internal-proxy-vps |\n\n## Available But Not Confirmed Enabled\n\nThese nginx site files exist on `internal-proxy-vps`, but they were not listed as enabled symlinks during the last check:\n\n- `lytvak.gnexus.space` -> `http://192.168.1.167`\n\n(The former `minecraft.gnexus.space` entry pointed at the stale HTTP site file with dead upstream `192.168.1.218`; the live mapping is the stream config above.)\n\n## Verification Notes\n\n- 2026-10-04 (navi rei): the external VPS catch-all forwards unknown `*.gnexus.space` subdomains to the internal proxy — verified by fetching a probe file from the default site of `.226` through `http://synapse.gnexus.space`. HTTP-01 challenges therefore reach certbot on `.226` (LE certificate issued for `synapse.gnexus.space` the same day). nginx site configs live in `/etc/nginx/sites-available/` on `internal-proxy-vps` (root access required). Address note (2026-11-08, navi Eris): the internal proxy then lived on `.226`; since 2026-10-17 it is on `.183` — historical mentions of `.226` in older notes refer to that era.\n- 2026-10-04 (navi rei): added `hpanel.gnexus.space` → `http://192.168.1.176:8000` (GHard Monitor panel). nginx site on `internal-proxy-vps`: port 80 → 301 to https, port 443 → TLS proxy with `Host`/`X-Real-IP`/`X-Forwarded-For`/`X-Forwarded-Proto`, `proxy_buffering off`, `proxy_read_timeout 300s`, `proxy_http_version 1.1`. LE certificate issued via `certbot --nginx` (valid until 2027-01-02). The `/mcp` location is blocked at the proxy (403): the panel has no auth yet (GHARD_AUTH_* unset, admin token empty), so the MCP endpoint must not be public. Verified externally: DNS → 51.83.131.93, health `{\"status\":\"ok\"}`, UI 200 over HTTP/2, HTTP→HTTPS 301.\n- 2026-10-25 (navi rei): Minecraft public path verified end-to-end. MC status ping via `minecraft.gnexus.space:25565` and `51.83.131.93:25565` returned MOTD `A Minecraft Server`, version 26.2 (proto 776), 0/40 players; TCP connect from 3 external check-host.net nodes (BR/MD/RU) OK. Internal chain: ovpn VM (192.168.1.150) nft DNAT (tun0 tcp 80/443/25565 → 192.168.1.183, SNAT to 192.168.1.150; counters ~2.85M packets) → nginx stream on .183 (listen 25565 → 192.168.1.160:25565). Legacy leftovers left in place: disabled `sites-available/minecraft.gnexus.space` on .183 (stale .218 upstream), redundant socat `minecraft-tcp-forward.service` on the ovpn VM (→ 192.168.68.218:25565, mine's second NIC; receives no tun0 traffic — PREROUTING DNAT intercepts first).\n\n## Unknowns\n\n- OpenVPN public port.\n- SSH forwarding details to the internal `alex` VPS.\n- External VPS forwarding mechanism for 25565 (SSH credentials not in gnexus-creds, gntodo 506) — end-to-end verified working regardless.\n" + }, + "status": "applied", + "created_at": "2026-11-08T18:29:31Z", + "updated_at": "2026-11-08T18:29:32Z", + "applied_at": "2026-11-08T18:29:32Z", + "validation": { + "status": "ok", + "issue_count": 0, + "issues": [] + } +}