OpenClaw is listening on WebSocket port 18789 (listening on ws://0.0.0.0:18789)
Your domain is bound to a port named "web", which is typically HTTP
The startup probes are failing because they're trying to connect to port 18789 but the HTTP gateway can't properly route WebSocket traffic
The 502 error happens because Zeabur's HTTP gateway doesn't know how to route HTTP requests to a WebSocket-only service on port 18789.
The real issue: OpenClaw is a WebSocket service, but it's not exposing an HTTP endpoint that the domain can route to. The service needs to either:
Expose an HTTP port in addition to WebSocket, or
Be accessed directly via WebSocket instead of HTTP
Unfortunately, this is a limitation with how OpenClaw is configured on Zeabur. The service is running fine internally, but the HTTP-to-WebSocket routing isn't working properly.