Error missing on mobile, shows on desktop "Failed to construct 'WebSocket': An insecure WebSocket connection may not..."

[Dawsson]

The error will show up over my desktop browser but wont display on my phone. My phone simply shows no threads, no warning, nothing.

[Dawsson]

SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.
    at cue.connect (https://t3.dawson.gg/assets/index-CWbABLMQ.js:23:253757)
    at new cue (https://t3.dawson.gg/assets/index-CWbABLMQ.js:23:252941)
    at due (https://t3.dawson.gg/assets/index-CWbABLMQ.js:23:255360)
    at GA (https://t3.dawson.gg/assets/index-CWbABLMQ.js:23:257557)
    at Cde (https://t3.dawson.gg/assets/index-CWbABLMQ.js:23:290148)
    at bo (https://t3.dawson.gg/assets/index-CWbABLMQ.js:9:47580)
    at pc (https://t3.dawson.gg/assets/index-CWbABLMQ.js:9:70182)
    at Ac (https://t3.dawson.gg/assets/index-CWbABLMQ.js:9:80465)
    at Lu (https://t3.dawson.gg/assets/index-CWbABLMQ.js:9:116051)
    at Pu (https://t3.dawson.gg/assets/index-CWbABLMQ.js:9:115098)

[binbandit]

Hi, thanks for the report.

Please share a bit more detail so we can narrow this down:

1. Are you using the desktop app, or opening T3 Code in a normal browser?
2. What exact T3 Code version are you running? If built from source, what commit/branch?
3. What exact URL are you opening when it fails? Please include host/port, but redact any secrets or tokens.
4. Is the page loaded over https:// or http://?
5. How is T3 Code deployed in your setup?
   Examples: direct local server, NGINX, Caddy, Cloudflare Tunnel, Tailscale Serve, ngrok, custom reverse proxy.
6. Are the frontend and backend on the same origin, or is the UI hosted separately from the T3 server/WebSocket?
7. Did you set VITE_WS_URL anywhere for this build or deployment? If yes, what value pattern did you use? Redact secrets if needed.
8. Are you running the built app, or a dev setup like bun dev / Vite dev server?
9. If you’re reverse proxying, is TLS/HTTPS terminated at the proxy while T3 runs upstream over plain HTTP?
10. Does it fail for every user on that deployment, or only some users? If only some, what differs between working and failing users?
11. Which browser and version are affected? Does it reproduce in another browser?
12. In DevTools Console, what is the full error message / stack trace?
13. In DevTools Network, do you see a WebSocket request at all, or does it fail before any request appears?
14. If a WebSocket request does appear, what exact URL is it trying to open? We mainly want to know whether it is ws://... or wss://....
15. If this is self-hosted, please paste the exact server start command or deployment config you’re using, with secrets redacted.

That should tell us pretty quickly whether this is:

• an HTTPS page trying to use ws://...
• a bad VITE_WS_URL override
• a dev-mode / Vite exposure issue
• or a proxy/config problem after the protocol selection step.