a month ago
"TXT _railway-verify.www records are in place and match the verification token for http://www.restaurante31dejaneiro.com and http://www.ostrasecoisas.pt, but the domains remain unverified. Can you trigger a fresh verification? We want the certificate issued before switching the CNAME, to avoid downtime."
2 Replies
a month ago
The _railway-verify.www TXT records on both domains resolve to the expected tokens, so that part is set up correctly.
The certificate cannot be issued ahead of the switch, though. For a non-wildcard domain, the certificate authority validates by reaching the domain itself, and both www CNAMEs still point at your current host rather than at the Railway target, so validation cannot reach us yet. Re-triggering verification now would stop at the same point.
Once you set each www CNAME to the target shown for that domain in its service's Settings, under Networking, verification and certificate issuance continue on their own. You do not need to remove and re-add the domains.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Hi Railway team,
Project: carta-digital-staging (ced1e344-4c71-4b19-9b18-ce4b1305550c), environment: production
These 4 custom domains have had correct DNS for over 2 hours (changed 2026-10-09 ~13:30 Lisbon time), but they're still showing verified: false and certificateStatus ISSUING. In the meantime they serve the *.up.railway.app wildcard certificate, so the sites currently show a security warning to visitors:
- www.restaurante31dejaneiro.com (service site-31-de-janeiro) – CNAME -> 7ue544qg.up.railway.app
- www.ostrasecoisas.pt (service site-ostras-e-coisas) – CNAME -> 41cjzccg.up.railway.app
- gestao.grupo-m.pt (service frontend) – CNAME -> jwjz8kb2.up.railway.app
- clientes.grupo-m.pt (service frontend) – CNAME -> li5xdqfh.up.railway.app
Both the CNAME and the _railway-verify TXT record for each domain resolve correctly on public resolvers (8.8.8.8), the dashboard shows the DNS records as "Propagated", and there are no CAA records on any of these domains.
The same thing happened with www.grupo-m.pt and www.restaurantembrasa.pt in this project. Both were fixed right away once your team started a fresh verification. Could you please do the same for these 4?
www.ostrasecoisas.pt is a live restaurant website that is currently unreachable because of this, so it's urgent.
Thank you!
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
It looks like you already have a thread open about this: Custom domains stuck in VALIDATING_OWNERSHIP / certificate ISSUING for 2+ hours (DNS fully propagated). We're automatically closing this one, and we'll reply to you there soon. If you have anything more to add about this topic, please post it in that thread.
Status changed to Duplicate Railway • about 1 month ago