-
Notifications
You must be signed in to change notification settings - Fork 364
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[source build] could not connect to spice or vnc #1323
Comments
Having the same issue, haven't manage to resolve it yet. |
x3... Me tooo :) |
x4 same here --- EDIT--- For those that are stuck with this noVNC problem and are running kimchi on a headless machine, I found a temporary solution to at least complete the first installation. Here you can find the way to create an SSH tunnel that you can later use with your VNC client to connect to the VM. One you have connected, you might see some errors. Just hit TAB and then select the boot option. Hope it can help. |
这个问题有可能是websockify版本问题,使用websockify 0.7.0版本就不报这个错误了,解决办法: sudo pip3 install websockify==0.7.0 |
This problem may be caused by the websockify version. If you use the websockify 0.7.0 version, this error will not be reported. Solution
please write in english the next time, thank you. but anyway ill try that out |
Describe the bug
the web vnc or spice connection does not work as intendet, and breaks the connection up after a few frames
To Reproduce
Steps to reproduce the behavior:
Expected behavior
as tested i would like to see a guest desktop / video here
Desktop (please complete the following information):
Additional context
Log:
The text was updated successfully, but these errors were encountered: