veyon service unreachable or not running

[Bielet]

@hammergil I think the problem is the port 11100 in Ubuntu. This is the port that Veyon listen the petitions from the master.

Does anyone know how to properly open port 11100 in Ubuntu so that it listens for Veyon requests?

Thanks.

[kamik]

@bielet I don't know veyon in ubuntu, but you can check listening ports and a firewall.

sudo netstat -latupn

it shows all open ports and processes - check port 11100

sudo ufw status

it shows status of the firewall

[Bielet]

@kamik said in veyon service unreachable or not running:

@bielet I don't know veyon in ubuntu, but you can check listening ports and a firewall.

sudo netstat -latupn

it shows all open ports and processes - check port 11100

sudo ufw status

it shows status of the firewall

Trying sudo netstat -latupn, Indeed, the client's veyon does not seem to open the port, it is not in the list of ports ...

The firewall is down, so no restrictions should be applied.

I have tried stopping and restarting the service from the Veyon configurator and it still does not listen to port 11100

[kamik]

@bielet is the veyon service really running?

sudo systemctl status veyon

you should check logs:
systemd logs: sudo journalctl -eu veyon.service
veyon logs should be in /tmp folder, depends on your config

[Bielet]

@kamik

It seems a problem with wayland. I am using Ubuntu 18.04.5 LTS

[Bielet]

@bielet I have tried adding -noshm at VNC configuration, but the service keeps stopping

[kamik]

@bielet Do you need wayland ? Try run with Xorg.

https://www.youtube.com/watch?v=8PxjgKyyrO0

wayland is probably still unsupported

[hammergil]

@kamik
It is a false message. Wayland is not running. Mine says the same thing and a check shows that the session is Xorg

[Bielet]

@kamik

It says that i'am using x11

[tobydox]

The Wayland messages could come from your display manager which already uses Wayland while your user sessions don't. However from your descriptions it rather sounds like the Veyon Server inside the user sessions starts up properly and during the first access. Is there a chance you can downgrade to 4.5.6 by manually installing https://github.com/veyon/veyon/releases/download/v4.5.6/veyon_4.5.6-0-ubuntu-focal_amd64.deb (if it doesn't help, try with 4.5.5 via https://github.com/veyon/veyon/releases/download/v4.5.5/veyon_4.5.5-0-ubuntu-focal_amd64.deb)? This way we can determine whether this is a regression or a general problem.

@hammergil I admit the (free community) support has been poor in the last weeks to due holidays (also the development of Veyon 5 takes quite some resources). I'm confident we'll fix the Ubuntu issue in the next weeks, even though you seem to have found another solution.

[dashohoxha]

@tobydox I have the same problem with LinuxMint (which is based on Ubuntu 20.4). The service veyon seems to be running properly, but telnet localhost 11100 says Unable to connect to remote host: Cannot assign requested address, and the message on the Master "veyon service unreachable or not running".

The same problem happened with version 4.3.1 which is the one packaged on ubuntu-20.04, and the same happens with the latest release downloaded from veyon.io.