a month ago
The production domain www.itriaconsulting.cloud serves the default *.up.railway.app certificate. Dashboard status: Certificate Authority is validating challenges. Added today, 14 September 2026. All four Aruba authoritative nameservers return www CNAME p0rh9gez.up.railway.app; the required TXT is present and verified. No CAA restrictions, DNSSEC disabled, no Cloudflare proxy. curl HTTPS fails with error 60 (hostname mismatch); OpenSSL confirms the Railway wildcard certificate. HTTP reaches Railway and redirects to HTTPS. The generated production domain and /healthz work. Service online, Amsterdam, port 8080. The apex uses Aruba for a working HTTPS 301 redirect to www; the unused apex Railway entry is pending DNS intentionally. Please inspect failed ACME challenges and retry certificate issuance if appropriate. What action is needed to get www HTTPS working?
1 Replies
Status changed to Awaiting Railway Response Railway • 26 days ago
a month ago
Your DNS and domain verification are both correct, and the ACME challenge path reaches our edge. The certificate issuance workflow stalled after verification passed, so we have started a re-issue for the domain.
Status changed to Awaiting User Response brody • 26 days ago
19 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 • 19 days ago