Skip to content
This repository has been archived by the owner on Dec 4, 2020. It is now read-only.

HTTP 502 Bad Gateway when trying to login in via admin for the first time #34

Closed
mehrad-rafigh opened this issue Jul 9, 2015 · 4 comments

Comments

@mehrad-rafigh
Copy link

Hey guys,

I tried to install taiga on a vm, which fulfills the requirements of taiga. Everything is actually working, but when I try to log in for the first time as admin with 123123 as the password, I'll get the Bad Gateway Error. Did somebody experience the same thing and has an idea how to solve this? Any help is highly appreciated!

@mehrad-rafigh mehrad-rafigh changed the title HTTP 502 Bad Gateway when trying to login in via admin HTTP 502 Bad Gateway when trying to login in via admin for the first time Jul 9, 2015
@bameda
Copy link
Contributor

bameda commented Jul 10, 2015

Hi @mehrad-rafigh

Can you show me your config.json file? Your taiga-front client can connect with your taiga-back server instance.

@mehrad-rafigh
Copy link
Author

@bameda I already fixed it. It seemed that the error was inside the nginx taiga file. I manually added

# Django admin access (/admin/)
location /admin {
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Scheme $scheme;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_pass http://127.0.0.1:8001$request_uri;
    proxy_redirect off;
}

and now it works again. This part was not automatically in my nginx configuration when the installation was finished.

@bameda
Copy link
Contributor

bameda commented Jul 10, 2015

Great! \o/

@sivasai519
Copy link

Hello @bameda

While i was going with this url http://localhost/api/v1 i am getting error in webpage
502 bad gateway
can you please help me

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

No branches or pull requests

3 participants