4 months ago
I'm getting a "Failed to issue TLS certificate" error on my caddy-proxy service in the endearing-communication project. The domain *.useinspect.dev is mapped to Port 80, but when attempting to issue a TLS certificate, it shows the error: "An internal error occurred. Please retry or contact support." I have tried the "Try Again" button but the issue persists.
6 Replies
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
Additional info: The domain *.useinspect.dev is registered and managed through Namecheap. The DNS is configured to point to Railway. Please let us know if any specific DNS settings or CNAME records need to be adjusted on the Namecheap side to resolve the TLS certificate issuance issue.
4 months ago
I am the owner of the project and invited demoatworkstream to help to fix but didn't work.
4 months ago
Your DNS records are correctly configured - both the wildcard CNAME and the _acme-challenge CNAME are resolving properly. The TLS certificate issuance failure appears to be on our end, and we're escalating this to our platform team to investigate.
Status changed to Awaiting User Response Railway • 4 months ago
4 months ago
Hi sam-a, thank you for looking into this! Just wanted to kindly check in — has there been any progress from the platform team on the TLS certificate issuance issue? We're looking forward to getting this resolved. Thank you!
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
Could you try re-adding the domain, and ensure the DNS records are correct? It seems there's a stale TXT record on _acme-challenge that you may have to reach out to your DNS provider to flush.
Status changed to Awaiting User Response Railway • 4 months ago
4 months ago
That did it! We deleted the stale TXT record, re-added the domain, and the TLS certificate issued successfully. Thanks so much for the help!
Status changed to Awaiting Railway Response Railway • 4 months ago
Status changed to Solved demoatworkstream • 4 months ago