Forum

Do you think people here will help to solve the problem?

Hey — to clarify:

Our AI assistant isn’t fully familiar with OpenClaw yet, so it may give the wrong call on OpenClaw-specific issues. But it is still useful for Zeabur platform stuff (logs, ports, health checks, env vars, networking, redeploy, etc.).

So you know openclaw doesn't work on your platform, but you're still allowing people to sign up for it anyway?

No — OpenClaw can run on Zeabur. What’s happening is: some OpenClaw gateway modes/configs aren’t supported in our environment (for example, tailscale serve/funnel requires binding to 127.0.0.1, but Zeabur services must bind to 0.0.0.0 to pass routing/health checks). When users hit one of those unsupported modes, it looks like “OpenClaw doesn’t work,” but it’s really a specific configuration limitation, not the whole service.

we will help you soon

Hi I am trying to fix this problem for you

You can open a post for support or follow Troubleshooting guide to save your configuration

https://zeabur.com/templates/VTZ4FX