Public domain times out while service is running
mariam-hossam-saleh
HOBBYOP

2 months ago

I am experiencing an issue with a Railway service where the application is running correctly, but the public HTTP domain is unreachable.

Current behavior:

  • The service deploys successfully.

  • The container starts without errors.

  • The Node.js/Express server is listening on 0.0.0.0:8080.

  • MongoDB connects successfully.

  • Logs confirm the server is running:

     Accounting Server running on port 8080
     Connected to MongoDB successfully
    
  • However, accessing the public domain results in:

    ERR_CONNECTION_TIMED_OUT
    

Expected behavior:

  • The service should be reachable via its public domain over HTTP.

Additional details:

  • The application was working normally with the same deployment and configuration approximately one hour before the issue occurred.

  • No code or configuration changes were made before the issue started.

  • The public networking domain exists and is mapped to port 8080.

  • The application correctly binds to 0.0.0.0 and the exposed port.

  • The issue occurs even when accessing the domain directly in a browser (not only from the frontend app).

Solved

1 Replies

parmstar
EMPLOYEE

2 months ago

I am not seeing a timeout now? Can you check again?


Status changed to Awaiting User Response Railway about 2 months ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway about 1 month ago


Loading...