I have host my frontend on railway, which is a github repository. I set up custom domain and it is [tutio.study](http://tutio.study) I have waited now was also 10 hours and it is still validating. Is there any problem

Validating domain for too long. - Railway Central Station

Validating domain for too long.

bearior

HOBBYOP

2 months ago

I have host my frontend on railway, which is a github repository. I set up custom domain and it is tutio.study

I have waited now was also 10 hours and it is still validating. Is there any problem

Solved$10 Bounty

Pinned Solution

0x5b62656e5d

MODERATOR

2 months ago

Something I'd try is to just remove the DNS records from your DNS provider and Railway, wait for 10-ish minutes, then re-add it again and see how it goes.

2 Replies

Railway

BOT

2 months ago

Your CNAME and verification TXT records are both correctly configured and propagated. However, your domain is resolving to an A record with IP 151.101.2.15, which is not a Railway IP. This is likely a conflicting A record at your DNS provider that is interfering with the CNAME and preventing certificate issuance. Check your DNS provider for any existing A records on tutio.study and remove them so the CNAME to qla1bc88.up.railway.app can take effect properly.

Status changed to Awaiting User Response Railway • about 2 months ago

Status changed to Awaiting Railway Response Railway • about 2 months ago

Status changed to Open Railway • about 2 months ago

0x5b62656e5d

MODERATOR

2 months ago

Something I'd try is to just remove the DNS records from your DNS provider and Railway, wait for 10-ish minutes, then re-add it again and see how it goes.

Status changed to Solved brody • about 2 months ago

Welcome!