starred/pikvm-pikvm
1
0
Fork 0
mirror of https://github.com/pikvm/pikvm.git synced 2026-03-02 18:16:56 -05:00
Code Issues 133 Projects Packages Wiki Activity

VNC not working #941

New issue
Closed
opened 2026-02-20 14:08:47 -05:00 by deekerman · 4 comments
deekerman commented 2026-02-20 14:08:47 -05:00
Owner
Copy link

Originally created by @DIGist on GitHub (Aug 28, 2024).

Originally assigned to: @mdevaev on GitHub.

Unable to connect to VNC on Pikvm model 3.
Configured /etc/kvmd/override.yaml:

vnc:
     # See https://github.com/pikvm/pikvm/blob/master/pages/vnc.md
     keymap: /usr/share/kvmd/keymaps/en-us
     auth:
         vncauth:
             enabled: true # Enable auth via /etc/kvmd/vncpasswd

I want to use the vncauth to connect as it allows me to work with another project that works with vnc control.
Connecting with tigervnc gives me a h264 context error
Attempting to connect with standard vnc fails with this in the kvmd-vnc log:

> Aug 28 09:12:49 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.server              INFO --- [::ffff:192.168.144.99]:43428 [entry]: Connected client
> Aug 28 09:12:49 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb                 INFO --- [::ffff:192.168.144.99]:43428 [entry]: Starting client tasks ...
> Aug 28 09:12:49 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb                 INFO --- [::ffff:192.168.144.99]:43428 [main]: Using RFB version 3.8
> Aug 28 09:12:49 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb                 INFO --- [::ffff:192.168.144.99]:43428 [main]: Using VeNCrypt security type
> Aug 28 09:12:49 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb                 INFO --- [::ffff:192.168.144.99]:43428 [main]: Using VeNCrypt/X509Plain auth type
> Aug 28 09:12:50 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb                 INFO --- [::ffff:192.168.144.99]:43428 [main]: Starting TLS (valid) ...
> Aug 28 09:12:50 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb                 INFO --- [::ffff:192.168.144.99]:43428 [main]: Gone: Can't start TLS: ConnectionResetError:
> Aug 28 09:12:50 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb                 INFO --- [::ffff:192.168.144.99]:43428 [kvmd]: Cancelling subtask ...
> Aug 28 09:12:50 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb                 INFO --- [::ffff:192.168.144.99]:43428 [streamer]: Cancelling subtask ...
> Aug 28 09:12:50 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb                 INFO --- [::ffff:192.168.144.99]:43428 [fb_sender]: Cancelling subtask ...
> Aug 28 09:12:50 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb                 INFO --- [::ffff:192.168.144.99]:43428 [entry]: Connection closed

To Reproduce
Steps to reproduce the behavior, like:

  1. Enable vnc in /etc/kvmd/override.yaml
  2. restart
  3. attempt to connect with plain vnc
  4. See failure and log in 'journalctl -u kvmd-vnc'

Expected behavior
successful standard vnc connection to pikvm

Desktop (please complete the following information):

  • OS: Linux
  • Browser chrome
  • Version latest
  • VNC client tigervnc, remmina, connections, multivnc

PiKVM info:

  • Raspberry Pi board version : RPi 4
  • PiKVM platform : Model 3
  • KVMD version:
    kvmd 4.8-1
    kvmd-fan 0.31-1
    kvmd-oled 0.27-1
    kvmd-platform-v3-hdmi-rpi4 4.8-1
    kvmd-webterm 0.50-1
  • uStreamer version: ustreamer 6.13-1
  • Linux kernel: Linux pikvm1 6.6.45-3-rpi #1 SMP Fri Aug 23 19:13:06 UTC 2024 armv7l GNU/Linux
Originally created by @DIGist on GitHub (Aug 28, 2024). Originally assigned to: @mdevaev on GitHub. Unable to connect to VNC on Pikvm model 3. Configured /etc/kvmd/override.yaml: ```yaml vnc: # See https://github.com/pikvm/pikvm/blob/master/pages/vnc.md keymap: /usr/share/kvmd/keymaps/en-us auth: vncauth: enabled: true # Enable auth via /etc/kvmd/vncpasswd ``` I want to use the vncauth to connect as it allows me to work with another project that works with vnc control. Connecting with tigervnc gives me a h264 context error Attempting to connect with standard vnc fails with this in the kvmd-vnc log: ``` > Aug 28 09:12:49 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.server INFO --- [::ffff:192.168.144.99]:43428 [entry]: Connected client > Aug 28 09:12:49 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb INFO --- [::ffff:192.168.144.99]:43428 [entry]: Starting client tasks ... > Aug 28 09:12:49 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb INFO --- [::ffff:192.168.144.99]:43428 [main]: Using RFB version 3.8 > Aug 28 09:12:49 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb INFO --- [::ffff:192.168.144.99]:43428 [main]: Using VeNCrypt security type > Aug 28 09:12:49 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb INFO --- [::ffff:192.168.144.99]:43428 [main]: Using VeNCrypt/X509Plain auth type > Aug 28 09:12:50 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb INFO --- [::ffff:192.168.144.99]:43428 [main]: Starting TLS (valid) ... > Aug 28 09:12:50 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb INFO --- [::ffff:192.168.144.99]:43428 [main]: Gone: Can't start TLS: ConnectionResetError: > Aug 28 09:12:50 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb INFO --- [::ffff:192.168.144.99]:43428 [kvmd]: Cancelling subtask ... > Aug 28 09:12:50 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb INFO --- [::ffff:192.168.144.99]:43428 [streamer]: Cancelling subtask ... > Aug 28 09:12:50 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb INFO --- [::ffff:192.168.144.99]:43428 [fb_sender]: Cancelling subtask ... > Aug 28 09:12:50 pikvm1 kvmd-vnc[568]: kvmd.apps.vnc.rfb INFO --- [::ffff:192.168.144.99]:43428 [entry]: Connection closed ``` **To Reproduce** Steps to reproduce the behavior, like: 1. Enable vnc in /etc/kvmd/override.yaml 2. restart 3. attempt to connect with plain vnc 4. See failure and log in 'journalctl -u kvmd-vnc' **Expected behavior** successful standard vnc connection to pikvm **Desktop (please complete the following information):** - OS: Linux - Browser chrome - Version latest - VNC client tigervnc, remmina, connections, multivnc **PiKVM info:** - Raspberry Pi board version : RPi 4 - PiKVM platform : Model 3 - KVMD version: kvmd 4.8-1 kvmd-fan 0.31-1 kvmd-oled 0.27-1 kvmd-platform-v3-hdmi-rpi4 4.8-1 kvmd-webterm 0.50-1 - uStreamer version: ustreamer 6.13-1 - Linux kernel: Linux pikvm1 6.6.45-3-rpi #1 SMP Fri Aug 23 19:13:06 UTC 2024 armv7l GNU/Linux
deekerman commented 2026-02-20 14:08:48 -05:00
Author
Owner
Copy link

@mdevaev commented on GitHub (Aug 28, 2024):

Connecting with tigervnc gives me a h264 context error

Which error exactly?

@mdevaev commented on GitHub (Aug 28, 2024): > Connecting with tigervnc gives me a h264 context error Which error exactly?
deekerman commented 2026-02-20 14:08:48 -05:00
Author
Owner
Copy link

@DIGist commented on GitHub (Aug 28, 2024):

image

But I'm really most interested in the standard vncauth

@DIGist commented on GitHub (Aug 28, 2024): ![image](https://github.com/user-attachments/assets/866482f1-b685-418a-809a-6e1ab905d6f1) But I'm really most interested in the standard vncauth
deekerman commented 2026-02-20 14:08:48 -05:00
Author
Owner
Copy link

@mdevaev commented on GitHub (Aug 28, 2024):

It seems your client can't handle SSL encryption. You can try o disable it at all:

vnc:
    server:
        tls:
            ciphers: ""

standard vncauth

It is not safe by design.

@mdevaev commented on GitHub (Aug 28, 2024): It seems your client can't handle SSL encryption. You can try o disable it at all: ``` vnc: server: tls: ciphers: "" ``` > standard vncauth It is not safe by design.
deekerman commented 2026-02-20 14:08:48 -05:00
Author
Owner
Copy link

@DIGist commented on GitHub (Aug 28, 2024):

Sure thing! Thanks for the assist.
I really appreciate the default for vnc requiring encryption as I know basic VNC doesn't have encryption to protect the traffic. In my specific use case, the tool that will be connecting to kvmd-vnc will be going over an SSH tunnel for encryption and the 5900 port will be blocked from traffic from everything except localhost.

@DIGist commented on GitHub (Aug 28, 2024): Sure thing! Thanks for the assist. I really appreciate the default for vnc requiring encryption as I know basic VNC doesn't have encryption to protect the traffic. In my specific use case, the tool that will be connecting to kvmd-vnc will be going over an SSH tunnel for encryption and the 5900 port will be blocked from traffic from everything except localhost.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
gh-pages
No results found.
Labels
Clear labels   
component:documentation

   
help wanted

   
resolution:delayed

   
resolution:duplicate

   
resolution:fixed

   
resolution:invalid

   
resolution:rejected

   
resolution:wontfix

   
success story

   
type:bug

   
type:bug

   
type:feature

   
type:question

   
type:question
No labels
component:documentation
help wanted
resolution:delayed
resolution:duplicate
resolution:fixed
resolution:invalid
resolution:rejected
resolution:wontfix
success story
type:bug
type:bug
type:feature
type:question
type:question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/pikvm-pikvm#941
No description provided.