a month ago
The custom domain qeeplogic.com has been stuck in ISSUING / POLLING_AUTHORIZATIONS since 2026-10-16 around 20:38 UTC (over one hour). HTTPS fails with certificate name mismatch. Could Railway staff investigate the ACME authorization/order and edge certificate provisioning, and retrigger issuance if stuck?
Checks: ownership verified=true; DNS is Spaceship CNAME flattening at the apex pointing to 0w1osazk.up.railway.app, with authoritative A matching the target (69.46.46.26). Railway DNS status alternates between PROPAGATED and REQUIRES_UPDATE with empty currentValue. Public Google DNS validates DNSSEC (AD=true); no CAA restrictions or AAAA record. TXT verification is present. Deployment and /health return 200 via the Railway domain. www.qeeplogic.com is reported certificate VALID, but redirects to the apex where HTTPS fails. CLI certificate retry is rejected because issuance has not failed and remains ISSUING.
Please identify the underlying authorization failure and help restore HTTPS on qeeplogic.com.
1 Reply
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
The certificate for your apex domain has now issued and shows as valid, and an HTTPS request to it just returned 200 from your service, so the redirect from www should land on a working certificate too. If a browser still shows the name mismatch, it is likely holding on to an older connection, and a fresh tab or private window will pick up the new certificate.
Status changed to Awaiting User Response Railway • about 1 month ago
24 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 • 24 days ago