3 months ago
Hello,
I connected my custom domain oloxshop.com from Namecheap to Railway using the recommended CNAME records:
www → 4wms6w7f.up.railway.app
The status in Railway shows Setup complete, but HTTPS is still not working.
Both URLs:
return “Connection not secure / NET::ERR_CERT_COMMON_NAME_INVALID”.
Because HTTPS is not active yet, my API routes return 500 errors when the frontend tries to call /api/create-order.
I waited for DNS propagation, and the domain resolves correctly, but the SSL certificate still isn’t issued.
Could you please check why SSL/HTTPS is not being applied to my custom domain?
Thank you.
2 Replies
3 months ago
Hey there!
I can confirm, it looks like it was just taking DNS a moment to propagate. Everything here is good to go!
Status changed to Awaiting User Response Railway • 3 months ago
Status changed to Solved echohack • 3 months ago