Repository navigation
[Help] starting host server via CLI stuck in "relay rejected connection" #5147
Description
Describe the problem you confuse
I'm getting started with the CLI on a remote cloud VM, after logging in when I run superset start it gets stuck in a "relay rejected connection" loop:
◇ Host service running on port 45059 (pid 539358)
│
● Connected to relay — machine is now accessible.
│
└ Press Ctrl+C to stop.
[host-service] registered as host 28xxxxxx
[host-service:tunnel] connected to relay for host 56xxxx:28xxxxxx
[host-service:tunnel] relay rejected connection (code=1008, reason=Forbidden); retrying
[host-service:tunnel] reconnecting in 847ms (attempt 1)
[host-service:tunnel] connected to relay for host 56xxx:28xxxxxx
[host-service:tunnel] relay rejected connection (code=1008, reason=Forbidden); retrying
[host-service:tunnel] reconnecting in 734ms (attempt 1)
[host-service:tunnel] connected to relay for host 56xxx:28xxxxxx
[host-service:tunnel] relay rejected connection (code=1008, reason=Forbidden); retrying
[host-service:tunnel] reconnecting in 655ms (attempt 1)
[host-service:tunnel] connected to relay for host 56xxx:28xxxxxx
[host-service:tunnel] relay rejected connection (code=1008, reason=Forbidden); retrying
I see the host in my local Superset desktop UI on my Macbook but it shows as Offline
Not sure where to start debugging this... my machine has inbound firewall rules but the docs say the host only binds to 127.0.0.1 which has none, and I have no outbound firewall rules.
Would could be the causes of this?
Activity
themightychris commentedon Jun 5, 2026
Hmm ok after I subscribed to Pro it worked. It would be helpful if the docs could say this or the CLI errors could say this. I'm just getting an initial feel for what superset could do and lucky for y'all I was curious enough to drop $20 to see
fix: solve #5147 — escalate tunnel reconnect backoff on relay 1008 re…
saddlepaddle commentedon Jun 5, 2026
Ah apologies, good call out! I'll update the docs accordingly 😄
themightychris commentedon Jun 10, 2026
A more specific error in the CLI log would be great too!
Kitenite commentedon Jul 12, 2026
Fixed by #5573 (headless host registration: env key handling, org selection, and the relay now reports the real rejection reason instead of a bare 1008) plus #5571, which removed the plan gate that caused silent rejections.