Failed to connect to localhost:5901 errno 111, connection refused

59 views
Skip to first unread message

Martine & Philippe vont à la mer Martineke

unread,
Dec 8, 2024, 10:29:21 AM12/8/24
to noVNC
hello
under debian, after an installation by copying from github, the proxy is ok, the vnc.html page works, but the connection to the VNC server (realVNC) is in failure for error 111, connection refused.
i did not have time to enter an identification and password, and i did not find in the preference button what to enter an identifier and password before launching the connection.
a connection with a traditional vnc client works.
thanks

Martine & Philippe vont à la mer Martineke

unread,
Dec 8, 2024, 6:07:21 PM12/8/24
to noVNC
well the listening port is in 5900.
when restarting, there is no more error on the terminal side, but the web page indicates connection failure...

Pierre Ossman

unread,
Dec 9, 2024, 6:32:52 AM12/9/24
to no...@googlegroups.com, Martine & Philippe vont à la mer Martineke
On 09/12/2024 00:07, Martine & Philippe vont à la mer Martineke wrote:
> well the listening port is in 5900.
> when restarting, there is no more error on the terminal side, but the web
> page indicates connection failure...
>

Are you perhaps specifying port 5900 directly to noVNC? The port given
to noVNC needs to be the port of the proxy. And the port 5900 needs to
be given to the proxy instead.

Regards,
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Martine & Philippe vont à la mer Martineke

unread,
Dec 9, 2024, 7:15:04 AM12/9/24
to noVNC
Hello

i used ./utils/novnc_proxy --vnc localhost:5900

i got : proxying from 6080 to localhost:5900
and during connection : my client IP : Path 'websockify' connecting to localhost:5900

i saw a debug mode into vnc.html.
where is the file, or how to catch debug informations?

greetings

Pierre Ossman

unread,
Dec 9, 2024, 7:16:48 AM12/9/24
to no...@googlegroups.com, Martine & Philippe vont à la mer Martineke
On 09/12/2024 13:15, Martine & Philippe vont à la mer Martineke wrote:
> Hello
>
> i used ./utils/novnc_proxy --vnc localhost:5900
>
> i got : proxying from 6080 to localhost:5900
> and during connection : my client IP : Path 'websockify' connecting to
> localhost:5900
>

Sounds like it is almost there. Please change the port setting in
noVNC's GUI to 6080 and it should hopefully work just fine.

> i saw a debug mode into vnc.html.
> where is the file, or how to catch debug informations?
>

It is in the browser console log. Note that the browser might be
filtering debug messages per default.

Martine & Philippe vont à la mer Martineke

unread,
Dec 9, 2024, 7:40:04 AM12/9/24
to noVNC
well
with the console :
Screenshot 2024-12-09 13.37.53.png
is it just coz no https?

greetings

Pierre Ossman

unread,
Dec 9, 2024, 9:36:27 AM12/9/24
to no...@googlegroups.com, Martine & Philippe vont à la mer Martineke
On 09/12/2024 13:40, Martine & Philippe vont à la mer Martineke wrote:
> well
> with the console :
> [image: Screenshot 2024-12-09 13.37.53.png]
> is it just coz no https?
>

We are progressing. It can now talk to the VNC server.

The issue is not HTTPS, no. Although that might give issues later on, so
it would be good to enable that.

Security type 262 is TLS encryption with Plain authentication.
Unfortunately, we don't support VNC's TLS extensions. You'll need to
configure your VNC server without that.

Martine & Philippe vont à la mer Martineke

unread,
Dec 10, 2024, 3:02:38 AM12/10/24
to noVNC
Ok
many thanks !

Reply all
Reply to author
Forward
0 new messages