Issues with SSL certificate
ntrampuz
HOBBYOP

5 months ago

I have normally added the custom domain www.nejctrampuz.com to the Railway; SSL issued automatically.

Then I added a redirection (nejctrampuz.com -> www.nejctrampuz.com) on my domain / DNS provider (FreeDNS from Domenca), which automatically added another custom domain on Railway; but the SSL certificate does not issue automatically as it should. The domain on Railway is stuck on “Issuins TLS certificate” for about 36 hours now. When visiting the nejctrampuz.com i get “This Connection Is Not Private”.

On the screenshots see the entry for the redirection in the FreeDNS (“A” entry), and the stuck position on Railway.

Thanks for your help! 🙂

Solved$10 Bounty

4 Replies

diogoribeirodev
FREE

5 months ago

why dont you do:

www.nejctrampuz.com -> railway

nejctrampuz.com -> railway

instead of nejctrampuz.com -> www.nejctrampuz.com


diogoribeirodev
FREE

5 months ago

browsers automatically add and hide www so you dont need to add a redirect


ntrampuz
HOBBYOP

5 months ago

Hey sorry, missed you message, thanks for your help!

I wanted to add nejctrampuz.com -> railway, but my domain provider does not allow adding CNAME without the www prefix for some reason. 😕

Problem is that not all browsers add http://www. automatically...I think Chrome does, possibly Safari, but not Edge, DuckDuckGo etc. So some people might still try to visit it without the prefixes and get "This connection is not private" warning...

I guess the only feasible solutions seems to set up the Cloudflare where I have more control over DNS settings than the FreeDNS which is integrated into my domain provider by default?


ntrampuz
HOBBYOP

5 months ago

In the end I have set up the Cloudflare instead of the FreeDNS, where I could do a proper redirect - works well now.


Status changed to Solved nico 5 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...