Merge pull request 'fix(m3-atlas): remove netbird-only middleware from dashboard router' (#16 ) from fix/remove-netbird-middleware into master

Reviewed-on: #16
fix(m3-atlas): remove netbird-only middleware from dashboard router
2026-05-11 17:16:42 +02:00 · 2026-05-11 17:15:16 +02:00
1 changed files with 0 additions and 7 deletions
@@ -56,12 +56,6 @@
          };
        };
        middlewares = {
-          # Hermes Dashboard — Netbird mesh only
-          netbird-only = {
-            ipWhiteList = {
-              sourceRange = ["100.64.0.0/16"];
-            };
-          };
          domain-redirect = {
            redirectRegex = {
              regex = "^https://www\\.m3tam3re\\.com(.*)";
@@ -95,7 +89,6 @@
          hermes-dashboard = {
            rule = "Host(`dash.m3ta.dev`)";
            service = "hermes-dashboard";
-            middlewares = ["netbird-only"];
            entrypoints = ["websecure"];
            tls = {
              certResolver = "godaddy";
Author	SHA1	Message	Date
m3tam3re	20d2548791	Merge pull request 'fix(m3-atlas): remove netbird-only middleware from dashboard router' (#16 ) from fix/remove-netbird-middleware into master Reviewed-on: #16	2026-05-11 17:16:42 +02:00
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