Veyon Community Forum

Hello Tobydox I now know the problem of error 87 ... but I don't know how to solve it yet ... the error occurs if I am connected in RDP on the machine on which I am installing Veyon. if I am physically connected to the machine no more error 87 problem. From the information I could read, this is related to graphics driver problem ... But you have necessarily done something about the graphics settings since until version 4.5.4.3 this does not pose a problem in RDP. Fred

@drewloker said in 4.4.2 - Downgrade options? CRASHES Master and Clients, No Demo: Demo still doesn't work. I brought the whole lab up to 4.5.4.0 It went to Demo, showed my screen for a few second on a couple of the 7 students logged in a lab of 26 clients. Then, Demo stopped working even on the couple that did get my screen. I was able to back out of Demo mode with out crashing their computer. Hello i have the same problem .. i opened a new topic: https://veyon.nodebb.com/topic/1258/veyon-4-5-4-vnc-serveur-crash-on-demo-mode where I put the logs to see if tobydox manages to understand what is wrong ... Fred

Hello, I am struggling to get veyon-server to start up automaically at the login screen of Ubuntu 20.04 before any user logs in. I am using the lightdm Display Manager and latest veyon from the ubuntu ppa. We have the ubuntu Desktop Environment for local use and the xfce Desktop Environment for use via RDP. So, once I am inside any user session and run the "veyon-server" command from a terminal, the veyon server starts and establishes a proper connection with the veyon master. Before and after that, I just see the orange screen... I have searched quite a while now and found several related posts to this topic, but this seems to be the newest one. Please tell me if I should post any logs or where I could check proper configuration. Thank you in advance. [image: 1644590495609-veyon-l%C3%A4uft-nicht.png]

@Carlo That solution isn't good in my case, because I'm not always present in the laboratory and I can't always log the students.

The version 4.8.0.4 have resolved the problem of black screen. But I realised that we can not login a session for multiple computers. Is there a bug for this function too?

Can you try to upgrade both clients and master to 4.2 RC (4.1.92) to see if the problem still persists?

@tobydox said in Veyon 4.5.1 I can't open website from Master: Some technical background: first you should make sure the tray icon is visible on all computers. If it's not visible, the Veyon Service for some reason is not able to run it's own worker processes within the user session. The Veyon tray icon is provided by such a worker process. Launching the "Run program" or "Open website" features also launches a (different) worker process inside the user sessions as a helper process. This worker will then start the program or open the website and this way make sure the program or browser is opened with user privileges (instead of Admin/LocalSystem privileges which the Veyon Service is running with). On computers where the tray icon is not visible, can you please check the VeyonServer.log file for messages starting with WindowsCoreFunctions and post them here? Veyonserver.log https://pastebin.com/Z4bGjPd0 VeyonService.log https://pastebin.com/BH1And2t

Any news here?

@jrpfahl Try turning off the Windows Defender Firewall (Domain Network) for one of the Windows 10 computers and try again.

I'm sorry, no good news: [image: 1581490882199-veyon_service.png]

I don't know if this helps ... but when I start "veyon-server" as a login-Script I get this message: [image: 1621874370270-screenshot_20210524_183807.png]

@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.

I am having this same issue. I used Veyon 4.4.1 and now I get the C++ Runtime error. The master PC is Windows 7.

0 I want to install Veyon on the RPi4. I have read about Debian packages and the instructions. I had a look in my /etc/apt/sources.list and it had an entry for buster, so I added the line for Veyon Buster: deb http://ppa.launchpad.net/veyon/stable/ubuntu bionic main I then tried to run the command sudo add-apt-repository ppa:veyon/stable. .

@tobydox I just updated to version 4.1.4. indeed the problem was solved. Thank you!!

@tobydox No problem, you can't be on dev and forum at the same time Your job is really helpful for a lot of people, thanks for that. I'd like to be more useful here on the forum, but not "good" enough yet with veyon to help much people. Regards ET

@MackenzieP A tech at a neighboring school advised that rather than entering IP addresses into the Configurator’s Host address/IP field (Locations & computers) to instead enter computer names. A bit confusing to me but he said to make the Host address/IP field match the Name field when using DHCP assigned addresses.

@tobydox nice. This solved an issue I've been struggling with for quite q few days:) thanks!

Hi @fra-sa @esaurel In one lab, I finished updating all my clients to Veyon 4.8.2, and for some students, the issue is still present. At this very moment, the lab is wired with both the Windows 10 x64 master and student computers connected at 1 GB/s. I opened an issue on github here: https://github.com/veyon/veyon/issues/895. In the meantime, hitting F5 refreshes the correct student status. Have a good day.

I think a central install on a server where teachers get permissions to manage a classroom would be (especially from an admin point of view) highly preferable.