Skip to content

Connection issues

Most connection problems are local network issues or a missing username. Work through these in order.

  1. Check your local firewall / VPN. Corporate networks often block outbound 59010 (VNC) and sometimes 22 (SSH). This is the #1 cause. Try from a different network or a phone hotspot to confirm.
  2. Confirm the machine is up at status.myremotemac.com.
  3. Test each service separately:
    Terminal window
    nc -vz YOUR-IP 22 # SSH
    nc -vz YOUR-IP 59010 # VNC / Screen Sharing
    If SSH works but VNC doesn’t, it’s a VNC-client or port issue, not the machine being down.
  4. Double-check the IP, port and username from your welcome email / dashboard.

Logins are protected by fail2ban: 5 failed attempts within 10 minutes bans your IP for 1 hour, on both SSH and VNC. If nothing connects right after several failures:

  • Wait for the ban to expire (up to 1 hour), or connect from a different IP.
  • Fix the root cause first (username, port 59010, correct key) before retrying.
  • Need it lifted sooner? Contact support@myremotemac.com with your public IP.

See Security → Brute-force protection for the full rules.

  • Make sure your client uses macOS / Apple authentication (username + password), not legacy “VNC password”.
  • Try RealVNC Viewer or TigerVNC, which handle Apple auth automatically.
  • Confirm you’re on port 59010, not 5900.

If SSH works but the VNC desktop won’t connect, macOS Screen Sharing may have stopped, for example after an automatic macOS update. Connect over SSH and check it:

Terminal window
# 1. Is anything listening on the VNC port?
sudo lsof -nP -iTCP:59010 -sTCP:LISTEN
# 2. Is the Screen Sharing service loaded? Yes if the output starts with
# "system/com.apple.screensharing = {". "state = not running" is normal:
# launchd starts screensharingd only when a viewer connects.
sudo launchctl print system/com.apple.screensharing | head -n 5

If the port is listening but the desktop still won’t open, the screensharingd process may be stuck. End it: macOS starts a new one at your next connection.

Terminal window
sudo pkill screensharingd

If nothing is listening on 59010, or launchctl answers Could not find service, turn Screen Sharing back on:

Terminal window
sudo launchctl enable system/com.apple.screensharing
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.screensharing.plist

Then retry vnc://YOUR-IP:59010. If the desktop still won’t come up, restart the Mac with sudo shutdown -r now (with FileVault on, use sudo fdesetup authrestart, see below). If that doesn’t fix it, contact support.

If you’ve enabled FileVault, the disk stays locked after a reboot — the desktop (VNC) and normal login are unavailable until it’s unlocked. Unlock it over SSH first, or avoid the lock by rebooting with:

Terminal window
sudo fdesetup authrestart

On recent macOS you can unlock at the pre-login SSH prompt (password only — keys don’t work at that stage). Full details in FileVault & reboots.

  • The Mac may have gone to display sleep. Connect over SSH and wake it:
    Terminal window
    caffeinate -u -t 2
  • After a reboot, the login session may need a user to sign in — see Reboot & reset.

”Your screen is being observed” — is someone watching?

Section titled “”Your screen is being observed” — is someone watching?”

No. macOS shows that menu-bar indicator whenever Screen Sharing / Remote Management is active with a connected session — which is your own VNC connection. It is not a third party. Click the icon to see active sessions. Apple explains it here: support.apple.com/en-us/120315. More in Security.

  • Usually unstable local Wi-Fi/latency. Prefer a wired connection and lower the VNC quality (see Performance).
  • Keep an SSH session open in parallel; if SSH stays up while VNC drops, the network path is fine and it’s a VNC-client setting.