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
Only succeeded by adding the prefix "ws://".This is weird, is there a way to remove it?
This warning will not show up when "ws://" is missing.
Also, what's the difference between "ws" and "wss"?Users won't know it's difference between http and https.
The offical server used "wss", but connection failed to establish when I tried to connect localhost.Only "ws" works.
Also, when connecting offical server with "ws", No warning will show up.
In one word,pls make it more user-friendly :)
The text was updated successfully, but these errors were encountered:
driver1748
changed the title
Unable to connect to localhost
Please remove "ws://"
Dec 15, 2022
When using the HTTPS protocol, it is restricted by the browser security. You can only connect to the back end using the WSS protocol (which can be understood as the SSL version of WebSocket), that is, wss://. At the same time, you need to configure the ssl certificate for the back end to link. You can add a ws://"+ field in the javascript code of index.html to prevent the front end from displaying ws://. This operation will also result in failure to connect to the wss server, In order to ensure compatibility in the official demo, ws://or wss://should be included in the address by default. You can modify the default backend address by modifying the HTML code.
Also tried global IPv4, failed too.
Only succeeded by adding the prefix "ws://".This is weird, is there a way to remove it?
This warning will not show up when "ws://" is missing.
Also, what's the difference between "ws" and "wss"?Users won't know it's difference between http and https.
The offical server used "wss", but connection failed to establish when I tried to connect localhost.Only "ws" works.
Also, when connecting offical server with "ws", No warning will show up.
In one word,pls make it more user-friendly :)
The text was updated successfully, but these errors were encountered: