That would be the previous container exiting so that the new one can come online.

While that error message does not harm functionality, to avoid it you can update your start command to use node directly, e.g., node dist/index.js

Additionally, you have a TCP Proxy on the service pointed to the port commonly used for Postgres, instead of a domain, may I ask why?

it's just a random port, i even changed it to 5027 but still i can't make calls to the server

the idea is to have a simple api that receives tcp connections

Please remove the TCP Proxy and add a domain to the service that points to the correct port, not a random port.

https://docs.railway.app/guides/public-networking#target-ports

but why remove the tcp proxy?

I will send a request via tcp, my equipment must connect via this address and port that I defined

Are you sure you need TCP and not HTTPS?

yes I'm sure!

Then you need to point the TCP proxy to the correct port.

I did this, but I still can't connect. Can you see what's happening? What's the error? Because I only get a bad request, as if it didn't accept a TCP connection?

How do you know you've pointed it to the correct port?

Are you listening on 0.0.0.0 ?

Yes, I am listening on 0.0.0.0, and I set the port to 5027, then I went to the Railway panel and set the TCP proxy, and it generated this for me:

junction.proxy.rlwy.net:57845 -> :5027

In the client that should connect, I set the IP junction.proxy.rlwy.net and port: 57845,

But when I try to connect, I can't.

Sorry, I don't really know what to tell you, you have something miss configured somewhere.