Vncserver On CentOS 7

Home » CentOS » Vncserver On CentOS 7
CentOS 9 Comments

I am trying to setup a CentOS 7.1 VNCserver

I cannot believe they went from a relatively easy process in 6 to the
“crazyness” that is 7.

I did the following:
yum install tigervnc-server
cp /lib/systemd/system/vncserver@.service
systemctl daemon-reload
edit /etc/systemd.system/vncserver@.service and replace
with myuser
su – myuser run VNCpassword to set password
systemctl enable VNCserver@.

Says its enabled:
systemctl list-unit-files | grep VNC
vncserver@.service enabled

using another machine to connect gives error about nothing there.

netstat -tuln | grep 5900
gives nothing.

What did I miss?



9 thoughts on - Vncserver On CentOS 7

  • I guess the problem is, that you don’t provide the instance name (the part after the @), the VNCserver server need this to configure the local X- display.

    See the Quick HowTo line in the service unit file

    regards Ulf

  • You should:

    cp /lib/systemd/system/vncserver@.service /lib/systemd/system/vncserver@:#.service

    Where # is the VNC port 590# to open. Like /lib/systemd/system/vncserver@:4.service to start a VNCserver on port 5904.

    Then use `systemctl start VNCserver@:4′ to start that VNC server. Remember to edit the /lib/systemd/system/vncserver@:4.service file’s as you did before.


  • OK – I redid and used the name VNCserver@:0.service

    Still not work –

    I then used 4 as in your example and it worked.

    How do I get port 5900 ?



  • Not sure why the didn’t work. I’ve never used 0. You could add -rfbport 5900 to the VNCserver parameters, or explicitly set the display value by replacing any %1 in the .service file with the display number preceded by a colon. e.g., ‘:0’.

    Note that if you are hosting any kvm VMs, a running vm might be grabbing the 5900 port. Which could explain why the :0 file name didn’t work.


  • Is there a way to make VNCserver on CentOS 7 to be read only?

    I want to allow someone to connect and see the screen- but not change it of course.



  • Add -AcceptPointerEvents=0 and -AcceptKeyEvents=0 to the VNCserver commandline in VNCserver@:#.service file, or on the Xvnc command line.