5 hours ago
HTTPS clients reject kkmakeit.com before the redirect to www.kkmakeit.com. At 09:45 UTC on 7 November 2026, the certificate served for SNI kkmakeit.com had expired on 26 August 2026 at 18:03:59 UTC. Both apex certificates listed by Railway have expired. The existing domain is active and verified, DNS status is propagated, and the public ownership TXT matches. The apex and the required Railway target resolve to the same IPv4 address. The public API reports ISSUING with no detailed status, error or retryable flag. We also observed ISSUING on 28 October and 6 November. The www hostname serves a trusted certificate and both tested pages return HTTP 200. Could you check the outstanding ACME order and renew the certificate on the existing apex domain, or confirm the exact safe retry for its current state? Please keep the existing domain binding and www configuration in place.
1 Replies
Status changed to Awaiting Railway Response Railway • about 5 hours ago
5 hours ago
We confirmed what you described. The apex domain is verified and its DNS is correct, the certificate challenge path reaches us with a 200, and the certificate is still stuck in issuing with no error.
We've started a fresh certificate issuance on the existing apex domain. It can take a few minutes to finish. Your existing domain binding and the www configuration stay as they are, and you don't need to change any DNS records.
Status changed to Awaiting User Response chandrika • about 5 hours ago