13 days ago
Our FlowBench public pilot at https://flowbench.kcproserv.com.au is blocked by a certificate hostname mismatch. The custom domain is verified and its CNAME matches 5ntmh7as.up.railway.app, but Railway still reports ISSUING and the dashboard says 'Certificate Authority is validating challenges'. The latest deployment is SUCCESS.
At 04:50 UTC on 7 November 2026, GET requests to both /healthz and / from the running service failed with SSLCertVerificationError: hostname mismatch, certificate is not valid for flowbench.kcproserv.com.au. Python's default trust validation and hostname checking were enabled. No certificate warning was bypassed.
Earlier checks on the same day:
- At 04:30 UTC, OpenSSL with SNI and hostname verification showed a certificate for *.up.railway.app / up.railway.app rather than our hostname.
- At 04:31 UTC, both authoritative nameservers (ns1.syrahost.com and ns2.syrahost.com) returned the expected CNAME and ownership TXT. Neither returned an apex CAA record.
The domain API currently provides no certificate error message or retry eligibility. We have not deleted/re-added the domain or forced certificate retries.
Please inspect the ACME challenge error, last validation attempt and certificate installation status, and advise whether a retry is appropriate. This is a pilot walkthrough blocker; we are not reporting a confirmed wider outage.
Project: flowbench-public-pilot. Environment: production. Service: flowbench.
1 Reply
Status changed to Awaiting Railway Response Railway • 13 days ago
13 days ago
The current certificate order for your domain was stuck, not still in progress. When the certificate authority checked the challenge, its DNS lookup for the hostname came back as non-existent (NXDOMAIN). That rejection is final for that order, so waiting would never have finished it. Your records are correct now: the CNAME has propagated, ownership is verified, and the challenge path reaches us. So a retry is the right move, and we've started a fresh certificate order. It can take a few minutes to finish.
The hostname mismatch you saw is expected while there's no certificate for your domain. Until one is installed, the edge serves the default *.up.railway.app certificate. You don't need to delete and re-add the domain. Doing that would give you a new CNAME target and verification token to set up again.
Status changed to Awaiting User Response brody • 13 days ago
6 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 • 6 days ago