Custom domains stuck in fallback for 2.5+ hours.
yash-gadodia
PROOP

21 days ago

Custom domains stuck in fallback for 2.5+ hours. Project ID 9e97029e-b1f1-46ad-a8b7-3a5a8e13fffc, service vibemakers-newsite.

▎ Both vibemakers.dev and www.vibemakers.dev registered via CLI. Even Railway's own DNS targets (hrqazeqw.up.railway.app,

j76om3lj.up.railway.app) return x-railway-fallback: true — which shouldn't happen regardless of my custom DNS. TXT

▎ verification records railway-verify.vibemakers.dev and railway-verify.www.vibemakers.dev are publicly visible via dig. No

▎ CAA records. DNS resolution to Railway IPs confirmed. Region: asia-southeast1-eqsg3a. Asking you to manually re-trigger

▎ verification + cert issuance.

Solved$20 Bounty

1 Replies

Railway
BOT

21 days ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway 21 days ago


Try removing the domains from Railway, wait for ~10-15 mins, then re-add them.


Status changed to Solved yash-gadodia 20 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...