ERR_CONNECTION_TIMED_OUT error is returned in the site after deploing a Django application to Heroku

I just re-deployed an application in the new Eco Dyno and provisioning a new PostgreSQL datbase, however after deploying successfully, when I try to open the application, this HTTP error is returned ERR_CONNECTION_TIMED_OUT and the application never opens. I also updated the stack from heroku-20 to heroku-22 and it is not working on both. Is there any additional configuration that I need to complete?

This is the log from the latest deploy

2023-01-30T22:13:55.000000+00:00 app[api]: Build started by user
2023-01-30T22:14:32.846408+00:00 app[api]: Deploy c6f350bc by user
2023-01-30T22:14:32.846408+00:00 app[api]: Release v23 created by user
2023-01-30T22:14:33.126404+00:00 heroku[web.1]: Restarting
2023-01-30T22:14:33.141734+00:00 heroku[web.1]: State changed from up to starting
2023-01-30T22:14:34.066230+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2023-01-30T22:14:34.109732+00:00 app[web.1]: [2023-01-30 22:14:34 +0000] [4] [INFO] Handling signal: term
2023-01-30T22:14:34.109979+00:00 app[web.1]: [2023-01-30 22:14:34 +0000] [9] [INFO] Worker exiting (pid: 9)
2023-01-30T22:14:34.110205+00:00 app[web.1]: [2023-01-30 22:14:34 +0000] [10] [INFO] Worker exiting (pid: 10)
2023-01-30T22:14:34.310286+00:00 app[web.1]: [2023-01-30 22:14:34 +0000] [4] [INFO] Shutting down: Master
2023-01-30T22:14:34.461478+00:00 heroku[web.1]: Process exited with status 0
2023-01-30T22:14:35.372879+00:00 heroku[web.1]: Starting process with command `gunicorn aselsi.wsgi`
2023-01-30T22:14:36.441571+00:00 app[web.1]: [2023-01-30 22:14:36 +0000] [4] [INFO] Starting gunicorn 20.1.0
2023-01-30T22:14:36.441910+00:00 app[web.1]: [2023-01-30 22:14:36 +0000] [4] [INFO] Listening at: (4)
2023-01-30T22:14:36.441956+00:00 app[web.1]: [2023-01-30 22:14:36 +0000] [4] [INFO] Using worker: sync
2023-01-30T22:14:36.447323+00:00 app[web.1]: [2023-01-30 22:14:36 +0000] [9] [INFO] Booting worker with pid: 9
2023-01-30T22:14:36.521146+00:00 app[web.1]: [2023-01-30 22:14:36 +0000] [10] [INFO] Booting worker with pid: 10
2023-01-30T22:14:36.588676+00:00 heroku[web.1]: State changed from starting to up
2023-01-30T22:14:37.000000+00:00 app[api]: Build succeeded
2023-01-30T22:17:56.524340+00:00 app[api]: Starting process with command `python migrate` by user
2023-01-30T22:17:59.955485+00:00 heroku[run.7847]: State changed from starting to up
2023-01-30T22:18:00.056845+00:00 heroku[run.7847]: Awaiting client
2023-01-30T22:18:00.078452+00:00 heroku[run.7847]: Starting process with command `python migrate`
2023-01-30T22:18:05.101096+00:00 heroku[run.7847]: Process exited with status 0
2023-01-30T22:18:05.175678+00:00 heroku[run.7847]: State changed from up to complete

I re deployed from github making minor changes on the code to be sure that the most recent changes are being deployed properly. I updated the heroku stack to make sure that was not the problem. I also ran migrations after the application is deployed and they are applied successfully so the only problem is that the site is not reachable for some reason.

Back to Top