2 months ago
Hello Railway Support Team,
I am facing an issue with SSL certificate provisioning for my custom domain on Railway and need your assistance.
Domain details
- Custom domain:
api.sampark-setu.in - Service: Backend API (GraphQL)
- Port: 8080
- Hosting: Railway
Issue description
The custom domain is correctly added to my Railway project and DNS verification appears to be completed, however the SSL certificate is not correctly issued or attached.
Symptoms:
- Browser shows “Your connection is not private” / invalid certificate
- HTTPS does not work reliably for the custom domain
- Railway dashboard shows the domain attached, but certificate does not become active
DNS verification status
- CNAME record configured as provided by Railway
- TXT record added for domain verification
- DNS propagation confirmed using
nslookupagainst8.8.8.8 - Domain resolves to the Railway endpoint
Despite this, the SSL certificate has not been successfully provisioned.
Troubleshooting already attempted
- Removed and re‑added the custom domain in Railway
- Re‑verified DNS records after re‑adding the domain
- Tested from multiple networks and devices
- Allowed sufficient propagation time after DNS updates
Request
Could you please:
- Check whether SSL certificate provisioning is stuck or failed for this domain
- Manually re‑trigger certificate issuance if possible
- Confirm if there are any account or plan limitations affecting SSL for custom domains
This domain is already in use by a production mobile application, so a resolution or confirmation would be greatly appreciated.
Thank you for your support.
Best regards,
Dhiren Maru
(Project owner)
Attachments
2 Replies
2 months ago
Your domain api.sampark-setu.in has its CNAME and verification records correctly propagated, and our system shows the SSL certificate status as valid and complete. This means the certificate is issued and active on our end. If you're still seeing the "connection is not private" error, try clearing your browser cache or testing in an incognito window, as your browser may have cached the previous invalid certificate response.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Awaiting Railway Response Railway • about 2 months ago
Railway
Your domain api.sampark-setu.in has its CNAME and verification records correctly propagated, and our system shows the SSL certificate status as valid and complete. This means the certificate is issued and active on our end. If you're still seeing the "connection is not private" error, try clearing your browser cache or testing in an incognito window, as your browser may have cached the previous invalid certificate response.
2 months ago
Can you please check the attached screenshot of my service network configuration? It does not show SSL Status. Can you please share the screenshot of where you are seeing SSL Certificate attached to my custom domain?
Attachments
Status changed to Closed brody • about 2 months ago