Re: [TurboVNC-Users] "Connection closed" immediately after connecting

[DRC]

I honestly have no experience with using networking within a Docker container, but it doesn't appear as if the VNC connection is actually reaching the TurboVNC Server instance running in the Docker container.  Seems like there may be something wrong with the network configuration in the container, or perhaps you are trying to connect to the host's IP address instead of the container's IP address (?)

The normal behavior of the TurboVNC Viewer, when attempting to connect to a non-existent server instance, is to display "Connection refused".  However, when attempting to connect to a non-existent server instance using SSH tunneling, "Connection closed" will be displayed instead (because the tunneled RFB connection is actually opened by the SSH server-- it is just immediately closed, because the server end of the tunnel is unable to connect to a VNC server.)

On 6/8/18 7:44 PM, Isolated wrote:

I'm trying to get started with TurboVNC 2.1.90 and not having much luck.

I set up a server in a Ubuntu Docker container:

FROM ubuntu

ENV DEBIAN_FRONTEND=noninteractive

RUN apt-get update && apt-get install --yes \

wget

# TurboVNC

RUN apt-get update && apt-get install --yes \

xauth \

x11-xkb-utils xserver-xorg-input-kbd \

xfonts-scalable xfonts-base xfonts-utils xfonts-encodings

RUN wget --no-verbose https://sourceforge.net/projects/turbovnc/files/2.1.90%20%282.2beta1%29/turbovnc_2.1.90_amd64.deb/download

RUN dpkg --install download

# XEyes

RUN apt-get update && apt-get install --yes \

x11-apps

ENV DISPLAY=:1

When I run the container I publish the port 5091 locally.  I then start the server with this command:

root@9760477184e8:/# /opt/TurboVNC/bin/vncserver -securitytypes tlsnone,x509none,none -xstartup xeyes

xauth:  file /root/.Xauthority does not exist

Desktop 'TurboVNC: 9760477184e8:1 ()' started on display 9760477184e8:1

Starting applications specified in xeyes

Log file is /root/.vnc/9760477184e8:1.log

I try to connect via the TurboVNC client on macOS and after connection it immediately displays "Connection closed" with no other information.

Here's the contents of the log:

root@9760477184e8:/# cat /root/.vnc/9760477184e8:1.log

TurboVNC Server (Xvnc) 64-bit v2.1.90 (build 20180522)

Copyright (C) 1999-2018 The VirtualGL Project and many others (see README.txt)

Visit http://www.TurboVNC.org for more information on TurboVNC

09/06/2018 00:39:41 Using auth configuration file /etc/turbovncserver-security.conf

09/06/2018 00:39:41 Enabled authentication method 'tlsnone'

09/06/2018 00:39:41 Enabled authentication method 'x509none'

09/06/2018 00:39:41 Enabled authentication method 'none'

09/06/2018 00:39:41 Desktop name 'TurboVNC: 9760477184e8:1 ()' (9760477184e8:1)

09/06/2018 00:39:41 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t

09/06/2018 00:39:41 Listening for VNC connections on TCP port 5901

09/06/2018 00:39:41   Interface 0.0.0.0

09/06/2018 00:39:41 Listening for HTTP connections on TCP port 5801

09/06/2018 00:39:41   URL http://9760477184e8:5801

09/06/2018 00:39:41   Interface 0.0.0.0

09/06/2018 00:39:41 Framebuffer: BGRX 8/8/8/8

09/06/2018 00:39:41 New desktop size: 1240 x 900

09/06/2018 00:39:41 New screen layout:

09/06/2018 00:39:41   0x00000040 (output 0x00000040): 1240x900+0+0

09/06/2018 00:39:41 Maximum clipboard transfer size: 1048576 bytes

09/06/2018 00:39:41 VNC extension running!

It looks like xeyes is running successfully:

root@9760477184e8:/# ps

  PID TTY          TIME CMD

    1 pts/0    00:00:00 bash

   20 pts/0    00:00:00 Xvnc

   30 pts/0    00:00:00 xeyes

   34 pts/0    00:00:00 ps

How can I debug this?

Thanks,
Isolated

--
You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turbovnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/20172298-062c-4980-8bb1-8a120304f031%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Isolated]

Thank you for taking the time to consider my problem; I appreciate it.

After a lot of sleuthing I discovered that another program had corrupted my /etc/hosts file and localhost was no longer resolving to 127.0.0.1.  Everything is working fine now and I'm very happy with TurboVNC.  It's fine software—my hat is off to you sir!