Production service unreachable — domain pinned to a dead edge IP
dgecon
FREEOP

a month ago

Project: CredosCRM1 (2fa7934a-f3bc-4fc4-ad58-12037659d838), production environment, service CredosCRM1.

Public domain credoscrm1.up.railway.app resolves to edge 69.46.46.97, where TCP :443 does not connect (times out) — the site has been down for days. The app itself is healthy: inside the container localhost:3000/healthz returns 200 and the process listens on :3000; domain sync status is ACTIVE, target port 3000.

Our staging domain credoscrm1-staging.up.railway.app (edge 69.46.46.127) works fine. We already tried: multiple redeploys and removing/re-adding the production domain — the new domain still resolves to the same dead edge 69.46.46.97. Railway status page shows platform UP.

Please move the production service/domain off edge 69.46.46.97 (or fix that edge node). App and data are intact — this is purely edge routing.

$10 Bounty

Pinned Solution

It's possible that your ISP is blocking the traffic. If that's the case, then unfortunately, Railway won't be able to do anything about this.

Though you can attempt to deploy in different regions (eg, EU or Asia), this feature is only available to paid plan users.

6 Replies

Railway
BOT

a month ago

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

Status changed to Open Railway about 1 month ago


I'm able to access your site just fine. Have you tried accessing it from an incognito browser, a different device/network, or with a VPN?

90361.png

Attachments


0x5b62656e5d

I'm able to access your site just fine. Have you tried accessing it from an incognito browser, a different device/network, or with a VPN? ![90361.png](https://station-server.railway.com/attachments/att_01kwyd3z8ge06vm04wyvp00vf4)

dgecon
FREEOP

a month ago

Yes

image.png


It's possible that your ISP is blocking the traffic. If that's the case, then unfortunately, Railway won't be able to do anything about this.

Though you can attempt to deploy in different regions (eg, EU or Asia), this feature is only available to paid plan users.


0x5b62656e5d

It's possible that your ISP is blocking the traffic. If that's the case, then unfortunately, Railway won't be able to do anything about this. Though you can attempt to deploy in different regions (eg, EU or Asia), this feature is only available to paid plan users.

dgecon
FREEOP

a month ago

Thanks for you reply i'll check our network


Status changed to Open 0x5b62656e5d about 1 month ago


Status changed to Solved 0x5b62656e5d about 1 month ago


Status changed to Awaiting User Response 0x5b62656e5d about 1 month ago


dgecon
FREEOP

a month ago

Changing the region did not help


Status changed to Awaiting Conductor Response Railway about 1 month ago


dgecon

Thanks for you reply i'll check our network

dgecon
FREEOP

a month ago

There are no restrictions in our network


Welcome!

Sign in to your Railway account to join the conversation.

Loading...