-
Notifications
You must be signed in to change notification settings - Fork 7
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
fbvnc: vnc init failed! #4
Comments
Too large to fit in the margin ***@***.***> wrote:
```
fbvnc/fbvnc 192.168.1.10 5901
fbvnc: vnc init failed!
```
other vnc client OK
![image](https://github.com/aligrudi/fbvnc/assets/8005654/768e028c-a3f5-4e1a-b120-149d4bc91041)
This is probably because fbvnc does not support authentication methods.
This fork supports password authentication though:
https://github.com/uklatt/fbvnc
Ali
|
I get the same error (both in the fork with authentication support and here) even when I disable authentication on the vnc server. In my case I'm using https://github.com/any1/wayvnc , which detects a new client and immediately "close_after_write". |
MujJahHidDeenn ***@***.***> wrote:
I get the same error (both in the fork with authentication support and here) even when I disable authentication on the vnc server.
In my case I'm using https://github.com/any1/wayvnc , which detects a new client and immediately "close_after_write".
Does this issue exists with other VNC servers like Xvnc or Qemu's?
Ali
|
I got the same problem with wayvnc. Xvnc and Qemu's works fine (see my other issue). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
other vnc client OK
The text was updated successfully, but these errors were encountered: