In TXT record in GoDaddy ,

Host:_railway-verify.app

Value: railway-verify=469fb0430f2db6f9bff327a4d453139c856407b8bf3c15048eabc58845b902db

and

Type: CNAME

Host: app

Value: bzg4bwhf.up.railway.app

if not then hard reset

• Go to Railway dashboard
• Remove the domain
• Add app.autoclubhq.com again

The x-railway-fallback: true header and "Application not found" is the key clue here. Railway's edge is receiving the request but can't match it to your service. DNS is fine, this is a Railway-side domain binding issue.

Most likely cause

Your service is on a legacy region europe-west4-drams3a. Railway's custom domain routing on legacy regions sometimes doesn't fully propagate even after DNS is correct. The CNAME points to bzg4bwhf.up.railway.app but Railway's edge isn't mapping that incoming hostname to your actual service.

Things to check and try

Remove the custom domain from the service in Railway's UI and re-add it. Sometimes the internal binding just doesn't complete on first assignment, and re-adding forces it through.

After re-adding, wait for the Railway UI to show "Valid" on both the DNS and certificate status before testing. The "Waiting for DNS update" message can sometimes be a UI staleness issue on their end rather than an actual DNS problem.

Check that the domain is added under the correct service specifically. Since your project and service share the same name, it's worth confirming the domain is bound to the Next.js service and not at the project level.

The legacy region problem

This is likely the real issue. Legacy regions have known limitations with custom domain provisioning. If removing and re-adding doesn't fix it within an hour, the practical fix is to migrate the service to a current region. That's a redeploy but Railway retains your config. After migration, custom domains bind reliably.

Open a support ticket

Include the x-railway-fallback: true response and mention the legacy region explicitly. Railway support can force rebind the domain mapping on their edge, which you can't trigger yourself.

I'm able to access your URL just fine. Have you tried clearing your local DNS cache and/or accessing from a different device or incognito window?

thanks everyone, it was the region that was holding it back.

Take care