feat/hermes-dashboard-traefik
master
Browser (Netbird) → dash.m3ta.dev (TLS) → m3-atlas Traefik → Netbird → m3-hermes:9119
hermes-dashboard.nix
--insecure
0.0.0.0
100.64.0.0/16
traefik.nix
hermes-dashboard
http://100.81.231.152:9119
dash.m3ta.dev
netbird-only
https://dash.m3ta.dev — only reachable from Netbird mesh peers (IP whitelist + firewall).
https://dash.m3ta.dev
dash.m3ta.dev needs to point to m3-atlas (152.53.85.162). May already be handled or needs a DNS record.
152.53.85.162
m3-hermes: - Add --insecure flag (required for 0.0.0.0 bind, safe behind Netbird firewall) - Update comments to document the Traefik proxy flow m3-atlas Traefik: - New service: hermes-dashboard → http://100.81.231.152:9119 (Netbird) - New router: dash.m3ta.dev with GoDaddy TLS cert - New middleware: netbird-only (IP whitelist 100.64.0.0/16) Flow: Browser → dash.m3ta.dev (TLS) → Traefik → Netbird → m3-hermes:9119
No dependencies set.
The note is not visible to the blocked user.
Architecture
Changes
m3-hermes (
hermes-dashboard.nix)--insecureflag — required to bind0.0.0.0(hermes refuses non-localhost without it)100.64.0.0/16)m3-atlas (
traefik.nix)hermes-dashboard→http://100.81.231.152:9119(m3-hermes via Netbird)dash.m3ta.devwith GoDaddy ACME TLS certificatenetbird-only— IP whitelist restricting to100.64.0.0/16Access
https://dash.m3ta.dev— only reachable from Netbird mesh peers (IP whitelist + firewall).Supersedes
--insecurefix with the full Traefik setup)DNS
dash.m3ta.devneeds to point to m3-atlas (152.53.85.162). May already be handled or needs a DNS record.