Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad Gateway 502 #42

Closed
AdamLee321 opened this issue Feb 18, 2024 · 3 comments
Closed

Bad Gateway 502 #42

AdamLee321 opened this issue Feb 18, 2024 · 3 comments

Comments

@AdamLee321
Copy link

I am getting a 502 Bad Gateway when running get started I noticed the same issue on two other endpoints in the console too. I have attached screenshots in case anyone knows the answer. Thanks in advance.

Screenshot 2024-02-18 203350
Screenshot 2024-02-18 2033501

@3choBoomer
Copy link

I experienced this on an older machine that could not handle running the multiple docker containers needed for this application.

I moved to a newer and faster machine and it worked fine.

@tomch3ng
Copy link
Contributor

Are you using a Mac? I encountered this issue on my Mac, and it's because the server container defaults to port 5000, but that's in use by MacOS. You can confirm this by this error message in the console:
Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:5000 -> 0.0.0.0:0: listen tcp 0.0.0.0:5000: bind: address already in use
Docker Desktop or docker ps would also show two of the seven containers in "Created", but not "Running" state:
Screenshot 2024-05-27 at 5 01 05 PM

To fix this, simply change line 42 in docker-compose.yml to - "5001:5000" # flask from - "5000:5000" # flask.

@mtalcott
Copy link
Owner

I have merged @tomch3ng's port remapping fix, #48. @AdamLee321 @3choBoomer this should fix your issue, please confirm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants