DNS and SSL certificate issues

hygren
FREE

15 days ago

First time using railway.

Got godaddy with cloudflare setup to handle my domain leveranto.com. I tried generating a custom railway and that worked, so there's something with the custom URL.

Adding the custom URL leveranto.com on the frontend project suggests a CNAME which I've added in cloudflare.

When visiting leveranto.com I get this error:
ERR_SSL_UNRECOGNIZED_NAME_ALERT

Solved$10 Bounty

10 Replies

hygren
FREE

15 days ago

frontend settings

Attachments


hygren
FREE

15 days ago

And DNS settings in Cloudflare:

Attachments


faeyumbrea
PRO

15 days ago

The error is not appearing for me, can you try a different browser or device to see if it keeps happening?


faeyumbrea
PRO

15 days ago

Page is loading perfectly fine on my home wifi.

Attachments


hygren

And DNS settings in Cloudflare:

smolpaw
HOBBYTop 5% Contributor

15 days ago

In cloudflare can you go to SSL/TLS - Overview - Configure - select "Full (strict)" and save

Edit: Don't do this, read the reply from @brody below


smolpaw

In cloudflare can you go to SSL/TLS - Overview - Configure - select "Full (strict)" and saveEdit: Don't do this, read the reply from @brody below

15 days ago

We do not support Full (strict) as it prevents certification issuing.

Please do not recommend users set it.


faeyumbrea
PRO

15 days ago

ERR_SSL_UNRECOGNIZED_NAME_ALERT makes it feel potentially outside of Railways problem domain.

Since the domain is clearly set to proxy, the certificate failure here would be in the certificate sent from cloudflare, not from railways servers.

Hence my suggesting to use a different browser or device to narrow it down (especially because its working for me)


jcode
PRO

15 days ago

Are you sure the issue is unresolved? I just checked the site DNS status and it seems to have a valid certificate.

Perhaps try opening the website with cleared cache (CTRL F5 on Windows).


jcode
PRO

15 days ago


As you can see here.

Attachments


hygren
FREE

15 days ago

Thanks guys, the issue was that when I first enabled custom name servers (cloudflare) in godaddy I also imported all the existing DNS entries, INCLUDING name servers (which belonged to godaddy). And it took a long time for them to purge when I finally realized and removed them. And even more time for my ISP to have the new DNS propagated. Now it works. Many thanks for all your replies!


Status changed to Solved brody 15 days ago