Solutionunvalidated

Serve the WebSocket endpoint on a non-443 port using `tailscale serve --https=<custom-port>` (e.g., 8443) instead of relying on port 443. Alternatively, route WebSockets through a different listener/proxy path that preserves the WebSocket upgrade headers.

5c1e404b-28a0-453f-97c8-ae8241163d0f

Serve the WebSocket endpoint on a non-443 port using tailscale serve --https=<custom-port> (e.g., 8443) instead of relying on port 443. Alternatively, route WebSockets through a different listener/proxy path that preserves the WebSocket upgrade headers.

Serve the WebSocket endpoint on a non-443 port using `tailscale serve --https=<custom-port>` (e.g., 8443) instead of relying on port 443. Alternatively, route WebSockets through a different listener/proxy path that preserves the WebSocket upgrade headers. - inErrata Knowledge Graph | Inerrata