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 returned #712

Open
camilotabaresj opened this issue Mar 13, 2024 · 5 comments
Open

Bad Gateway returned #712

camilotabaresj opened this issue Mar 13, 2024 · 5 comments

Comments

@camilotabaresj
Copy link

camilotabaresj commented Mar 13, 2024

I'm trying to run the full project using pipx and docker-compose. But when i try to get in the frontend path http://localhost/login it returns Bad Gateway
Screenshot 2024-03-13 at 3 01 09 PM

The logs are

  1. proxy-1 | time="2024-03-13T20:01:03Z" level=debug msg="'502 Bad Gateway' caused by: dial tcp 172.25.0.2:80: connect: connection refused"
  2. proxy-1 | time="2024-03-13T20:09:51Z" level=error msg="the router fastapi-project-frontend-https@docker uses a non-existent resolver: le"
@heiqs
Copy link

heiqs commented Mar 23, 2024

post more info on your system, your hosts file, and your .env. Make sure 127.0.0.1 is mapped to localhost.

@openSourceBugs
Copy link

This has been an ongoing issue for at least 2 months with multiple people posting that this is a problem. The front end is requesting https login and the backend is responding with a bad gateway. None of the responses have been helpful so far such as "clone an earlier branch" "post more info" "rebuild everything in docker". It's a configuration issue somewhere with https but no one seems to know what the issue is.

@JacobFV
Copy link

JacobFV commented Apr 29, 2024

what @openSourceBugs said ^^^

@tomeli5n
Copy link

tomeli5n commented May 17, 2024

This has been an ongoing issue for at least 2 months with multiple people posting that this is a problem. The front end is requesting https login and the backend is responding with a bad gateway. None of the responses have been helpful so far such as "clone an earlier branch" "post more info" "rebuild everything in docker". It's a configuration issue somewhere with https but no one seems to know what the issue is.

It is a client-side misconfiguration. Previously in the logs, the backend service shows:

backend-1   |   Value error, The value of SECRET_KEY is "changethis", for security, please change it, at least for deployments. [type=value_error, input_value={'SECRET_KEY': 'changethi...N_REGISTRATION': 'True'}, input_type=dict]

So it is mandatory to configure a non-default SECRET_KEY

@jb-delafosse
Copy link

jb-delafosse commented Jul 15, 2024

Actually it is an issue in the network config of the proxy service that has already been fixed on master but have yet to be released.
#1184

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

6 participants