fix(web): use wss:// when page is served over HTTPS

PatrickBauer · PatrickBauer · commit fea0bd8ddc46 · 2026-03-07T16:48:04.000+01:00
When T3 Code web mode is accessed via HTTPS (e.g. through a reverse proxy
or Tailscale Serve), the WebSocket connection must use wss:// instead of
ws://. Browsers block mixed content — an insecure ws:// connection
initiated from an HTTPS page.

Fix: derive the WebSocket protocol from window.location.protocol.
diff --git a/apps/web/src/components/Sidebar.tsx b/apps/web/src/components/Sidebar.tsx
@@ -225,7 +225,7 @@ function getServerHttpOrigin(): string {
       ? bridgeUrl
       : envUrl && envUrl.length > 0
         ? envUrl
-        : `ws://${window.location.hostname}:${window.location.port}`;
+        : `${window.location.protocol === "https:" ? "wss" : "ws"}://${window.location.hostname}:${window.location.port}`;
   // Parse to extract just the origin, dropping path/query (e.g. ?token=…)
   const httpUrl = wsUrl.replace(/^wss:/, "https:").replace(/^ws:/, "http:");
   try {
diff --git a/apps/web/src/wsTransport.ts b/apps/web/src/wsTransport.ts
@@ -44,7 +44,7 @@ export class WsTransport {
         ? bridgeUrl
         : envUrl && envUrl.length > 0
           ? envUrl
-          : `ws://${window.location.hostname}:${window.location.port}`);
+          : `${window.location.protocol === "https:" ? "wss" : "ws"}://${window.location.hostname}:${window.location.port}`);
     this.connect();
   }
 

Original file line number	Diff line number	Diff line change
`@@ -44,7 +44,7 @@ export class WsTransport {`
`44`	`44`	`? bridgeUrl`
`45`	`45`	`: envUrl && envUrl.length > 0`
`46`	`46`	`? envUrl`
`47`		- : `ws://${window.location.hostname}:${window.location.port}`);
	`47`	+ : `${window.location.protocol === "https:" ? "wss" : "ws"}://${window.location.hostname}:${window.location.port}`);
`48`	`48`	`this.connect();`
`49`	`49`	`}`
`50`	`50`