is this the expected output?

should be .

so.. do you still get the err connection closed error? if you still facing the error, it's probably something wrong on your network, or try open it in incognito tab

thank you , tried in incognito, same error ERR_CONNECTION_CLOSED and no new http logs

it must be a Railway problem, as ALL /api/* is broken at Railway edge. It might becasue my credit card was disabled a few days ago, although it looks like Railway got money from it successfully, now a new card has been added, but the problem persist, do you know how to get a railway staff to look into this?

You have it connected to a github repo right? Could be worth trying to spin up a duplicate project. See if that fixes it - take down your other one so you don't spend double on compute.

yes, github repo is connected. I just duplicated the project, same error with "https://yourmusic-copy-production.up.railway.app/api/health"

This is a critical platform issue. The domain binding is completely broken despite multiple redeploys and config resets.

Let me check if there's a configuration error that's preventing the domain from being registered:

Fetched service config

Config is correct. The issue is on Railway's edge/routing layer, not your service config.

You need to contact Railway support directly. This is a platform infrastructure issue:

Your service is running and healthy (passes health checks)

The domain is correctly configured in your service settings

Multiple redeploys and config resets have failed to restore routing

The edge is returning 404 Denied instead of routing to your service

What to tell support:

Service: yourmusic (ID: 0a7e17a2-6180-42cd-bbd3-20aaac13600f)

Environment: production (ID: 4ea550d8-25d3-4232-a680-ffa2438f1b56)

Domain: yourmusic-production.up.railway.app

Issue: Domain returns HTTP/1.1 404 Denied from edge, service is online and healthy

Attempted fixes: 2 redeploys, removed/re-added domain config, all failed

Current deployment: f63be1a3-3781-41a5-b74f-e0902ad3637a (SUCCESS)