You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey everyone, I am pretty new to Docker and I have this issue that I have been dealing with for days. My containers are running fine, but then I can’t access my app from the browser. I get the response " This page isn’t working
0.0.0.0 didn’t send any data.
Reproduce
docker compose up -d runs the containers all fine. The container logs show no errors. I have reset the database, and also done a recent migration.
Some internet articles suggested checking the internet connection, I did that and also reset my network connection. I also tried tethering off of my phone, just to be sure.
I have cleared my cache, cookie and browsing history. I have tried using a different browser too. I also disabled my browser extensions. I have tried to open the server in an incognito browser.
I tried to change the port and also add a health check for the database to make sure it’s healthy before the django app starts. I also added a wait for the database script to ensure the app doesn’t try to connect to the database before it is ready.
I tried to run it on a windows laptop, and everything worked just fine. Also, my firewall is off on my mac and I am using macOS ventura 13.5.2.
Expected behavior
docker compose up -d should let me access the app successfully at http://0.0.0.0:8000/
docker version
4.34.2
docker info
Container rhs_soccer_local_redis Started 0.2s
✔ Container rhs_soccer_local_mailpit Started 0.2s
✔ Container rhs_soccer_local_postgres Healthy 5.7s
✔ Container rhs_soccer_local_celeryworker Started 0.3s
✔ Container rhs_soccer_local_celerybeat Started 0.3s
✔ Container rhs_soccer_local_flower Started 5.8s
✔ Container rhs_soccer_local_django Started
Additional Info
also tried to enter the container using curl and I am getting " (52) Empty reply from server . Here is my docker compose file .
@wanjiru-njuguna , seems like there might have a couple of issues in the dokcer-compose configurations. I am trying to give some suggestions that might help_
The ports you specified use curly quotes (‘8000:8000’) instead of straight quotes ("8000:8000"). Docker Compose requires standard double (") or single (') quotes for port mappings.
Ensure that your ALLOWED_HOSTS setting in the Django settings.py file includes localhost and 0.0.0.0.
As the containers are running fine, you can check the container logs which might indicate why it is not responding using this command, docker logs rhs_soccer_local_django.
Description
Hey everyone, I am pretty new to Docker and I have this issue that I have been dealing with for days. My containers are running fine, but then I can’t access my app from the browser. I get the response " This page isn’t working
0.0.0.0 didn’t send any data.
Reproduce
docker compose up -d runs the containers all fine. The container logs show no errors. I have reset the database, and also done a recent migration.
Some internet articles suggested checking the internet connection, I did that and also reset my network connection. I also tried tethering off of my phone, just to be sure.
I have cleared my cache, cookie and browsing history. I have tried using a different browser too. I also disabled my browser extensions. I have tried to open the server in an incognito browser.
I tried to change the port and also add a health check for the database to make sure it’s healthy before the django app starts. I also added a wait for the database script to ensure the app doesn’t try to connect to the database before it is ready.
I tried to run it on a windows laptop, and everything worked just fine. Also, my firewall is off on my mac and I am using macOS ventura 13.5.2.
Expected behavior
docker compose up -d should let me access the app successfully at http://0.0.0.0:8000/
docker version
docker info
Additional Info
also tried to enter the container using curl and I am getting " (52) Empty reply from server . Here is my docker compose file .
Any help will be highly appreciated and also, if more information is needed I am more than happy to provide that.
The text was updated successfully, but these errors were encountered: