Why is VNC Server not currently listening for Cloud connections?

Follow

VNC Server should be functioning correctly if there is a green tick (and no error messages) displayed in its Status dialog:

faq-troubleshooting.png

If, however, you are unable to connect and VNC Viewer displays the error message "VNC Server is not currently listening for Cloud connections" when you try to connect, please check the following:

  1. Check there are no service issues on the RealVNC status page.
  2. Check that the remote computer is connected to the Internet. If it isn't, you won't be able to connect.
  3. It may be that the remote computer is asleep. It is advisable to prevent a remote computer sleeping or hibernating while remote access is required:
    • Windows: In Control Panel > Power Options > Change when the computer sleeps, make sure Put the computer to sleep when plugged in is Never.
    • Mac: In System Preferences > Energy Saver, make sure Prevent computer from sleeping automatically when the display is off is selected.
  4. If you have disabled cloud connections in VNC Server's Options dialog, under the Connections heading. Make sure this is checked:
    allowcloud.PNG
  5. You may have the wrong team selected in VNC Viewer. Please ensure you have selected the correct team for the computer to which you want to connect.
  6. If you have purchased a subscription but did not subscribe from within your trial team, you will need to join your computer(s) to the new, paid-for team.
  7. Ensure that you also see your computer's name, and your Team name, listed in the Connectivity section. If you don't please re-join it as shown here: How do I rejoin a VNC Server to the cloud, or change which team VNC Server belongs to?

    Note: you may need to remove the existing entry using the Computers page of the online portal first.

  8. If you are trying to connect to VNC Server on Linux, check that Wayland is disabled
  9. Try restarting VNC Server and/or the computer running VNC Server.

    • In Windows, this can be done via the Services utility, accessible by searching for services.msc in the Start Menu.
    • For Mac/Linux, right click the VNC Server icon in the system tray (by the clock), and click Stop VNC Server. Then, launch VNC Server from your Applications menu.

If none of the above steps help, you can also check for the underlying error message by looking at the log files for VNC Server. These can be accessed by opening the VNC Server app and going to the Options section. Next, go to the Troubleshooting section, then click Show in folder.

If you do not have access to the VNC Server GUI, the log files can be found in the following locations instead:

  • Windows: C:\ProgramData\RealVNC-Service\vncserver.log and C:\ProgramData\RealVNC-Service\vncserver.log.bak
  • Mac: /Library/Logs/vncserver.log and /Library/Logs/vncserver.log.bak
  • Linux: /var/log/vncserver-x11.log and /var/log/vncserver-x11.log.bak

Once you have opened the logs, check for any of the error messages listed here: VNC Connect Error Messages

If you still have problems, and your subscription includes access to technical support, please submit a support request. Please attach the VNC Server diagnostics (VNC Server > Information Center > Diagnostics > Save As...) and log files (above) from VNC Server.

Was this article helpful?
1318 out of 1757 found this helpful

Comments

2 comments
  • The energy saver setting "Put the computer to sleep when plugged" doesn't seem to exist in mac os 13.1. Please advise.

    0
    Comment actions Permalink
  • You can also get the underlying reason for the issue (the "real" error message) by looking at the log files:

    VNC Server
    Open VNC Server's Options and go to the Troubleshooting section, then click Show in folder.

    If you do not have access to the VNC Server GUI, the log files can be found in the following locations instead:

    Windows: C:\ProgramData\RealVNC-Service\vncserver.log and C:\ProgramData\RealVNC-Service\vncserver.log.bak

    Mac: /Library/Logs/vncserver.log and /Library/Logs/vncserver.log.bak

    Linux: /var/log/vncserver-x11.log and /var/log/vncserver-x11.log.bak

    I got this tip from Jack!

    0
    Comment actions Permalink

Please sign in to leave a comment.