Custom domain stuck on old CNAME + SSL not issuing after switching Railway accounts
grillmasterz
HOBBYOP

6 months ago

I am having a domain and SSL issue with my custom domain grillmasterz.com.au and www.grillmasterz.com.au.

Here is what happened:

Originally my website was hosted on cPanel. I then moved it to Railway and pointed my domain to a Railway CNAME (something like vg5xp5g6.up.railway.app) and everything worked fine with SSL.

Later I deleted that Railway project and Railway account, then created a new Railway account and redeployed the same website. Railway gave me a new domain:

xqnf85lp.up.railway.app

I updated my DNS provider (domainregistration.secureapi.com.au / Buzz Domain) to point both www and the root domain to this new Railway domain.

The problem now is:

www.grillmasterz.com.au still resolves to an old Railway CNAME

grillmasterz.com.au resolves to an old A record that I cannot locate

• SSL no longer issues and shows “Your website does not have HTTPS enabled”

• Even after removing and re-adding the domain in Railway, the SSL validation fails

I believe Railway still has stale domain bindings or SSL challenges from the deleted project that are blocking the new project from validating this domain.

Could you please:

  1. Check if grillmasterz.com.au or www.grillmasterz.com.au is still attached to any deleted or inactive Railway project
  2. Remove any old domain or SSL bindings for this domain
  3. Force a clean re-verification so my current project on xqnf85lp.up.railway.app can issue SSL correctly

This domain was working perfectly before I switched Railway accounts, so I believe this is a stale verification issue on the Railway side.

Thank you very much for your help.

$10 Bounty

1 Replies

Status changed to Awaiting User Response Railway 6 months ago


I'm able to access your links perfectly fine on my end. Have you tried flushing your local DNS cache?


Welcome!

Sign in to your Railway account to join the conversation.

Loading...