VNC behaves oddly when monitor unplugged

**richardi99** · May 24th, 2020

I have an Intel NUC with the latest version of Ubuntu installed. I have VNC server running on it to allow remote access, because I want to rackmount the NUC without direct-attached KVM and use it as a headless server. Want to VNC in when I need to.

I can connect fine remotely, and control the NUC, until I unplug its HDMI monitor cable. As soon as I do that I can only view, and cannot remotely control.
Can anyone help me with this please?

**richardi99** · May 25th, 2020

Ok - so moved forwards one step. Discovered I need to buy an HDMI monitor emulator. to plug into the HDMI port. Done that. Now cannot seem to get VNC to start up at boot so I can VNC into this as a headless NUC. Have tried two things with no luck: https://tecadmin.net/setup-x11vnc-se...ntu-linuxmint/ and https://tecadmin.net/setup-x11vnc-se...ntu-linuxmint/. Any help appreciated

**Tadaen_Sylvermane** · May 25th, 2020

You don't need that. Can be done without it.

https://askubuntu.com/questions/4531...-is-plugged-in

I used this to run Kodi inside an LXD container on my headless server. Works great. X11VNC and away you go.

Systemd service to restart x11vnc after you exit it. I use for above purpose, rather I did until I changed to another service + script to stream audio out of the container to a remote pulse server. Change user & group as needed.

Code:

[Unit]
Description = Start and keep X11VNC server running

[Service]
User = kodi
Group = kodi
Type = simple
ExecStart = /usr/bin/x11vnc -display :0
Restart = always

[Install]
WantedBy = multi-user.target

In regards to VNC starting on boot you need something for it to connect to. In my container I have LightDM set to autologin to my kodi user on openbox, which autostarts Kodi. Using lightdm have it autologin to your user and that is it. The above service will keep the vnc server running.