The server starts but in this case, unfortunately, I can't change any connection or other parameters. This choice will ensure that our VNC connection will be smooth and stable even on slower Internet connections.
The VNC server we will be using is TightVNC, a fast and lightweight remote control package.
When I run the vncserver command in the terminal, I can access this vnc server with my client and disconnect or connect the vpn without any problem in exchange of a password, which must mean that I have administrator privileges.īut when I run this vncserver command automatically with my system script that I created here: that I have filled in as follows: In this guide, we will be setting up VNC on an Ubuntu 14.04 server and connecting to it securely through an SSH tunnel. ls -la /.vnc/xstartup you should see the file is not executable. startxfce4 & If you have created a new file remember to make it executable. nano /.vnc/xstartup Add this new line to the bottem of the file. Okay, so I'll explain as simply as possible, with the translator this time. Now we can modify the /.vnc/xstartup file add the following to the end of the file.
The service is running and port 5901 is busy, but I can't access my system through a vnc viewer, but when I run a simple command line via ssh "vncserver:1" it works. The service starts and port 5901 is busy, but I can't access my system through a vnc viewer. My system : Ubuntu 22.04.2 LTS (GNU/Linux 5.19.0-32-generic x86_64)Īfter installing Tightvnc, I scrupulously followed the instructions to fill in a service file so that my vnc server restarts every time ubuntu starts (Recommendation from this site, and many other tests: ):ĭescription=Start TightVNC server at startupĮxecStartPre=-/usr/bin/vncserver -kill :%i > /dev/null 2>&1ĮxecStart=/usr/bin/vncserver -depth 24 -geometry 1280x800 -localhost :%i
0 kommentar(er)
