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
The change is not visible, and there is an error about unable to connect to the websocket in the console.
It looks like the hot reload websocket connection is using the network IP address even on localhost, instead of using the host from the current environment.
So on https://localhost:8081 it's trying to load wss://192.168.0.109:8081/ws (my computer's local IP), and my browser (both Firefox and Chrome) are generating a security warning that I can't see to accept.
It does work if I manually open https://192.168.0.109:8081 and accept the security warning, but this is rather non-obvious when onboarding people to a project.
The text was updated successfully, but these errors were encountered:
Version
5.0.4
Reproduction link
github.com
Environment info
Steps to reproduce
npm run serve
What is expected?
The change should be immediately visible
What is actually happening?
The change is not visible, and there is an error about unable to connect to the websocket in the console.
It looks like the hot reload websocket connection is using the network IP address even on localhost, instead of using the host from the current environment.
So on https://localhost:8081 it's trying to load wss://192.168.0.109:8081/ws (my computer's local IP), and my browser (both Firefox and Chrome) are generating a security warning that I can't see to accept.
It does work if I manually open https://192.168.0.109:8081 and accept the security warning, but this is rather non-obvious when onboarding people to a project.
The text was updated successfully, but these errors were encountered: