a month ago
Priority: High
Project ID: a6c48868-44d9-45dd-ac37-a9be2b3dee41 Environment: production (df8ab2a3-71ff-4435-b18a-292c9ce0e467) Service: Frontend Dashboard Link:https://railway.com/project/a6c48868-44d9-45dd-ac37-a9be2b3dee41?environmentId=df8ab2a3-71ff-4435-b18a-292c9ce0e467
Issue: Domain www.twai.co.in shows a green checkmark (verified) in the Railway dashboard Networking tab, but the browser displays "not secured" when accessing the site. The SSL certificate has not been issued despite the domain appearing valid in the system.
Domain Details:
- Domain:www.twai.co.in
- Port: 8080
- Dashboard Status: Green checkmark (verified)
- Browser Status: "Not secured" / SSL certificate error
- DNS Provider: GoDaddy (with nameservers: domaincontrol.com)
- DNS Configuration: CNAME pointing to e43zd3g8.up.railway.app
Steps Already Taken:
- Hard refreshed browser (Ctrl+Shift+R)
- Tested in incognito/private window
- Tested in multiple browsers
- Verified DNS resolution is correct
- Confirmed service is running and responding (HTTP 200)
- Removed root domain to isolate the issue
Expected Behavior: Domain should show green checkmark AND have a valid SSL certificate issued by Let's Encrypt or Railway's CA.
Current Behavior: Domain shows green checkmark but certificate is not issued. Browser reports "not secured."
Requested Action: Please investigate why the SSL certificate is not being issued for www.twai.co.in despite the domain showing as verified. Either issue the certificate or provide guidance on what's blocking provisioning.
3 Replies
a month ago
Your domain's DNS is correctly resolving to our servers and the SSL certificate on our side shows a valid and complete status, so the certificate has been issued successfully. The CNAME record and the resolved IP both match what we expect. If your browser still shows "not secured," this typically indicates your application is serving resources over HTTP within the page (mixed content), which causes browsers to downgrade the security indicator even when the certificate itself is valid. You can verify the certificate is present by clicking the padlock/info icon in your browser's address bar and inspecting the certificate details.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
It works in edge but not in chrome
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your SSL certificate is confirmed valid and fully issued on our end. If it works in Edge but not Chrome, Chrome is likely caching a previous insecure response. Try clearing Chrome's cached data for the site, or visit chrome://net-internals/#hsts and delete the domain entry, then retry.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved pssantosh • about 1 month ago