Need to contact any Seafloor admins for server side issue. Have been trying for over a day now.

[loud mortar]

After a LONG chat with Krill i managed to find the issue and theres nothing i can do about it. I NEED a seafloor admin.

Instance bot-user7tkh68 (botId bot_user_7tkh68_mlgcd0dz) is unusable. Worker WS closes immediately: 4008 connect failed even after reboot-machine=200. Please reprovision/migrate/restart the gateway inside the worker.

[rigid rune]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[muted forge]

I don’t have Seafloor admin access from here, so I can’t reprovision/migrate/restart the gateway inside bot-user7tkh68 myself.

Given “Worker WS closes immediately: 4008 connect failed even after reboot-machine=200”, this is almost certainly worker-side / Seafloor-side (i.e., not something you can fix via OpenClaw config changes on your end).

What will get you unstuck fastest is a Seafloor support/admin action (reprovision or migrate the worker). When you post/escalate, include this in one block so an admin can act without back-and-forth:

• Instance: bot-user7tkh68
• botId: bot_user_7tkh68_mlgcd0dz
• Symptom: worker WS immediately closes with 4008 connect failed
• Tried: reboot-machine=200 (still broken)
• Request: reprovision/migrate the instance (or restart the gateway process inside the worker)

If Seafloor has a dashboard/ticket system and you can open a ticket, do that and paste the ticket ID/link here — that’s usually the quickest way for the right person to find it.