Custom domain verification stuck despite correct DNS records – CNAME green, TXT yellow
itsonlyelectric-glitch
HOBBYOP

an hour ago

Hi Railway Support,

I'm trying to connect www.itsonlyelectric.com to my public frontend service.

The CNAME record is correctly configured and Railway recognizes it (green checkmark).

The TXT verification record is also publicly accessible and matches the exact value requested by Railway.

I've verified both using Google's public DNS (8.8.8.8):

CNAME:

www.itsonlyelectric.com → zik1l8m3.up.railway.app

TXT hostname:

_railway-verify.www.itsonlyelectric.com

TXT value:

railway-verify=0d7ab....d256c10a

Despite this, Railway continues to show a yellow warning next to the TXT record.

When accessing https://www.itsonlyelectric.com, I receive a browser SSL certificate warning and, after proceeding, Railway displays:

"Not Found. The train has not arrived at the station."

Could you please investigate whether domain ownership verification is stuck on Railway's side and manually trigger a re-verification or certificate provisioning retry?

I'd prefer not to delete and recreate the custom domain unless absolutely necessary.

Thank you!

Awaiting Railway Response

0 Replies

Status changed to Awaiting Railway Response Railway • 28 minutes ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...