IIRC serviceDomain isn't a valid field in Railway's Config as Code. https://docs.railway.com/config-as-code/reference

If you're using the API, serviceDomain is used for *.railway.app. You should be using customDomains instead. (https://docs.railway.com/integrations/api/manage-domains)

Having pregenerated Railway domains shouldn't conflict with custom domains as well.

The same domains and DNS settings wasn't changed for weeks. it was working like a charm.

This URGENT bug happened only now after a new deploy.

I have added the permenant domain to the railway.json as the agent bot suggested with no luck .

every new deploy the system adds a random custom domain to the service. ignoring the custom domain that was working for few months now

I’ll check with the team regarding the agent’s response. But according to the schema, serviceDomains isn’t a valid field.

also the serviceDomain parameter was suggested by the agent as a fix that didn't worked

Forbidden. If this is your website, please make sure your domain's DNS is pointing to a .up.railway.app CNAME. For example, gateway.up.railway.app

this is the response of the domain. as mentioned above, nothing was changed lately.

What URL are you trying to access?

go.dakotime.app

I'm able to access the domain just fine.

hi,

it used to work until my last deploy.

obviously the response is from railway.

i've checked from 2 laptops..

any idea?

Have you tried using a VPN?

yes.

same response.

Let me check with the team.

Try clearing your local DNS cache or use a different network. Your DNS setup seems correct, so I'm not too sure what's happening here.

@livneb It's your persistent cache, you can confirm this by using your mobile device to access the website.

Your website's DNS is fine as can seen here: https://dnschecker.org/#A/go.dakotime.app

Flush your DNS:

sudo dscacheutil -flushcache

sudo killall -HUP mDNSResponder

And try again.

I have tried to flush dns before i opened the ticket.

this issue has happened right after a deploy, that's why i'm pretty sure it has something to do with railway system.

also, my my dns resolve the correct ip of the domain.

and... the response i get is from railway. which means the dns works as expected, my assumption is that the actual routing/ingress layer is not associating the domain with the service.

i have no other choice, other users get this error as well. i will try to add an additional subdomain now

Joining this conversation as similar thing happened to my domain as well.

Havn't deployed anything for 25 days already and started getting the same "Forbidden. If this is your website, please make sure your domain's DNS is pointing to a .up.railway.app CNAME. For example, gateway.up.railway.app" message when opening my website.

Tried a deploy today but nothing changed.

Please create your own thread.

I have a created a new subdomain. it worked for few hours. and then i created another one. it also worked for few more hours.

app.dakotime.app & my.dakotime.app

after few hours they just stopped responding.

the strange thing is that the app is working perfectly under the generated domain dakotime-production-8745.up.railway.app

can someone please have a look??