Release custom domains from inaccessible old project
Anonymous
HOBBYOP

a month ago

Hi Railway Support,

I need help releasing/transferring two custom domains from an inaccessible old Railway project to my current Railway workspace.

Old project:

  • Name: abundant-charisma
  • Project ID: 041ab182-2760-4176-a764-34a04d323b86
  • Environment: production
  • Environment ID: 3a9b664e-75fa-4925-b088-cc7bf9a9fa1a

Old services:

  • API service: @nelaride/api
  • API service ID: 09e7f2b2-cc1d-44ac-ad74-67b9fe33b781
  • Admin service: @nelaride/admin
  • Admin service ID: 0fbe4959-ca5d-45ac-ba69-3fe4e9b2440f

Domains to release/transfer:

  • api.nelaride.com
  • admin.nelaride.com

Current DNS:

  • api.nelaride.com -> wu1423vp.up.railway.app
  • admin.nelaride.com -> 7vs292ud.up.railway.app

I control DNS for nelaride.com and can prove ownership by adding TXT records if needed.

My new Railway project is already set up and healthy, but domain attachment fails because these domains appear to still be claimed by the old project.

Please release or transfer these custom domains so I can attach them to my new Railway project.

Solved

8 Replies

Railway
BOT

a month ago

We can remove both domains for you, but we need to verify ownership first. Please add a TXT record at _railway.verify.api.nelaride.com with the value k4wn7r2p and another TXT record at _railway.verify.admin.nelaride.com with the same value k4wn7r2p. Once both records have propagated, reply here and we will verify and remove api.nelaride.com and admin.nelaride.com so you can add them to your new project.


Status changed to Awaiting User Response Railway about 1 month ago


Railway

We can remove both domains for you, but we need to verify ownership first. Please add a TXT record at `_railway.verify.api.nelaride.com` with the value `k4wn7r2p` and another TXT record at `_railway.verify.admin.nelaride.com` with the same value `k4wn7r2p`. Once both records have propagated, reply here and we will verify and remove `api.nelaride.com` and `admin.nelaride.com` so you can add them to your new project.

Anonymous
HOBBYOP

a month ago

I added both TXT records:

_railway.verify.api.nelaride.com = k4wn7r2p

_railway.verify.admin.nelaride.com = k4wn7r2p

Please verify ownership and release/remove api.nelaride.com and admin.nelaride.com from the old Railway project.


Status changed to Awaiting Railway Response Railway about 1 month ago


a month ago

The custom domain has been removed. You can add it to your service now.


Status changed to Awaiting User Response Railway about 1 month ago


brody

The custom domain has been removed. You can add it to your service now.

Anonymous
HOBBYOP

a month ago

Thanks. Just to confirm: did you remove/release both custom domains, or only one?

Domains:

  • api.nelaride.com
  • admin.nelaride.com

Please confirm both have been released from the old project so I can attach them to my new Railway project.


Status changed to Awaiting Railway Response Railway about 1 month ago


Anonymous
HOBBYOP

a month ago

Hi Railway Support,

Thanks. I added the TXT verification records and you confirmed the custom domain was removed, but I still cannot attach either domain to my new Railway project.

Both domains are still blocked:

  • api.nelaride.com
  • admin.nelaride.com

Errors:

  • CLI: Unauthorized. Please run railway login again.
  • GraphQL customDomainCreate for API: Not Authorized, trace 6647106108724261341
  • GraphQL customDomainCreate for Admin: Not Authorized, trace 6002200492458943125

New service IDs:

  • API service: bf4a52e6-6885-419c-80e4-1c06d406dd93
  • Admin service: 4f701124-6d91-4452-bb66-fa55bf9a1884

Please confirm both domains were fully released from the old project and that my current workspace has permission to attach them. If possible, please manually attach:

api.nelaride.com → API service

admin.nelaride.com → Admin service

Or fully clear the domain claims so I can attach them myself.


Status changed to Solved Anonymous about 1 month ago


Anonymous
HOBBYOP

a month ago

Hi Railway Support,

Thanks. I added the TXT verification records and you confirmed the custom domain was removed, but I still cannot attach either domain to my new Railway project.

Both domains are still blocked:

  • api.nelaride.com
  • admin.nelaride.com

Errors:

  • CLI: Unauthorized. Please run railway login again.
  • GraphQL customDomainCreate for API: Not Authorized, trace 6647106108724261341
  • GraphQL customDomainCreate for Admin: Not Authorized, trace 6002200492458943125

New service IDs:

  • API service: bf4a52e6-6885-419c-80e4-1c06d406dd93
  • Admin service: 4f701124-6d91-4452-bb66-fa55bf9a1884

Please confirm both domains were fully released from the old project and that my current workspace has permission to attach them. If possible, please manually attach:

api.nelaride.com → API service

admin.nelaride.com → Admin service

or fully clear the domain claims so I can attach them myself.


Status changed to Awaiting Railway Response Railway about 1 month ago


Anonymous
HOBBYOP

a month ago

Hi Railway Support,

I verified ownership for these domains using the TXT records Railway requested:

  • api.nelaride.com
  • admin.nelaride.com

Support said the custom domain was removed, but I still cannot attach either domain to my new Railway project.

Current error:

CLI: Unauthorized. Please run railway login again.

GraphQL/customDomainCreate also returned:

Not Authorized

Read-only Railway commands work, and my account/workspace is verified.

New project:

  • NELA Ride
  • Project ID: 38f857ce-057d-4bad-ae35-fd9e83fc1620

New services:

  • API service ID: bf4a52e6-6885-419c-80e4-1c06d406dd93
  • Admin service ID: 4f701124-6d91-4452-bb66-fa55bf9a1884

Please manually attach or fully clear permission/domain claims for:

  • api.nelaride.com → API service bf4a52e6-6885-419c-80e4-1c06d406dd93
  • admin.nelaride.com → Admin service 4f701124-6d91-4452-bb66-fa55bf9a1884

The TXT verification records are still present.



Status changed to Awaiting User Response Railway about 1 month ago


Status changed to Solved Anonymous about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...