a month ago
Got it. So HTTPS is being enforced automatically. Let me search the docs to see if there's a known issue or setting with Streamlit and Railway certificates:
Searched docs: Streamlit SSL certificate HTTPS Railway
That didn't help. Let me try a different angle — is Streamlit configured to force HTTPS in your app code?
Read file: app.py
The code doesn't force HTTPS. The issue is on Railway's side — the certificate isn't issuing for these domains. Let me update your memory and then we need to escalate this:
This is a platform issue — Railway is not issuing SSL certificates for your service at all, neither for the custom domain nor for its own *.up.railway.app domains. That's not normal.
You need to open a support thread at station.railway.com with:
Subject: SSL certificates not issuing on judgment_analyser service
Body:
Service: judgment_analyser (c7095e70-f1c8-4798-b27f-bbdb1e090e68)
Project: secure-upliftment (e145b90e-922d-4945-84ae-e51c019ed466)
Environment: production (45fbf60e-4f06-472a-ae9d-9effee1e388d)
Issue: No SSL certificates are issuing for ANY of the service domains:
judgmentanalyser-production-61d2.up.railway.app — should auto-issue, but doesn't
www.evidenceedge.com.au — custom domain, DNS resolves correctly to Railway IP
The app runs fine (Streamlit starts correctly), but HTTPS fails with net::ERR_CERT_COMMON_NAME_INVALID
DNS is configured correctly (verified with nslookup)
This needs Railway's infrastructure team to investigate why the certificate issuer isn't picking up these domains.
Pinned Solution
a month ago
You need to add a TXT record for _railway-verify.www.evidenceedge.com.au. If you are using the API to add your custom domain, you can find it in verificationToken under status.
Also, your CNAME shouldn't be your service's public URL, it should be whatever Railway gave you to setup your custom domain.
3 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 29 days ago
a month ago
You need to add a TXT record for _railway-verify.www.evidenceedge.com.au. If you are using the API to add your custom domain, you can find it in verificationToken under status.
Also, your CNAME shouldn't be your service's public URL, it should be whatever Railway gave you to setup your custom domain.
a month ago
so the TXT record name should be evidenceedge.com.au, and the value as above?
Where do if find "status"?
riverina-rumpole
so the TXT record name should be evidenceedge.com.au, and the value as above? Where do if find "status"?
a month ago
The TXT record should be set for _railway-verify.www.evidenceedge.com.au, and you can get the value of it from status.verificationToken if you are using the API. Otherwise, you can get the values from the dashboard and set them up in your DNS records.
Status changed to Solved 0x5b62656e5d • 25 days ago