This method will only work if you have set your Pi to automatically log into the desktop environment. See Lesson 2.

Connecting to your Raspberry Pi remotely with VNC is fine as long as your Pi does not reboot. If it does, then you either have to connect with SSH and restart the VNC Server or arrange for the VNC Server to run automatically after the Raspberry Pi reboots.

There are several different methods of arranging for some code to be run as the Pi starts. The method described below is probably the easiest to use. You can adapt it to run other commands instead of starting the VNC server.

Step 1.

Open a Terminal session on the Pi, or connect using SSH. A new terminal or SSH session will automatically start you off in your home directory of /home/pi. If you are not in this directory, change to it by typing:

$ cd /home/pi

Then cd to the .config directory by typing:

$ cd .config

Note the '.' at the start of the folder name. This makes it a hidden folder that will not show up when you type 'ls'.


Step 2.

Issue the command below to create a new directory inside .config called 'autostart'.

$ mkdir autostart

cd into that new directory by typing:

$ cd autostart

Step 3.

All that remains is to edit a new configuration file. So type the following command to open the nano editor on the new file:

$ nano tightvnc.desktop

Edit the contents of the file with the following text.

[Desktop Entry]
Type=Application
Name=TightVNC
Exec=vncserver :1
StartupNotify=false

Type ctrl-X and then Y to save the changes to the file.

Thats all there is to it. The next time you reboot the VNC server will restart automatically.

This guide was first published on Dec 21, 2012. It was last updated on Jan 02, 2013.

This page (Running VNCServer at Startup) was last updated on Jan 02, 2013.

Text editor powered by tinymce.