Custom domain returns ERR_CONNECTION_REFUSED after "Error configuring network" deploy failure
miliard
HOBBYOP

8 days ago

Hi, my production site is completely down.

Project: impartial-playfulness

Service: web

Region: US West

Custom domain: www.baby-confort.shop

Deployment 1eae54e1 failed with:

Initialization: OK

Build: OK

Deploy > Configure network (07:31): "Error configuring network"

Post-deploy: Not started

Since then www.baby-confort.shop returns ERR_CONNECTION_REFUSED. The HTTP

Logs tab shows "No logs in this time range" - zero requests reach the

service. Deploy logs show the app starts fine ("Server running on

http://0.0.0.0:8080") and the service shows "Online".

This looks like the same known platform-side issue reported here:

https://station.railway.com/questions/stuck-networking-operation-every-deplo-403abebb

In that thread a Railway employee confirmed it was a known platform-side

issue and suggested redeploying. I already triggered a manual redeploy and

the domain is still not responding, so the stuck networking operation

appears to still be there.

Could you please clear the stuck/orphaned networking operation for this

service and restore routing for www.baby-confort.shop? This is a live

store and it is losing sales while down.

Thank you.

$10 Bounty

1 Replies

Railway
BOT

8 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 8 days ago


It seems like your Whois verification is put on hold. You should contact your registrar (appears to be Namecheap) to resolve this issue.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...