opening the https version looks fine for me

for some people, when they navigate to www.easypairing.com, they get an error. did you get that?

It can happen when using Railway with custom domains that:

• https://easypairing.com works

• https://www.easypairing.com does not

This is usually not a DNS issue, even if the www CNAME record is configured correctly.

The key point is that Railway only serves domains that are explicitly registered in the service. DNS only resolves the hostname, but Railway still needs to know that the domain is valid for the application.

Railway is responsible for:

• validating the domain

• issuing the HTTPS certificate

• routing the request to the app

If www.easypairing.com is not added under Settings → Domains in Railway, Railway will not route traffic for it, even if DNS points to the correct Railway hostname.

That’s why one domain can work while the other does not.

The correct setup is:

• add easypairing.com to Railway

• add www.easypairing.com as well

• once both are working, choose one as the primary domain

• redirect the other with a 301 at the application or proxy level (not in DNS)

This explains why www can fail while the root domain works, even though both point to the same place in DNS.

The DNS for www.easypairing.com is working

• The request reaches Railway

• Railway does not have that domain assigned to any service

• Because of that, Railway returns its own 404 page

• The solution is to add www.easypairing.com in Railway → Domains

I have added both entries in railway. I want to mention that I am using cloudflare as well, but still get the same error. I have a redirect in cloudflare from www to root, but still have the not secure message even though it says the certificate is valid

hy depassport703, i think the issue might be your cloudflare ssl/tls mode

try this:

1. go to cloudflare → ssl/tls → overview

2. check what mode you have selected

3. if it's on "full (strict)", try changing it to just "full"

railway's docs specifically say "full (strict) will not work as intended" when using cloudflare proxy with railway. this could explain why some people see the ssl error and others don't

also make sure:

• universal ssl is enabled (ssl/tls → edge certificates)

• both your @ and www records in cloudflare dns have the orange cloud turned on

• both domains show green checkmarks in your railway dashboard

if you have a cloudflare redirect rule from www to root, try temporarily disabling it to see if that's causing issues, then set it up again using cloudflare's bulk redirects feature instead

i'd try the ssl mode change first since that's what railway's docs emphasize the most

let me know if it helps!

I have it set yo full and not strict on cloudflare
universal ssl is enable on cloudflare
they both have the orange cloudsyet, when I go to https://easypairing.com, I get the sae not secure error but certificate s valid. Not sure what else to do now. I have tried multiple times and same problem. Some get it, some don't get the error. funny enough, it works incognito for me with no error.

thanks

the fact that it works in incognito but not in regular browsing is the key here. this means your configuration is actually correct , it's a browser cache issue

here's what's happening:

when you or others visited the site before when there was an ssl issue, your browser cached that "not secure" state. incognito doesn't use any cache, so it sees the site correctly

try this:

1. clear your ssl cache:

   • chrome: go to chrome://net-internals/#hsts

   • type "easypairing.com" in "delete domain security policies"

   • click delete

   • do the same for "www.easypairing.com"

2. clear browser cache completely (ctrl+shift+delete, select "cached images and files" and "cookies")

3. restart your browser

4. wait a bit , sometimes it takes 10-30 minutes for everything to fully propagate after cloudflare changes

5. tell the users who are having issues to clear their browser cache too

the fact that some people see it correctly and it works in incognito means your railway + cloudflare setup is actually working fine now. it's just cached incorrectly in some browsers from when there was an issue earlier

give it a try and see if clearing the hsts cache fixes it for you..

it works for me

this confirms what i said , your railway + cloudflare configuration is correct. the issue was cached ssl state in browsers

for users still getting the error:

tell them to clear their browser cache and ssl state:

1. chrome: go to chrome://net-internals/#hsts

2. type "easypairing.com" and click "delete"

3. type "www.easypairing.com" and click "delete"

4. clear browser cache (ctrl+shift+delete)

5. restart browser

or just wait a bit , browser caches expire naturally. within 24-48 hours most users won't see the error anymore without doing anything

your setup is working fine now. no railway or cloudflare issues.

i hope this help you

Thank you so much!!! I guess there were so many moving parts, and the cache made it even difficult to debug. Clearing the ssl state and restarting thr browser fixed it. Thanks everyone!!

glad it worked! yeah the cache thing makes ssl issues tricky to debug since it looks like a config problem but it's actually just stale browser data. if any of your users still report the issue just point them to clear their hsts cache the same way. good luck with your project