From c70dc33f67c85dc492090edd68b18c08e5e84997 Mon Sep 17 00:00:00 2001 From: Sascha Lustenberger | techlan gmbh Date: Tue, 24 Feb 2026 10:31:08 +0100 Subject: [PATCH] fix(caddy): route relay WebSocket traffic to relay container Add /relay* location block to Caddyfile template so that NetBird relay WebSocket connections (rels://) are correctly forwarded to the relay container instead of falling through to the dashboard handler. Without this fix, all relay WebSocket connections silently hit the dashboard container, causing STUN/relay connectivity failures for all deployed NetBird instances. Co-Authored-By: Claude Sonnet 4.6 --- templates/Caddyfile.j2 | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/templates/Caddyfile.j2 b/templates/Caddyfile.j2 index 58c8284..6ed0dd9 100644 --- a/templates/Caddyfile.j2 +++ b/templates/Caddyfile.j2 @@ -29,6 +29,11 @@ } } + # NetBird Relay WebSocket (rels://) + handle /relay* { + reverse_proxy netbird-{{ subdomain }}-relay:80 + } + # Default: NetBird Dashboard handle { reverse_proxy netbird-{{ subdomain }}-dashboard:80