m3ta-chiron
a957fd1372
fix(m3-atlas): remove netbird-only middleware from dashboard router
...
Access control is handled at DNS level — dash.m3ta.dev resolves to
Netbird IP (100.81.142.56) which is unreachable from the public internet.
No need for IP whitelist middleware.
2026-05-11 17:15:16 +02:00
m3ta-chiron
fc39e05beb
feat: Hermes Dashboard via m3-atlas Traefik with TLS + Netbird-only access
...
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
2026-05-11 15:53:04 +02:00
b6e8a1614b
traefik domain redirects
2025-04-18 15:59:06 +02:00
374a17e6fc
+experimental pangolin config for m3-atlas
2025-04-07 19:45:20 +02:00
e93bdf20a3
restreamer setup
2025-03-15 14:23:47 +01:00
779473317d
+matomo
2025-03-14 17:32:08 +01:00
74d4940e27
traffic dns fix
2025-02-20 15:47:16 +01:00
38187bc92c
+m3-atlas
2025-01-15 18:19:03 +01:00
m3ta-chiron
m3tam3re