I'm using this on coder (remote dev workspaces in the cloud) and when serving it automatically forwards the open ports in the workspace to a special subdomain, all on HTTPS.
In the index.html the protocol is hardcoded to "ws:" though, which the browser then prevents from loading because it's insecure.
Best solution would be to check if the page is loaded securely or insecurely and then adding/removing the 's' to the protocol aswell (ws/wss), maybe like this?
I'm using this on coder (remote dev workspaces in the cloud) and when serving it automatically forwards the open ports in the workspace to a special subdomain, all on HTTPS. In the index.html the protocol is hardcoded to "ws:" though, which the browser then prevents from loading because it's insecure. Best solution would be to check if the page is loaded securely or insecurely and then adding/removing the 's' to the protocol aswell (ws/wss), maybe like this?