Fix a Connection That Will Not Start
A session will not open or the host shows offline? Work through these checks in order to get connected again. No VPN or port-forwarding needed.
If a session will not open, or a host shows as offline, work through these checks in order. Most connection problems come down to the host being unreachable or the two devices not being on the same account. RealFrame needs no VPN and no port-forwarding, so you can skip router and firewall changes while you troubleshoot.
1. Confirm the host is online
On the host computer:
- It is powered on and awake (not asleep or hibernating).
- It is connected to the internet.
- The RealFrame host app is running. It should start on its own, but open it to be sure.
If the host shows offline in your client, this is almost always the cause.
2. Check you are on the same account
The client only sees hosts that belong to the same RealFrame account.
- Sign out and back in on the client.
- Confirm the email address matches the one used on the host.
3. Check both internet connections
- Open a website on the host and on the client to confirm each has working internet.
- If you are on a restrictive corporate or guest network, it may block the connection. Try a different network, such as a phone hotspot, to see if that is the cause.
4. Approve the pairing code
If the connection starts but never finishes, you may have a pending pairing request.
- Look for a 6-digit code on both devices and approve it.
- See pair devices with a code for the full steps.
5. Restart the apps
- Quit and reopen the client, then try again.
- Quit and reopen the host, then try again.
- If the host machine has been up for a long time, a reboot can clear a stuck state.
6. Update to the latest version
- Make sure both the host and the client are on the latest version. A large version mismatch can prevent a session from opening.
7. Self-host: confirm the service address
If you self-host, also check:
- The server address in both apps points at your coordination service.
- The service is running and reachable.
- The TLS certificate has not expired.
See self-host setup for details.
Still stuck?
Note what you have already tried, the operating systems involved, and any message you saw, then reach out to RealFrame support so we can help.