21 days ago
Custom domain www.getaislewise.com has been stuck on "Issuing TLS certificate"
for over 48 hours. Project fa534bf9-3c50-48ba-bc8e-7442911a1476, service
getaislewise, environment production.
DNS verified from outside: CNAME www -> ipj35kdr.up.railway.app (resolves to
69.46.46.25); TXT _railway-verify.www.getaislewise.com is public with the token
from the dashboard. No CAA records, no DNSSEC/DS records, no conflicting A
record, no proxy in front (Namecheap BasicDNS, direct). HTTP requests to
/.well-known/acme-challenge/ return 404 (not a redirect). The app is reachable
over TLS on that hostname but serves an expired placeholder certificate.
The apex domain getaislewise.com in the same DNS zone and same service
(fjsl7m2i.up.railway.app) issued its certificate normally and works. Please
retry issuance for the www domain — I'd rather not delete/re-add it and burn
the Let's Encrypt duplicate-certificate limit.
Per your SSL troubleshooting docs this is past the point where DNS propagation
explains it, and every item on that checklist is verified clean on my side.
1 Replies
Status changed to Awaiting Railway Response Railway • 21 days ago
21 days ago
Your DNS and verification for www.getaislewise.com are correct. The certificate issuance pipeline had stalled, so we've re-triggered it. It should complete within a few minutes.
Status changed to Awaiting User Response Railway • 21 days ago
Status changed to Solved mykal • 21 days ago