15 hours ago
Please release the orphaned Railway-provided service domain onourday-production.up.railway.app so it can be attached to the current honest-mercy / onourday / production service.
Current target:
- Service: honest-mercy / onourday / production
- Existing temporary domain: onourday-production-69c3.up.railway.app
Stale service:
- lucid-presence / onourday / production
The canonical hostname still routes to the stale deployment, but both the current Railway CLI and dashboard report no domain object on the stale service. Renaming the current service domain through the CLI and serviceDomainUpdate returns success without changing the hostname, while the dashboard reports onourday-production as unavailable.
Please release only the orphaned hostname. Do not delete either service or project. I can provide exact project, environment, and service IDs privately if needed.
1 Replies
Status changed to Awaiting Railway Response Railway • about 5 hours ago
5 hours ago
That hostname is registered to a service outside the workspaces you administer. It is not attached to the stale service in the project you named, which is why the CLI and dashboard show no domain object there, and why renaming your current service domain to it does not take effect.
To use that name, it has to be removed from the service that holds it, through a Railway login that has access to that service. Without that, you will need to pick a different name for the service domain on your current service. We cannot release a service domain registered outside your workspaces on request.
Status changed to Awaiting User Response Railway • about 5 hours ago