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 8afbaf7..a6acb93 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 @@ -3,8 +3,8 @@ status: active last_reviewed: 2026-10-04 review_interval: 90d -confidence: medium -source_of_truth: owner-confirmed +confidence: high +source_of_truth: owner-confirmed-and-live-verified --- # Public gnexus.space Traffic To Internal nginx @@ -41,6 +41,7 @@ ## Known Public Domains - `git.gnexus.space` +- `hpanel.gnexus.space` - `jellyfin.gnexus.space` - `lytvak.gnexus.space` - `minecraft.gnexus.space` @@ -66,6 +67,7 @@ | `files.gnexus.space` | `http://192.168.1.157` | | `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` | @@ -81,6 +83,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): 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. ## Unknowns diff --git a/90-maintenance/pending-changes/20261005000324-96972db9.json b/90-maintenance/pending-changes/20261005000324-96972db9.json new file mode 100644 index 0000000..408d4a2 --- /dev/null +++ b/90-maintenance/pending-changes/20261005000324-96972db9.json @@ -0,0 +1,19 @@ +{ + "id": "20261005000324-96972db9", + "kind": "doc", + "target": "10-systems/traffic-routes/public-gnexus-space-to-internal-nginx.md", + "summary": "Add hpanel.gnexus.space route to internal nginx proxy targets (GHard panel, TLS, /mcp blocked)", + "reason": "Публикация hpanel.gnexus.space: nginx-сайт на internal-proxy (.226) с TLS (LE, до 2027-01-02), апстрим http://192.168.1.176:8000, /mcp закрыт 403 на прокси. Проверено вживую: DNS, health, UI HTTP/2, 301.", + "payload": { + "content": "---\nowner: gmikcon\nstatus: active\nlast_reviewed: 2026-10-04\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\n## Exposure\n\n- Exposure: public.\n- Public-facing entry: `external-vps`.\n- Internal routing: OpenVPN tunnel to `internal-proxy-vps`.\n- Proxy layer: `internal-nginx-proxy`.\n- Main public web ports: `80`, `443`.\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`, s-host.com.ua, Ukraine, Ubuntu Server 22.04.\n- Internal proxy VPS: `internal-proxy-vps`, VM `ovpn_reserv`, LAN address `192.168.1.226`, 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## 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- `minecraft.gnexus.space` -> `tcp://192.168.1.218:25565`\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).\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\n## Unknowns\n\n- OpenVPN public port.\n- SSH forwarding details to the internal `alex` VPS." + }, + "status": "applied", + "created_at": "2026-10-05T00:03:24Z", + "updated_at": "2026-10-05T00:03:25Z", + "applied_at": "2026-10-05T00:03:25Z", + "validation": { + "status": "ok", + "issue_count": 0, + "issues": [] + } +}