You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before 3.3.0, the dev server's websocket was connected via wss:// when the site was reached via https:// but this seems no longer to be the case, it now only seems to attempt ws:// which is blocked by the browser:
Steps to reproduce
Create a app on 3.3.0 and start the dev server
Set up a HTTPS reverse proxy towards the devserver port
If the HTTPS certificate is self-signed, add it to OS or Browser stores
Open the HTTPS site, observe above error
Expected behavior
Websocket should connect using wss:// when site is served on https://.
Actual behavior
Websocket tries to connect ws:// and is blocked by the browser.
The text was updated successfully, but these errors were encountered:
Describe the bug
Before 3.3.0, the dev server's websocket was connected via
wss://
when the site was reached viahttps://
but this seems no longer to be the case, it now only seems to attemptws://
which is blocked by the browser:Steps to reproduce
Expected behavior
Websocket should connect using
wss://
when site is served onhttps://
.Actual behavior
Websocket tries to connect
ws://
and is blocked by the browser.The text was updated successfully, but these errors were encountered: