2 months ago
Hey everyone,
I purchased my domain from NameSilo and initially pointed it to AWS to host a server on EC2. Recently, I switched to Railway for deploying a new backend, and Railway asked me to create a CNAME record and i did that in AWS Route 53
Now, when I open the link, it loads over HTTPS, but the browser still shows it as “Not Secure.”
Does anyone have an idea what could be causing this?
5 Replies
2 months ago
Have you allowed time for the changes to propagate, and made sure that CloudFlare TLS is not set to Full (Strict)?
2 months ago
For this specific backend on Railway, Cloudflare is not in the DNS path. My domain's nameservers point to AWS Route 53, and the CNAME record is configured directly in Route 53 to point to your provided Railway target. So, Cloudflare's TLS settings aren't applicable here.
2 months ago
And secondly Yes, I've definitely allowed time for the changes to propagate. I made the CNAME update in Route 53, 7 hours ago
2 months ago
can you share the configuration of CNAME on route 53.
Assuming you're using a subdomain like api.yourdomain.com, here’s what Route 53 should look like:
Type : CNAME
Name : api
Value : cname.tryrailway.app
2 months ago
Your DNS setup and propagation time seem correct, but make sure you’re not using a CNAME at the root. If you are, switch to an ALIAS or A record. Otherwise, give it more time or re-add the domain in Railway to resolve potential SSL certificate issuance delays.