Source: websockify
Severity: important
Tags: newcomer
Dear Maintainer,
* What led up to the situation?
When installing python3-websockify or websockify v0.8.0
NoVNC won't be able to connect to a VNC Server (e.g. x11vnc).
x11vnc prints following errors when novnc tries to connect:
"code 400, message Client must support 'binary' or 'base64' protocol"
"code 405, message Method Not Allowed"
But this behavior is already fixed in v0.9.0 upstream.
(Probably because Base64 support was removed and binary mode is now
required)
* What exactly did you do (or not do) that was effective (or
ineffective)?
Just installing from upstream sources (v0.9.0) websockify
Thank you!
-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
