Cloud desktop not connecting

Most connection failures come down to one thing: the instance isn't running. Open the cloud desktops list, check the status shown next to your instance, and follow the section below that matches what you see.

Instance is stopped

If the status shows Stopped, the instance hasn't booted yet. Start it from MultiClaw Cloud, then wait for it to reach Online status before clicking Connect in the desktop app.

Instance is in Error state

An Error status usually means something went wrong during provisioning. Try restarting the instance from MultiClaw Cloud. If the instance returns to Error after two restart attempts, you may need to delete it and create a new one.

Viewer can't establish a connection

If the instance shows Online but the viewer fails to load, the problem is likely WebRTC connectivity. Go to Settings > Gateway, scroll down to the Browser Automation section, and switch WebRTC connection mode to TURN relay. Click Connect again — the relay routes traffic through MultiClaw's servers instead of a direct peer-to-peer connection.

Corporate firewall blocking traffic

Some networks block the UDP traffic or TURN server access that WebRTC requires. Ask your IT team to allow outbound UDP on ports 3478 and 5349, and HTTPS access to turn.multiclaw.io. Once the firewall rules are in place, reconnect using the standard connection mode.

Session token expired

If the viewer was open but idle, the session may have timed out. Close the viewer tab, return to the cloud desktops list, and click Connect to start a fresh session.

Cloud region temporarily unavailable

If none of the above apply, the region your instance runs in may be degraded. Check https://status.multiclaw.io for active incidents. If your region is affected, wait for the incident to resolve before reconnecting.