2 months ago
No SSL certificates are issuing for ANY of the service domains:
tolip-ai-production.up.railway.app — should auto-issue, but doesn't
https://tolipai.com/ — custom domain, DNS resolves correctly to Railway IP
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.
6 Replies
2 months ago
The SSL certificate for tolipai.com is currently valid and fully issued, DNS is correctly propagated (CNAME pointing to your Railway service and TXT verification record in place), and the domain is verified and serving traffic through our edge. The "Not secure" warning in your screenshot was from the certificate showing *.up.railway.app instead of your custom domain's own cert, but that has since resolved. You should be able to access https://tolipai.com normally now.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Have you tried checking in another browser? SSL seems to be working on my side.
Attachments
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Awaiting User Response Railway • 2 months ago
jratienza65
Have you tried checking in another browser? SSL seems to be working on my side. 
2 months ago
works on chrome but it give this error in Edge
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Solved Railway • 2 months ago
2 months ago
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 2 months ago
2 months ago
This might just be an edge quirk.
Unless you are missing an update on your Edge browser, you really can't do anything for your end users since this could either be an issue with how Edge resolves the certificate trust chain or maybe you are serving mixed content or SmartScreen is being tripped.