Hi guys! It looks like https://docs.fedoraproject.org/en-US/Fedora/24/html/System_Administrators_Guide/ch-TigerVNC.html is a bit out of date. The service changed the way it starts, it now requires two changes: User=MY_USER PIDFile=/home/MY_USER/.vnc/%H%i.pid I also suggest to add Troubleshooting section: A) When VNC server does not start, check status of the service (systemctl status), system journal or SELinux denials. (I recently filed a bug 1383088 for Fedora 24 on that topic) B) TigerVNC enforces encryption when using password authentication. Some clients (outdated or MacOS built-in Shared Screen application) won't be able to connect.
Thank you for raising this bug. I will test and update accordingly.
(In reply to Lukas Zapletal from comment #0) > Hi guys! > > It looks like > > https://docs.fedoraproject.org/en-US/Fedora/24/html/ > System_Administrators_Guide/ch-TigerVNC.html > > is a bit out of date. The service changed the way it starts, it now requires > two changes: > > User=MY_USER > PIDFile=/home/MY_USER/.vnc/%H%i.pid > and the instructions in the file [1] do not tell you to replace <user> with a valid user. I can clone this bug for that. [1] /lib/systemd/system/vncserver@.service