17 days ago
Project bb5a8a69, service 35917601, domain backend.dmcaguardian.xyz. CNAME is VALID, HTTP ACME intercept works (returns 404), but no cert issued after 2+ hours. Tried multiple domains (api.dmcaguardian.xyz, backend.dmcaguardian.xyz). Same result on fresh subdomains.
11 Replies
17 days ago
You need to add TXT records to _railway-verify. backend.dmcaguardian.xyz and _railway-verify.api.dmcaguardian.xyz.
17 days ago
You can find the content for the TXT records under verificationToken property under status.
17 days ago
Are you using the API?
Yes, adding domains via the GraphQL API (customDomainCreate mutation). Should we use the dashboard instead?
16 days ago
You can obtain the TXT content from the verificationToken property under status.
16 days ago
Either works.
Added the TXT record for _railway-verify.backend.dmcaguardian.xyz with value railway-verify=2b1f2a07efabe39c3dbf5e608e622a2412e7356606c2e42d567b414fbb85699f.
Can you trigger cert provisioning for backend.dmcaguardian.xyz on service 35917601-2da2-48a6-8d3b-879316738feb?
CNAME is valid and pointing to api-production-b2ee.up.railway.app.
16 days ago
Railway should automatically trigger the certs after detecting the DNS changes.
Also, keep in mind that the CNAME records should be pointing to the provided CNAME content by Railway, it shouldn't be pointing to the pregenerated domain.
16 days ago
(If Railway doesn't automatically issue the cert within the hour, remove the domain from Railway, wait for ~10-15 mins, then re-add the domain. Make sure to update DNS records as necessary.)
Status changed to Solved 0x5b62656e5d • 16 days ago