VNC works but not Xorg

[PeeBeerBeach]

I can use this docker through VNC. But whenever i try to login via Xorg the screen stays blank for a long time and then get "connection problem giving up" on the client, so a timeout of some kind.

I remarked that there seems to be a problem with the sshd service in the logs of the docker. I am running the docker in host mode and remap port 22 to 2222:

` 2020-05-25 23:04:09,459 CRIT Supervisor running as root (no user in config file) 2020-05-25 23:04:09,460 INFO Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing 2020-05-25 23:04:09,460 INFO Included extra file "/etc/supervisor/conf.d/xrdp-sesman.conf" during parsing 2020-05-25 23:04:09,460 INFO Included extra file "/etc/supervisor/conf.d/xrdp.conf" during parsing 2020-05-25 23:04:09,514 INFO RPC interface 'supervisor' initialized 2020-05-25 23:04:09,515 CRIT Server 'inet_http_server' running without any HTTP authentication checking 2020-05-25 23:04:09,516 INFO RPC interface 'supervisor' initialized 2020-05-25 23:04:09,516 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2020-05-25 23:04:09,517 INFO supervisord started with pid 1 2020-05-25 23:04:10,524 INFO spawned: 'xrdp-sesman' with pid 18 2020-05-25 23:04:10,531 INFO spawned: 'sshd' with pid 19 2020-05-25 23:04:10,536 INFO spawned: 'xrdp' with pid 20 2020-05-25 23:04:10,616 INFO exited: sshd (exit status 255; not expected) 2020-05-25 23:04:11,618 INFO success: xrdp-sesman entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-05-25 23:04:11,621 INFO spawned: 'sshd' with pid 22 2020-05-25 23:04:11,622 INFO success: xrdp entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-05-25 23:04:11,655 INFO exited: sshd (exit status 255; not expected) 2020-05-25 23:04:13,660 INFO spawned: 'sshd' with pid 24 2020-05-25 23:04:13,696 INFO exited: sshd (exit status 255; not expected) 2020-05-25 23:04:16,703 INFO spawned: 'sshd' with pid 25 2020-05-25 23:04:16,741 INFO exited: sshd (exit status 255; not expected) 2020-05-25 23:04:17,743 INFO gave up: sshd entered FATAL state, too many start retries too quickly

`

[danielguerra69]

That is correct behavior because this is not a VNC server, but a RDP server. You need a RDP client instead of VNC

[PeeBeerBeach]

That is correct behavior because this is not a VNC server, but a RDP server. You need a RDP client instead of VNC

I believe we have a misunderstanding here.

I am using Windows 10 remote dekstop, so an RDP client. Still when i connect i can chose between Xorg and Xvnc. Xorg does not work as described above.

[danielguerra69]

Sorry there is no vnc in this container. I use xorgxrdp

[danielguerra69]

On windows 10 use windows remote desktop that never asks for vnc

[PeeBeerBeach]

I am in fact using windows remote desktop as you suggest. I know this client cannot operate with the VNC protocol but uses the RDP protocol. I get an RDP connection to my machine and your docker, then get presented with the login screen. Here i can chose between Xord or Xvnc. No idea how this works but it is the case. I thought you would know.

Here is some proof:

[danielguerra69]

In the windows RDP client use user: "ubuntu" with the password "ubuntu" (remove the quotes). I get your second screen when login went wrong. And next time rtfm :) (README)

[PeeBeerBeach]

Sorry i read about the ubuntu/ubuntu user but was not clear that i need to use this on the window end. I did that now and it does not change anything on behaviout at all. Still get to the Linux login prompt. Still have the Xvnc option and Xorg does not work. sigh i guess something is screwed up here a bit more deep down.