Open Tancy0123 opened 11 months ago
If you SSH to the system and tail the ~/.vnc/*.log file when you login, is there any output when it freezes?
If you SSH to the system and tail the ~/.vnc/*.log file when you login, is there any output when it freezes?
The following is the content of the log:
2023-11-23 10:05:41,988 [DEBUG] websocket 127: using SSL socket 2023-11-23 10:05:41,991 [DEBUG] websocket 127: BasicAuth matched 2023-11-23 10:05:41,991 [DEBUG] websocket 127: Invalid WS request, maybe a HTTP one 2023-11-23 10:05:41,991 [DEBUG] websocket 127: Requested file '/vendor/interact.min.js.map' 2023-11-23 10:05:41,991 [DEBUG] websocket 127: file not found or insufficient permissions 2023-11-23 10:05:41,991 [INFO] websocket 127: 115.154.130.52 115.154.130.52 tancy "GET /vendor/interact.min.js.map HTTP/1.1" 404 180 2023-11-23 10:05:41,991 [DEBUG] websocket 127: No connection after handshake 2023-11-23 10:05:41,991 [DEBUG] websocket 127: handler exit 2023-11-23 10:05:42,013 [INFO] websocket 128: got client connection from 115.154.130.52 40A69FF0E87F0000:error:0A000416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown:../ssl/record/rec_layer_s3.c:1584:SSL alert number 46 2023-11-23 10:05:42,024 [DEBUG] websocket 128: using SSL socket 2023-11-23 10:05:42,024 [DEBUG] websocket 128: Client closed during handshake 2023-11-23 10:05:42,024 [DEBUG] websocket 128: No connection after handshake 2023-11-23 10:05:42,024 [DEBUG] websocket 128: handler exit 2023-11-23 10:05:42,036 [INFO] websocket 129: got client connection from 115.154.130.52 2023-11-23 10:05:42,043 [DEBUG] websocket 129: using SSL socket 2023-11-23 10:05:42,046 [DEBUG] websocket 129: BasicAuth matched 2023-11-23 10:05:42,046 [DEBUG] websocket 129: Invalid WS request, maybe a HTTP one 2023-11-23 10:05:42,046 [DEBUG] websocket 129: Requested file '/app/images/icons/368_kasm_logo_only_32x32.png' 2023-11-23 10:05:42,046 [INFO] websocket 129: 115.154.130.52 115.154.130.52 tancy "GET /app/images/icons/368_kasm_logo_only_32x32.png HTTP/1.1" 200 7814 2023-11-23 10:05:42,046 [DEBUG] websocket 129: No connection after handshake 2023-11-23 10:05:42,046 [DEBUG] websocket 129: handler exit 2023-11-23 10:05:43,933 [INFO] EncodeManager: Max encoding time during the last 60 frames: 31 ms (limit 16, near limit 13) 2023-11-23 10:05:45,785 [INFO] EncodeManager: Max encoding time during the last 60 frames: 19 ms (limit 16, near limit 13) 2023-11-23 10:05:51,416 [DEBUG] SMsgReader: Received binary clipboard, type image/png, 56240 bytes 2023-11-23 10:05:51,416 [DEBUG] Selection: Remote binary clipboard announced, grabbing local ownership 2023-11-23 10:05:51,416 [DEBUG] Selection: Grabbed PRIMARY selection 2023-11-23 10:05:51,416 [DEBUG] Selection: Grabbed CLIPBOARD selection 2023-11-23 10:05:51,416 [DEBUG] Selection: Local clipboard lost, notifying clients 2023-11-23 10:05:51,416 [DEBUG] Selection: Client sent 1 mimes, 1 were valid 2023-11-23 10:05:51,416 [DEBUG] Selection: Selection request for PRIMARY (type TARGETS) 2023-11-23 10:05:51,416 [DEBUG] Selection: Selection request for CLIPBOARD (type TARGETS) 2023-11-23 10:05:51,417 [DEBUG] Selection: Selection request for CLIPBOARD (type UTF8_STRING) 2023-11-23 10:05:51,417 [PRIO] Selection: Text clipboard paste requested, but client sent no text 2023-11-23 10:07:02,683 [DEBUG] SMsgReader: Received binary clipboard, type text/plain, 2659 bytes 2023-11-23 10:07:02,684 [DEBUG] SMsgReader: Received binary clipboard, type text/html, 5649 bytes 2023-11-23 10:07:02,684 [DEBUG] Selection: Remote binary clipboard announced, grabbing local ownership 2023-11-23 10:07:02,684 [DEBUG] Selection: Grabbed PRIMARY selection 2023-11-23 10:07:02,684 [DEBUG] Selection: Grabbed CLIPBOARD selection 2023-11-23 10:07:02,684 [DEBUG] Selection: Client sent 2 mimes, 1 were valid 2023-11-23 10:07:02,684 [DEBUG] Selection: Selection request for PRIMARY (type TARGETS) 2023-11-23 10:07:02,684 [DEBUG] Selection: Selection request for CLIPBOARD (type TARGETS) 2023-11-23 10:07:02,685 [DEBUG] Selection: Selection request for CLIPBOARD (type UTF8_STRING)
same issue, any fix ?????
update:
ended up deleting the .vnc folder
re-run vncserver
:
Please choose Desktop Environment to run:
[1] Gnome
[2] Manually edit xstartup
and choose [2]
Ah... I did not notice it before, but the password screenshot you provided is Gnome's login screen or lock screen, not Kasm. KasmVNC has not insight into the desktop environment. That being said, if your desktop environment has a lock screen that comes up after 15 minutes (or whatever time frame), that is outside of KasmVNC, you will need to consult the docs for whatever DE you are using. Additionally, the KasmVNC credentials are not the same as the user on the system. So, if you are entering your KasmVNC password in that box, and it is not the same as the password set on the system, then it will fail.
Describe the bug A clear and concise description of what the issue is.
System Description Provide the output of
KasmVNC Details Provide the filename of the package you installed KasmVNC with. The filename includes important details like the OS, architecture, and commit sha.
kasmvncserver_focal_1.2.0_amd64.deb
Provide the output of this command.
To Reproduce Steps to reproduce the behavior (for non-installation issues):
Expected behavior A clear and concise description of what you expected to happen.
After setting up kasmvnc according to the documentation, I can log in normally, but after timeout logout, entering the password again will freeze. What is the reason for this? Entering the wrong password will display an incorrect password icon.
Browser If this is a problem with the KasmVNC client, provide details about the browser you are accessing KasmVNC from.
Additional context Add any other context about the problem here.