Skip to main content
added 353 characters in body
Source Link
apathos
  • 123
  • 1
  • 1
  • 6

I have a Raspberry Pi B running a fresh install of PIXEL that I'm trying to connect to headless, within my own network. When I connect with a monitor, I have no issues - I can use RealVNC viewer from another device perfectly.

But when I restart the device headless, I cannot connect. Specifically I get an error: "The connection was refused by the host computer". I have created a virtual desktop using the instructions at VNC, but I cannot connect.

Again, plugging the same device with no changes into a monitor lets me log in from ANY remote device on the network. Shutdown, restart without monitor - connection refused.

Also noted, I can ssh in at any time. If I ssh in and run 'vncserver', I can then connect vncviewer headless. I take this to mean that vncserver is not starting up automatically when headless? I have followed the instructions at this page for setting up VNC server. Step 2 states, "From now on, VNC Server will start automatically whenever your Pi is powered on." I apparently am not observing this behavior.

Also related - when I am able to connect headless after ssh'ing in, if I close the connection and let the device idle for some undetermined length of time (hours), the whole process starts over again.

I'd really love some advice for this.

EDIT to add: I also tried the steps at https://www.realvnc.com/docs/raspberry-pi.html#raspberry-pi-ssh, running sudo systemctl start vncserver-x11-serviced.service and then sudo systemctl enable vncserver-x11-serviced.service This has also not had the desired effect.

I have a Raspberry Pi B running a fresh install of PIXEL that I'm trying to connect to headless, within my own network. When I connect with a monitor, I have no issues - I can use RealVNC viewer from another device perfectly.

But when I restart the device headless, I cannot connect. Specifically I get an error: "The connection was refused by the host computer". I have created a virtual desktop using the instructions at VNC, but I cannot connect.

Again, plugging the same device with no changes into a monitor lets me log in from ANY remote device on the network. Shutdown, restart without monitor - connection refused.

Also noted, I can ssh in at any time. If I ssh in and run 'vncserver', I can then connect vncviewer headless. I take this to mean that vncserver is not starting up automatically when headless? I have followed the instructions at this page for setting up VNC server. Step 2 states, "From now on, VNC Server will start automatically whenever your Pi is powered on." I apparently am not observing this behavior.

Also related - when I am able to connect headless after ssh'ing in, if I close the connection and let the device idle for some undetermined length of time (hours), the whole process starts over again.

I'd really love some advice for this.

I have a Raspberry Pi B running a fresh install of PIXEL that I'm trying to connect to headless, within my own network. When I connect with a monitor, I have no issues - I can use RealVNC viewer from another device perfectly.

But when I restart the device headless, I cannot connect. Specifically I get an error: "The connection was refused by the host computer". I have created a virtual desktop using the instructions at VNC, but I cannot connect.

Again, plugging the same device with no changes into a monitor lets me log in from ANY remote device on the network. Shutdown, restart without monitor - connection refused.

Also noted, I can ssh in at any time. If I ssh in and run 'vncserver', I can then connect vncviewer headless. I take this to mean that vncserver is not starting up automatically when headless? I have followed the instructions at this page for setting up VNC server. Step 2 states, "From now on, VNC Server will start automatically whenever your Pi is powered on." I apparently am not observing this behavior.

Also related - when I am able to connect headless after ssh'ing in, if I close the connection and let the device idle for some undetermined length of time (hours), the whole process starts over again.

I'd really love some advice for this.

EDIT to add: I also tried the steps at https://www.realvnc.com/docs/raspberry-pi.html#raspberry-pi-ssh, running sudo systemctl start vncserver-x11-serviced.service and then sudo systemctl enable vncserver-x11-serviced.service This has also not had the desired effect.

Source Link
apathos
  • 123
  • 1
  • 1
  • 6

RealVNC Viewer connection refused when headless

I have a Raspberry Pi B running a fresh install of PIXEL that I'm trying to connect to headless, within my own network. When I connect with a monitor, I have no issues - I can use RealVNC viewer from another device perfectly.

But when I restart the device headless, I cannot connect. Specifically I get an error: "The connection was refused by the host computer". I have created a virtual desktop using the instructions at VNC, but I cannot connect.

Again, plugging the same device with no changes into a monitor lets me log in from ANY remote device on the network. Shutdown, restart without monitor - connection refused.

Also noted, I can ssh in at any time. If I ssh in and run 'vncserver', I can then connect vncviewer headless. I take this to mean that vncserver is not starting up automatically when headless? I have followed the instructions at this page for setting up VNC server. Step 2 states, "From now on, VNC Server will start automatically whenever your Pi is powered on." I apparently am not observing this behavior.

Also related - when I am able to connect headless after ssh'ing in, if I close the connection and let the device idle for some undetermined length of time (hours), the whole process starts over again.

I'd really love some advice for this.