Subject: CONFIGURE_NETWORK Stage Stuck - Custom Domain Issue

tarek-unitx

PROOP

2 months ago

Hi Railway Support,

I'm experiencing a critical deployment issue with my service in the project. All deployments are hanging indefinitely at the CONFIGURE_NETWORK stage.

Service builds and creates containers successfully
Deployment hangs at CONFIGURE_NETWORK stage (10+ minutes, no timeout)
This has affected 7+ consecutive deployments since March 20, 2026

Suspected Root Cause: I have two custom domains configured via Cloudflare: One of these domains appears to be in a corrupted or stuck state—I cannot remove it from the service configuration, and it's not appearing in the service config API response, yet it seems to be blocking network configuration.

Troubleshooting Steps Taken:

Redeployed multiple times
Removed all service domains from the configuration
Attempted to remove the problematic custom domain (unable to remove)
Verified the application builds and starts successfully (Next.js ready in 133ms)

Current Status: The latest deployment (45dfdbdc-5ec5-41dc-85be-6d91dda6e2cc) was triggered with zero service domains to test if the custom domains are the culprit.

What I Need:

Force-remove any stuck/corrupted custom domain configurations from my service
Investigate why CONFIGURE_NETWORK is hanging
Restore normal deployment functionality

Please advise on next steps.

Solved

9 Replies

darkoatanasovski

HOBBY

2 months ago

the same for me!

gainsgoblin

PRO

2 months ago

Same issue here

darkoatanasovski

HOBBY

2 months ago

I recreated the service, and when I'm trying to add new custom domain, I get error:

Error adding custom domain

Failed to create custom domain, please try again

the response code from their api endpoint returns 200 OK, but the response body is:

{
  "errors": [
    {
      "message": "Failed to create custom domain, please try again",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "customDomainCreate"
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR"
      },
      "traceId": "15554770086350771313"
    }
  ],
  "data": null
}

chandrika

EMPLOYEE

2 months ago

Hi, we're aware of an issue affecting custom domain operations right now. I've raised it with our engineering team and we will investigate the issue. Really sorry for the inconvenience here!

Status changed to Awaiting User Response Railway • 2 months ago

darkoatanasovski

HOBBY

2 months ago

@chandrika, could you please update your status page, so we can follow the updates there? thanks

Status changed to Awaiting Railway Response Railway • 2 months ago

darkoatanasovski

@chandrika, could you please update your status page, so we can follow the updates there? thanks

darkoatanasovski

HOBBY

2 months ago

any updates on this? currently we're blocked due to this issue 😐

chandrika

Hi, we're aware of an issue affecting custom domain operations right now. I've raised it with our engineering team and we will investigate the issue. Really sorry for the inconvenience here!

darkoatanasovski

HOBBY

2 months ago

update: it works for new added custom domains, but the ones that was stucked last time (the service is already removed and the domain doesn't exists anymore ) it's still broken. Can you take a look into this?

tarek-unitx

PROOP

2 months ago

Also unable to add new custom domains

EMPLOYEE

2 months ago

Hey! We've removed the orphaned domain from your deleted service, so deployments should no longer be blocked. If you need that domain on your current service, you can re-add it from the Railway dashboard.

@darkoatanasovski @gainsgoblin if you're still experiencing stuck or orphaned domains, please open separate threads with your domain names so we can look them up and clean them up.

Status changed to Awaiting User Response Railway • 2 months ago

Status changed to Solved jr • 2 months ago

Welcome!