Hey there! We've found the following might help you get unblocked faster:

• 🧵 Kong dns resolution error

• 🧵 Internal Networking Issue: Prometheus Cannot Connect to Django App Despite Correct Configuration

• 🧵 Railway Project Domain Not Resolving (DNSPROBEFINISHEDBADCONFIG) — App Running, Logs OK

• 📚 Create a Bridge from Railway to AWS RDS with Tailscale

If you find the answer from one of these, please let us know by solving the thread!

No none of these helps

My domain is app.chartchats.com that I am trying to add as custom domain

It should be the fin-chart-ui service and not fin-chart

I have deleted the previous exiting domain and added a new one
Still getting the same issue

Don't know why was this issue coming in the first place.

Also a lot of time fin-chart backend service goes un responsive. Login endpoint suddenly does not respond and it starts being unresponsive. This has happened a lot of times and just redeploying the service starts the backend service. Why is this happening again and again ?

Please can you find some solution to this ?

Hello,

I'm not seeing any issues with that domain. It appears to be working fine and is successfully attached to this service:

https://railway.com/project/a275ec99-c269-42b5-9670-fe5f37eac660/service/3a597e3c-eb9b-446c-bfcb-768dbed953a8/settings?environmentId=32a0b277-2d43-4861-af85-a6949bcb0705

Could you provide more details about the specific issue you're experiencing? This will help me better understand what you're seeing on your end.

Best,

Brody

Hi, I am sorry but this wasn't a domain issue

Again and again the backend service which is fin-chart stops accepting the endpoints, the service kind of stops altogether. After this incident none of the endpoints are reachable and this has happened to us a number of times.

We just restart the service which make it up and running. But why is this happening form your side ?

Just 20 mins ago we experienced this and the website not responding appropriately is costing us users and money

Hello,

It looks like your service sometimes pins itself at approximately 1 vCPU. This would be indicative of running a single-threaded or synchronous process, since the maximum vCPU it could use would be 1 vCPU. When this happens, a common pattern would be that the application would be unable to answer further network requests.

Since this application is run with Uvicorn, I would look into optimizing Uvicorn's configuration, or, most easily, add more replicas to your service from the services settings to scale out horizontally.

But since the solution requires application-level configurations on your side, I will open this thread up to the community so that they can help you with that, as the Railway team can only provide support for the platform and product side of things.

Best,
Brody