Troubleshooting

The most common snags when connecting a machine, and how to clear them.

The environment stays “Pending” / “Disconnected”

The console isn't seeing the connector dial out. On the box, check the service is running:

# Linux sudo systemctl status cloudflared # macOS sudo launchctl list | grep cloudflared

If it's stopped, start it (sudo systemctl start cloudflared). If it's missing entirely, the install didn't complete — re-run the connect command with a fresh token from the console. Also confirm your SkyPilot API server is actually running on localhost:46580 (attach mode) — the connector dials out fine, but the dashboard will be empty if there's nothing behind it.

“cloudflared not found” on macOS

The installer uses Homebrew to install cloudflared on macOS. If Homebrew isn't present it can't proceed. Install Homebrew (brew.sh) and re-run the connect command, or install cloudflared yourself first:

brew install cloudflared

The dashboard shows 403 / won't load

First make sure the environment is ● Connected in the console and that you're signed in (the dashboard is gated by your Slipstream session). If it's connected and you're signed in but still blocked, it's on our side of the proxy — reload once, and if it persists, contact support with the environment name.

“--token is required”

The token is shown once, right after you create the environment. If you lost it, delete the environment and create a new one to get a fresh token — see Disconnect & remove, then Connect again.

Does it survive a reboot?

Yes — the connector is installed as a system service that restarts automatically. After a reboot the environment should return to ● Connected on its own. If it doesn't, start the service manually with the commands above.

Still stuck?

Email support@slipstreamcompute.com with the environment name and what you're seeing.