Custom Domain DNS Verifaction stuck
guitartsword
PROOP

11 days ago

TXT and CNAME verification is failing for domain energy.andespower.com.

I checked and both records are propagated correctly. Checking similar threads it seems that this needs to be re-triggered.

Can you trigger the certificate issuance for this domain?

Solved

3 Replies

Railway
BOT

11 days ago

Neither the required CNAME nor the TXT verification record is currently resolving for energy.andespower.com. The domain's nameservers are parking nameservers (Afternic), so DNS records you've added may not be taking effect. You'll need to point the domain to a DNS provider where you can manage records, then add the CNAME and TXT records shown on the domain's settings page in your Railway project. Once both records propagate, verification and certificate issuance will proceed automatically. Reply here once the records are in place and we can re-check.


Status changed to Awaiting User Response Railway 11 days ago


Railway

Neither the required CNAME nor the TXT verification record is currently resolving for `energy.andespower.com`. The domain's nameservers are parking nameservers (Afternic), so DNS records you've added may not be taking effect. You'll need to point the domain to a DNS provider where you can manage records, then add the CNAME and TXT records shown on the domain's settings page in your Railway project. Once both records propagate, verification and certificate issuance will proceed automatically. Reply here once the records are in place and we can re-check.

guitartsword
PROOP

11 days ago

you are right, the correct domain is energy.andespower.co, it had a typo


Status changed to Awaiting Railway Response Railway 11 days ago


Railway
BOT

11 days ago

The domain added to your Railway project is energy.andespower.com (the typo), but your DNS records (CNAME and TXT) are correctly configured for energy.andespower.co. Remove energy.andespower.com from your service's custom domain settings and add energy.andespower.co instead. Verification and certificate issuance should proceed automatically since both records are already propagated for the .co domain.


Status changed to Awaiting User Response Railway 11 days ago


Status changed to Solved guitartsword 11 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...