6 days ago
Issue: My custom domain (witgoedaanbod.nl) has been stuck for 2+ days. It shows as verified (green checkmark) in Settings → Networking, and DNS is confirmed correct via multiple independent resolvers (Google 8.8.8.8, Cloudflare 1.1.1.1, and the domain's own authoritative TransIP nameservers) — all consistently resolving to the correct Railway target. Despite this, visiting the domain always returns Railway's own "Not Found — domain has not provisioned" page.
The underlying service itself is healthy — the default *.up.railway.app URL loads the site correctly.
What I already tried (with help from Railway's dashboard AI assistant):
- Confirmed DNS records (ALIAS + TXT verification record) are correct and match exactly what Railway's "Configure DNS Records" dialog expects
- Triggered a manual redeploy — no change
- Removed and re-added the custom domain in Networking settings — it re-verified within seconds (confirming DNS is fine), but the site still returned "Not Found"
- The AI assistant inspected the service config directly and found that witgoedaanbod.nl was NOT present in serviceDomains, despite being added and showing as verified in the UI
- It added the domain to serviceDomains and deployed — but checking again afterward, the domain had disappeared from serviceDomains again
- It also removed a multi-region config, suspecting that was causing the domain to be stripped on each deploy — this didn't fix it either
- At one point, adding the domain triggered a "You have reached the limit for service domains per service on your plan" error, after several auto-generated *.up.railway.app domains had accumulated across the repeated deploy attempts
- I manually cleaned up the extra auto-generated domains, keeping only one default domain + the custom domain — the custom domain still doesn't route correctly
This looks like a platform-level bug with custom domain persistence in the service configuration, not a DNS or application issue. The service is: witgoed-aanbod (also referenced as witgoed-aanbod-production.up.railway.app). Could someone take a look at why the custom domain binding isn't sticking after deployment? Happy to provide screenshots or logs on request.
Attachments
3 Replies
6 days ago
Your workspace subscription is currently inactive, and the service witgoed-aanbod in the project artistic-motivation does not appear to have an active deployment. Traffic is reaching us on witgoedaanbod.nl (DNS and certificate are both valid), but there is no running deployment to route it to, which produces the "Not Found" page. Your .up.railway.app domain may have been working from a cached or previously active deployment that has since been removed. To resolve this, you'll need to reactivate your subscription from your billing settings and ensure the service has a successful deployment.
Status changed to Awaiting User Response Railway • 6 days ago
6 days ago
I checked billing and everything shows as active:
- Active Plan: Hobby Workspace
- Payment method on file (card ending 7564)
- Billing History shows one successful charge (June 11, 2026, $5.00), no failed payments
- I also just added a complete billing address (was previously missing) - but the domain still shows "Not Found" after this
I don't see anything on my end indicating an inactive subscription. Could you double-check the workspace status again, or clarify exactly what "inactive" refers to? Project: witgoed-aanbod, workspace: artistic-motivation, domain: witgoedaanbod.nl
Status changed to Awaiting Railway Response Railway • 6 days ago
Status changed to Awaiting User Response Railway • 6 days ago
peterhoman
I checked billing and everything shows as active: - Active Plan: Hobby Workspace - Payment method on file (card ending 7564) - Billing History shows one successful charge (June 11, 2026, $5.00), no failed payments - I also just added a complete billing address (was previously missing) - but the domain still shows "Not Found" after this I don't see anything on my end indicating an inactive subscription. Could you double-check the workspace status again, or clarify exactly what "inactive" refers to? Project: witgoed-aanbod, workspace: artistic-motivation, domain: witgoedaanbod.nl
6 days ago
Thanks for looking into this. Since the automated troubleshooting hasn't resolved it yet, and this seems like an edge case (billing shows active but the platform apparently flagged it as inactive), could a human Railway engineer take a look at this specifically? This has been blocking our production launch for several days now. Happy to provide any additional info needed.
Status changed to Awaiting Railway Response Railway • 6 days ago
Status changed to Awaiting User Response Railway • 6 days ago