-
-
Notifications
You must be signed in to change notification settings - Fork 792
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
502 Bad Gateway error on fresh Debian 11 install #8494
Comments
There is not enough info to debug this here @mschaffner9239 . The log is from nginx, not the inventree server, and the described things can be a thousand things. |
I also have gotten this error from the installer; on a fresh Ubuntu 22.04 install;
Initially it seemed like the installer failed to properly install packages. Initially - the gpg file failed to install/write - even after using sudo - fixed that
I fixed the broken package - then ran the installer again - which properly installed the packages without any issue - but still got a 502. Oddly the services all show active
From #6349 (comment) - I checked for the maintenance mode - but it still doesn't work. Next attempt is a full new VM running 24.04 - but not sure how much that will change things as it's also an LTS. |
Seems like this is related? #8495 |
All, I have just release |
Hi Oliver, I attempted an install on Debian 12 and it stopped with a different issue, see log below:
|
@mschaffner9239 we are playing whack-a-mole here... Some quick googling of this new error shows that maybe there is a version incompatibilitity with another package already installed on your system? Can you show the output of: pip show pillow
pip show PIL References |
Hi Oliver, My apologies, the above was meant for the other ticket. I did an install of 0.16.9 on Debian 11 and so far that seems to be working correctly. I'll move over that previous message to the proper ticket. Mike |
Please verify that this bug has NOT been raised before.
Describe the bug*
After creating a fresh Debian 11 VM and installing InvenTree, everything seems to be fine. Able to login with the provided admin from the installer script. After rebooting the VM, no longer able to login, when trying to reach the server, getting a '502 Bad Gateway' error message.
Steps to Reproduce
Expected behaviour
After reboot of the VM, that the login screen would appear.
Deployment Method
Version Information
0.16.8 based on first login.
Please verify if you can reproduce this bug on the demo site.
Relevant log output
The text was updated successfully, but these errors were encountered: