-
Notifications
You must be signed in to change notification settings - Fork 15
0.9-rc: 502 Bad Gateway #91
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
Comments
Try env LOG_LEVEL=debug |
any news about this? happened again? |
i added the LOG_LEVEL but it doesn't show anything. If no one gets the 502 error, then I'll just chalk it up to my setup. I know how to quick recover from it. |
could it be that you had previous version cookie set at time of first launch? (Do you resolved with just that cleanup? it never happened again?) |
no it still happens. I checked my nginx proxy logs and found this. Don't know if it helps. |
could you try to run docker image with env HOST=0.0.0.0 |
and since we are here: are you on arm or amd64? |
i'm on x64. I'm not sure what you mean by HOST=0.0.0.0. I use docker compose. I think you should just skip this and fix the app functionality issues first. |
After updating image to 0.9-rc-001 and adding HOST: 0.0.0.0 to my docker compose it didn't startup at all. I looked at the docker logs and it looks like now it's requiring TOKEN_SECRET. So I added that and the container started up, but unfortunately the behavior with the 502 Bad Gateway Errors remain the same. So are you saying this doesn't happen to anyone else? I'd say don't bother fixing it then. I don't feel like troubleshooting anymore. |
tbf yours is only feed like this i received. |
I'll close this for now, if you change your mind and wanted to give snapp another chance i'll be here :) |
I have the same issue in 0.9-rc-019 |
That peoblem also comes with the fact, that everything exept the homepage and /admin throw 502 |
Try remove host, Set Public URL equal to Origin, and put log_level=debug If it doesnt show anything i can make a debug versione full of logs ad hoc for debugging this problem |
All I have to do is login and then do a refresh on the browser and 502 Bad Gateway error pops up. Somehow it's saving some data that's causing this. If I clear the data/cookie data, the error goes away.
The text was updated successfully, but these errors were encountered: