novnc / noVNC

VNC client web application
https://novnc.com
Other
11.63k stars 2.31k forks source link

NOVNC not continue reload. #903

Closed AntoWkill closed 7 years ago

AntoWkill commented 7 years ago

From today without do nothing my novnc console stop working, its load and i can see the vm screen for 1-2 second and after disconnect and recharge.

The error is with ALL browser, i have also tried from Mobile Phone and i have the same error.

https://www.youtube.com/watch?v=7aPpensiZo0 --> Error screen

CendioOssman commented 7 years ago

Which version of noVNC are you using?

What does the browser console say?

AntoWkill commented 7 years ago
novnc1 novnc2 novnc3 novnc4

VERSION: novnc-pve: 0.5-9 (on proxmox)

CendioOssman commented 7 years ago

That is very old. I would suggest testing master.

However the logs seem to indicate a normal disconnect from the server. What VNC server is this? Can you check its log files?

AntoWkill commented 7 years ago

set 25 12:52:29 problem with client XXXX; ssl3_read_bytes: sslv3 alert bad certificate I've already tried both letsencrypt and with the self-signed certificate s(the error becomes sslv3 alert unknown ca)

CendioOssman commented 7 years ago

A bad certificate would not cause the issues you describe. What else does the log say?

AntoWkill commented 7 years ago

Nothing alse on the log, the certificate is no bad Is perfectly working.

AntoWkill commented 7 years ago

I had also tried to use the last version of novnc, and error is the same.

CendioOssman commented 7 years ago

What VNC server are you using?

AntoWkill commented 7 years ago

I think vncterm

CendioOssman commented 7 years ago

That seems to use libvncserver. Are you connecting directly to it, or do you have a websocket proxy inbetween?

AntoWkill commented 7 years ago

Yes there is pveproxy

CendioOssman commented 7 years ago

Alright, so I guess the log is from pveproxy? What does the log from vncterm say?

AntoWkill commented 7 years ago

Sep 26 15:55:39 ns3008621 pvedaemon[14800]: root@pam end task UPID:ns3008621:00000410:93DE79C3:59CA5C59:vncproxy:100:root@pam: OK Sep 26 15:55:39 ns3008621 pveproxy[24409]: problem with client 151.22.103.198; ssl3_read_bytes: tlsv1 alert unknown ca Sep 26 15:55:40 ns3008621 pvedaemon[22464]: root@pam starting task UPID:ns3008621:00000413:93DE7AB9:59CA5C5C:vncproxy:100:root@pam: Sep 26 15:55:40 ns3008621 pvedaemon[1043]: starting vnc proxy UPID:ns3008621:00000413:93DE7AB9:59CA5C5C:vncproxy:100:root@pam: Sep 26 15:55:41 ns3008621 pveproxy[24409]: problem with client 151.22.103.198; ssl3_read_bytes: tlsv1 alert unknown ca Sep 26 15:55:41 ns3008621 pvedaemon[22464]: root@pam end task UPID:ns3008621:00000413:93DE7AB9:59CA5C5C:vncproxy:100:root@pam: OK Sep 26 15:56:01 ns3008621 CRON[1076]: (root) CMD (/usr/local/rtm/bin/rtm 44 > /dev/null 2> /dev/null) Sep 26 15:57:01 ns3008621 CRON[1227]: (root) CMD (/usr/local/rtm/bin/rtm 44 > /dev/null 2> /dev/null)

AntoWkill commented 7 years ago

I found the problem but i haven't solution. The VNC Console start again to work IF i force SSLV3 (insicure). So the problem is tls.

DirectXMan12 commented 7 years ago

hmm... maybe the TLS implementation is mismatched?

AntoWkill commented 7 years ago

And how i can check / solve?

CendioOssman commented 7 years ago

I'm afraid that would be a question for pveproxy. noVNC isn't involved in the TLS stuff in this case, only the browser and pveproxy. So I would suggest your next step would be to file a bug with pveproxy.

I'm going to close this issue since it doesn't involve noVNC.