12 days ago
Custom domain www.ensaar.com never finishes certificate issuance.
Project ensaar-website — fff8bc8f-aaf9-40cc-9f5b-65f77f14e36f
Service web — 5da5beda-c01b-49ca-855b-3304a953d0a5
Domain created 2026-08-09T10:45Z
Your API returns:
Code
You see the correct record, call it propagated, report no error, and still do not issue. Five hours and counting.
Sampling the DNS check every 30s against records that were not changing showed it flapping between PROPAGATED and REQUIRES_UPDATE, so it may never hold a positive result long enough to proceed.
Same problem on www.dailybytepro.com (project 4cf8ea4b-46f7-4ddc-bdbc-a2f702d25a0d, service 86d37bbe-4add-4a1d-bc7a-37a58fed960a).
Already tried: two DNS providers (GoDaddy, then Cloudflare unproxied); deleting and recreating the domains; targetPort 8080 and auto. DNS verified correct against Google, Cloudflare and the authoritative nameservers. /.well-known/acme-challenge/ returns your edge's own 404, so ACME requests reach you. Both services are healthy and their *.up.railway.app domains return 200.
Can you retrigger provisioning, or is something stuck server-side?
1 Replies
12 days ago
Both domains have their CNAME records propagated correctly, but the TXT ownership-verification records are missing. Certificates cannot issue until both records are present. For each domain, add a TXT record in Cloudflare with the name _railway-verify.www and the value shown on the domain's settings page in the Railway dashboard. Once the TXT records propagate, verification and certificate issuance should proceed automatically. Reply here after adding them and we can re-check the status.
Status changed to Awaiting User Response Railway • 12 days ago
5 days 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 • 5 days ago