I can't access my open claw deployment
Anonymous
FREEOP

15 days ago

When I try opening my open claw deployment i get the following message:

Gateway not ready: Error: Gateway did not become ready in time

It was working before. and the status seems to work fine. Anyone knows how to fix this?

$10 Bounty

8 Replies

Status changed to Open Railway 15 days ago


Have you tried redeploying the service?


darseen

Have you tried redeploying the service?

Anonymous
FREEOP

15 days ago

I just tried redeploying. It shows the deployment was successful but the issue persists.


Are there any error logs in the deploy logs section that you can share?


darseen

Are there any error logs in the deploy logs section that you can share?

Anonymous
FREEOP

15 days ago

Yes, it is consistent with the gateway error, but I have no idea how to solve it.

Edit: I tried using claude to guide me, it seems I need to open the JSON to add the gateway config, but I am not able to do so.

Attachments


Try passing --allow-unconfigured in the start command.


darseen

Try passing `--allow-unconfigured` in the start command.

Anonymous
FREEOP

15 days ago

Not working, I think I'll start a new project. It should take me a couple of hours getting to the point I was before. Might be the most efficient way forward

Attachments


![](https://station-server.railway.com/attachments/att_01kr1q9623exwt2bhfyfteappf)Not working, I think I'll start a new project. It should take me a couple of hours getting to the point I was before. Might be the most efficient way forward

The start command should be: openclaw gateway --allow-unconfigured not just --allow-unconfigured Try that and see if it resolves the issue


darseen

The start command should be: `openclaw gateway --allow-unconfigured` not just `--allow-unconfigured` Try that and see if it resolves the issue

Anonymous
FREEOP

15 days ago

Still not working, although it failed on the healthcheck step instead of the deploy. This time there are no errors on the deploy log.

Attachments


Welcome!

Sign in to your Railway account to join the conversation.

Loading...