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
InB4, "this issue already exists": I checked this issue and the answer there is very old, vague, doesn't provide context for how to implement it in code.
Background: I have a scientific device with a screen on it and it provides me with an IP address that, if I put it into a VNC app, I can see and control the screen. This is currently out in the world and working fine.
Goal: I want to build a custom VNC app so I have a branded experience for my customers.
Using x to keep the URL private...
Problem: <VncDisplay url="ws://xx.xxx.xxx.xxx" /> gives me back the following error:
websock.js:262 WebSocket connection to 'ws://xx.xxx.xxx.xxx/' failed: Error during WebSocket handshake: Unexpected response code: 200
In the Chrome DevTools Network tab I have the following in the Headers:
InB4, "this issue already exists": I checked this issue and the answer there is very old, vague, doesn't provide context for how to implement it in code.
Background: I have a scientific device with a screen on it and it provides me with an IP address that, if I put it into a VNC app, I can see and control the screen. This is currently out in the world and working fine.
Goal: I want to build a custom VNC app so I have a branded experience for my customers.
Using
x
to keep the URL private...Problem:
<VncDisplay url="ws://xx.xxx.xxx.xxx" />
gives me back the following error:websock.js:262 WebSocket connection to 'ws://xx.xxx.xxx.xxx/' failed: Error during WebSocket handshake: Unexpected response code: 200
In the Chrome DevTools Network tab I have the following in the Headers:
Request URL: ws://xx.xxx.xxx.xxx/
Provisional headers are shown
Accept-Encoding: gzip, deflate
Accept-Language: en-US,en;q=0.9
Cache-Control: no-cache
Connection: Upgrade
Host: xx.xxx.xxx.xxx
Origin: http://localhost:3000
Pragma: no-cache
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
Sec-WebSocket-Key: a string...(wB, etc)
Sec-WebSocket-Protocol: binary
Sec-WebSocket-Version: 13
Upgrade: websocket
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36
The text was updated successfully, but these errors were encountered: