Custom domain stuck in VALIDATING_OWNERSHIP since 2026-08-11 — TXT record verified publicly
astinocompany
PROOP

2 months ago

Custom domain my.anafcompoundingsolutions.be (domain ID 5bc26be8-75e4-49e8-9af7-504c781f9793, project ERP, environment production) has been stuck in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP since it was created on 2026-08-11. The required TXT record _railway-verify.my is published with the exact expected value railway-verify=03f896f2dfb006c75ed4c721ccbc... and resolves correctly from all three authoritative nameservers (ns1.european-server.eu, ns3/ns4.european-server.com) as well as from public resolvers. The CNAME my → mrrfa9fi.up.railway.app resolves and HTTP routing already works (port 80 returns a 301 to HTTPS), but HTTPS serves the *.up.railway.app wildcard certificate, so no certificate was ever issued for the custom domain. There is no CAA record and no conflicting A/AAAA record. railway domain certificate retry refuses because the status is still VALIDATING_OWNERSHIP. Please force re-validation.

Solved

1 Replies

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


2 months ago

Your DNS is correctly configured and the verification record matches. The certificate validation workflow stalled before your DNS propagated and never retried. We've triggered a certificate re-issuance for my.anafcompoundingsolutions.be, which should complete within a few minutes.


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


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...