Differences

This shows you the differences between two versions of the page.

--- infrastructure:vnc [2021/12/09 09:38] – created pmania
+++ infrastructure:vnc [2022/04/13 13:18] (current) – [Vncviewer after Reboot] s_fuyedc
@@ Line 1: / Line 1: @@
+======Setting up VNC for Remote Desktop access======
 This page describes methods that lets you connect remotely to the graphical interface of a machine.
 The main assumption here is, that we want to get the actual output of the graphics card, so basically everything that you would see on the screen of the PC. This has the benefit that you can also use the remote desktop for 3D applications like Unreal which are based on vulkan, but is a bit more intense on your network connection.
@@ Line 95: / Line 97: @@
 The next steps will be done on your client machine.
-VNC itself comes per default without any encryption. This is why we'll create a SSH tunnel to the remote machine and pipe the whole VNC traffic through it.
+VNC itself comes per default without any encryption. This would mean that your keypresses and the screen could be sniffed. This is why we'll create a SSH tunnel to the remote machine and pipe the whole VNC traffic through it.
 Please go to your client machine and execute the following command to create the SSH tunnel and start the VNC server on the remote machine.
@@ Line 110: / Line 112: @@
 sudo apt-get update
 sudo apt-get install tigervnc-viewer
+vncviewer
 </code>
 In the tigervnc-viewer, first open the options and set the compression to 'auto'.
-Afterwards, you can enter 'localhost' in the connection dialog and hit Connect.
+Afterwards, you can enter '**localhost**' in the connection dialog and hit Connect.
+Please note: Please __do not__ enter the IP address of your remote machine here, but really 'localhost'. This works, because we have a SSH tunnel running (see above).
+**Important: Once after every reboot, a user must log in to the server on site, because the virtual display is only launched after the first user's login.** This is similar to the 18.04 method mentioned above.
+====Vncviewer after Reboot====
+Tested with GDM3 (20.04 default display manager).
+After reboot the desired display :1 is not loaded until you logged in on display :0. We need to connect to display :0 once after rebooting. With x11vnc you can easily open :0. A newly set-up system needs one UI login to establish general display settings.
+<code>
+# on the remote machine
+sudo apt-get update
+sudo apt-get install x11vnc
+</code>
+Get onto the remote machine and look for the Xauthority file in /run/user/
+<code>
+# on the remote machine
+sudo find /run/user/ -name Xauthority
+</code>
+This will yield at least two paths, one with a 4-digit named directory, and another with 3 digits. We need the path with 3-digits. Now from the client you can launch x11vnc similar to the x0vncserver. Specify the path to Xauthority and replace '125' with yours.
+<code>
+# on your client machine
+ssh USERNAME@REMOTE.SERVER.IP -t -t -L 5900:localhost:5900 \
+  "sudo x11vnc -display :0 -auth /run/user/125/gdm/Xauthority"
+</code>
+Connect to x11vnc with vncviewer, it will show the login display :0. After login, close the connection  and use x0vncserver to launch display :1.