Aplication failed to respond
calico91
PROOP

2 months ago

When trying to consume my backend through the public URL, I get this error. The deployment is performed normally, the backend and database services are active.

$10 Bounty

14 Replies

Railway
BOT

2 months ago


calico91
PROOP

2 months ago

The request does arrive but something is blocking it.

Attachments


dev
MODERATOR

2 months ago

Are you listening on host 0.0.0.0 and do you have the correct port configured in your domain settings under your service settings?


calico91
PROOP

2 months ago


That is the port that is configured in my yml

Attachments


calico91
PROOP

2 months ago

config

Attachments


dev
MODERATOR

2 months ago

I believe what's happening is the request is reaching your service, your service is trying to give it to the deployment, but no deployment is accepting the request. This is usually relating to either not listening on 0.0.0.0 or not listening on the correct port, are you sure your yml defined port is being respected by your application?


calico91
PROOP

2 months ago

Here you can see that my application is starting on port 8080

This is how I have the public URL configured, I don't understand what's happening.


dev
MODERATOR

2 months ago

Did you change the port or something?


calico91
PROOP

2 months ago

In Railway I left it at 8080 since it is the port that my application has by default.

calico91
PROOP

2 months ago

I need help, I don't know what else I can do.


dev
MODERATOR

2 months ago

  1. Ensure your app is actually listening on host 0.0.0.0 and port the port you're mentioning

  2. Make sure your app web server is running and allat

Beyond that, I have no clue


fra
HOBBY

2 months ago

Should the app run on :: instead of 0.0.0.0? Can you do a new deployment, do a request and share all the logs? Maybe there is somethin hidden in the logs

Also can you try connecting via ssh to the container and try to do a curl to the app and see if it you get a response?

Also, are you able to connect to the backend from a different app using the internal URL?

Did you try deleting and recreating the public URL?


fra

Should the app run on :: instead of 0.0.0.0? Can you do a new deployment, do a request and share all the logs? Maybe there is somethin hidden in the logsAlso can you try connecting via ssh to the container and try to do a curl to the app and see if it you get a response?Also, are you able to connect to the backend from a different app using the internal URL?Did you try deleting and recreating the public URL?

0.0.0.0 should be used for public networking, and :: should be used for private IPv6 networking. If an app needs both, it will need to bind dualstack. Doing that varies to the framework.


always backend is the heart of application, in backend are you using supabase or neon, neon better, in neon tables are the core or heart, did you see actual content in tables?


Loading...