Texas-Mark wrote:I have read the whole thread and am having a similar problem (I think). In my case, when I enable RealVNC to auto start from the Raspberry Pi Configuration - Interfaces menu, I get the VNC icon, but the server does not actually auto start even though it says ready for connections. I can still manually start it from the terminal with "vncserver :1" and then it works fine. It's just the auto start that is not working. I have tried some of the fixes in this thread, but nothing seems to work. I have the latest updates for everything and don't really have anything odd installed. Any ideas?
Never mind. It seems that you have to use <ip address>:0 if auto start is on, instead of <ip address>:1 to connect when VNC is manually started.
Note: When I was setting up RealVNC, I had read to use "vncserver :1" and so that is what I had been doing and had set up the viewer to connect to <ip address>:1 so it was failing because auto start expects <ip address>:0
What you have here is two different things.
When you enable VNC from the Raspberry Pi configuration, you're enabling the RealVNC Service mode server. This is designed to allow access to the console display (in other words, what you see on the monitor), and runs on display :0 by default. Hence you use <ip-address>:0 or simply <ip-address> in your viewer to connect to it.
When you run the vncserver
command, you're actually staring a new VNC Virtual mode server, which is a separate desktop that you access via VNC. This will use the next available display number, starting with :1 (since you can run multiple virtual desktops).
A lot of tutorials that you'll read online are confusing these two modes, but which one to use really depends on what you are doing. The advantage of service mode is that you can run applications that require the GPU, for example Minecraft or Kodi (assuming you enable "experimental direct capture mode" in the VNC Server options). Virtual mode makes more sense when you only occasionally want to run graphical applications on a headless machine.