to resolve SSL problem and subdomain issue
shahzeb608
HOBBYOP

2 months ago

root domains are working but when we use sub domains like www. it does not work and SSL is not working or its showing insecure on our site

$10 Bounty

11 Replies

Railway
BOT

2 months ago

Your root domain akfdonation.com is configured and has a valid SSL certificate, but www.akfdonation.com has not been added as a custom domain to your service. You need to add www.akfdonation.com as a separate custom domain in your Frontend service's settings, then create the corresponding DNS records (CNAME and TXT verification) at your DNS provider for it to work with SSL.


Status changed to Awaiting User Response Railway about 2 months ago


Railway

Your root domain `akfdonation.com` is configured and has a valid SSL certificate, but `www.akfdonation.com` has not been added as a custom domain to your service. You need to add `www.akfdonation.com` as a separate custom domain in your Frontend service's settings, then create the corresponding DNS records (CNAME and TXT verification) at your DNS provider for it to work with SSL.

shahzeb608
HOBBYOP

2 months ago

should i disable proxied yellow button or not and what does it do?


Status changed to Awaiting Railway Response Railway about 2 months ago


Railway
BOT

2 months ago

The orange cloud (Cloudflare proxy) routes traffic through Cloudflare before it reaches us. You can leave it enabled, but you must set your Cloudflare SSL/TLS mode to Full (not Full Strict) under SSL/TLS > Overview in your Cloudflare dashboard, otherwise you will get redirect loops or SSL errors. Also, as mentioned in the previous reply, you still need to add www.akfdonation.com as a separate custom domain in your service settings for the www subdomain to work. Our docs on Cloudflare configuration cover this in detail.


Status changed to Awaiting User Response Railway about 2 months ago


shahzeb608
HOBBYOP

2 months ago

i added www. subdomain can you check it it still gives warning on CNAME


Status changed to Awaiting Railway Response Railway about 2 months ago


Railway
BOT

2 months ago

We can see www.akfdonation.com has been added to your Frontend service and verification passed, but the CNAME record is missing from your DNS provider. You need to create a CNAME record for www pointing to 30r06kxr.up.railway.app at your DNS provider (Cloudflare) for traffic to route correctly.


Status changed to Awaiting User Response Railway about 2 months ago


shahzeb608
HOBBYOP

2 months ago

www. does not show any insecure error but akfdonation without www shows insecure error


Status changed to Awaiting Railway Response Railway about 2 months ago


shahzeb608
HOBBYOP

2 months ago

akfdonation.com is dns only (proxy disabled) and www.akfdonation.com is proxied (proxy enabled)


Railway
BOT

2 months ago

Your root domain akfdonation.com is resolving to an IP address (151.101.2.15) that does not belong to Cloudflare or Railway, which is why SSL is showing as insecure. In your Cloudflare dashboard, check that the CNAME record for @ (or akfdonation.com) points to the Railway target r9xqt4au.up.railway.app with the proxy enabled (orange cloud), and make sure there is no conflicting A record for the root domain. Your www subdomain is correctly routing through Cloudflare, which is why it works. Also ensure your Cloudflare SSL/TLS mode is set to Full as previously mentioned.


Status changed to Awaiting User Response Railway about 2 months ago


shahzeb608
HOBBYOP

2 months ago

so i can turn on proxy options for all?


Status changed to Awaiting Railway Response Railway about 2 months ago


shahzeb608
HOBBYOP

2 months ago

can i ?


Status changed to Open Railway about 2 months ago


shahzeb608

so i can turn on proxy options for all?

Yes, you can enable Cloudflare proxy for both records.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...