a month ago
The "Not Found" error means the DNS is resolving to Railway, but Railway's edge isn't recognizing the wildcard domain as a valid service domain.
The root issue: the wildcard domain isn't actually in your service config. It keeps getting added via the UI/API, but it's not sticking. The railway.json should have fixed it, but Railway isn't reading it.
This is a Railway platform issue. You need to contact Railway support and mention:
Base domain estimate.savvybuild.co.uk works fine
Wildcard *.estimate.savvybuild.co.uk DNS is correct but Railway edge rejects it with "Not Found"
railway.json with serviceDomains isn't being read by Railway
Manual API adds don't persist across deploys
They can debug why the wildcard cert isn't provisioning or why railway.json isn't being applied.
3 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 29 days ago
a month ago
Hi, how is your schema in railway.json made?
a month ago
{
"serviceDomains": {
"estimate.savvybuild.co.uk": {},
"*.estimate.savvybuild.co.uk": {}}
}
this is what the agent used. I ended up adding the domain manually. Every time the agent did it, it just added a production url into the network settings instead
a month ago
your railway.json should look something like this:
{
"$schema": "https://railway.app/railway.schema.json",
"deploy": {
"startCommand": "npm start"},
"serviceDomains": [
"estimate.savvybuild.co.uk",
"*.estimate.savvybuild.co.uk"]
}
make sure serviceDomains is at the root level, not inside deploy. also double check the file is literally called railway.json and sits in the root of your repo, not in a subfolder.
if it still doesn't stick after a fresh deploy, it's a railway bug not your config — the wildcard cert just isn't provisioning properly on their side. worth hitting up their support directly with that info