I can't reach the Control UI

What to check when your subdomain doesn't load.

What this is

You clicked the Control UI link from Beach (the sd-XXXXXXXX.beachhost.io URL) and got a network error, blank page, or timeout. Usually this means your instance is stopped or still starting up, or your browser is holding onto stale state. Less commonly, DNS for a freshly provisioned subdomain hasn't fully propagated yet.

Try these in order

  1. Is your instance running? Open the Beach dashboard. If it shows "stopped", start it and wait for it to come up. See Starting & stopping.
  2. If it's running, wait 30 seconds and refresh. The Control UI takes a moment to be reachable after the instance boots — even after the dashboard shows "running".
  3. Clear your browser cache for the subdomain and reload. Stale cookies or cached error pages occasionally stick around.
  4. Try a different browser. This rules out a browser extension or stale local state. If the Control UI loads in a fresh browser, the issue was on your end.
  5. If your instance was just provisioned, wait a few minutes. A brand-new subdomain occasionally takes a few minutes to propagate across DNS. This usually only matters right after first signup.
  6. Contact support if none of the above worked. Include the subdomain URL and roughly when the issue started.

Note on the boundary

The Control UI is OpenClaw's interface, served from your dedicated server — Beach is responsible for routing your subdomain to that server, and for keeping the server running. If the subdomain doesn't resolve at all, that's a Beach-side issue. If it loads but the Control UI itself is broken, that's an OpenClaw-side issue and worth flagging to support so we can investigate.

Related

Still stuck?

Contact support — see Getting support.