-
-
Notifications
You must be signed in to change notification settings - Fork 830
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
Persistent Internal Server Error after fresh Digital Ocean droplet deployment v 0.16.8 #8754
Comments
You need to specify the |
@SchrodingersGat thank you for looking at this. This was not necessary the first time I deployed the droplet months ago. I am further confused because the URL and credentials are already provided in the message of the day when I open the SSH terminal. Please understand that I have no experience with Linux and I can barely manage interacting with the console. I do my best to follow instructions and steps others have shared, but I don't really know what I am doing. Maybe Inventree just isn't for me. I tried executing Thanks again for your assistance. |
As you can see in our 0.17.0 release notes under "breaking changes" (and also on the release blog) there is a change to the underlying django code which requires an adjustment to your setup. Read the "Samesite Cookie Fix" section - and this PR for further information |
Had the same issue after upgrading a test server to 0.17.0. Had to change the session cookie as per the above comment and reboot and then also had to rerun the update |
Thank you @StormTrooper, your steps enabled me to access the web login and use Inventree. @SchrodingersGat thank you as well for your direction. May I constructively suggest that the actual steps needed could be more prominently highlighted in the documentation? I realize you are all volunteers and fielding this many support questions requires concise responses. We are lucky to have you investing in a passion project. For the sake of growing the community to users who are not devs or database experts consider that this experience was not the most welcoming for me. I will post the steps to resolve explicitly in the initial post for the benefit of other future idiots (which will be me again I'm sure). Thanks again for everything. |
@levins-law absolutely. I can add it to the FAQ section, as this is a problem which seems to be impacting a few people. Anywhere in the install docs in particular that you think it should go? |
@SchrodingersGat if you want the perspective of a Digital Ocean user who is able to access the SSH terminal (which I was even thought I hit roadblocks after the build) then I would say you want it where mjmair's MoD appears on login. A snippet from the message of the day:
If one follows that link they end up here on the Bare Metal section of the install guide. I think a section right near the Permission Denied Error heading would be appropriate in an [!IMPORTANT] box would help catch the attention of a droplet user. IDK if this is solely a release-dependent thing that will become irrelevant on your next release, but it's a required setup step going forward I would think it's not release-dependent and needs to be listed as a required step. More importantly, droplet users will tend to be lower skill (like me). I get the sense there's no impetus to document the DO droplet deployment by itself, but I would challenge that assumption. Perhaps on the website front end (screenshot below) it would be worth mentioning there are like three extra commands you will need to know. I got into this predicament because I followed the documentation about updating Inventree which broke the hell out of my instance. To quote mjmair
The documentation linked in the MoD is the installer heading, which is full of all sorts of things that perhaps one should not do. This is worth mentioning. I really appreciate the call for feedback and hope it helps others. |
I have made some updates to the install / setup docs here: #8777 |
Important
This was resolved thanks to feedback herein. These were the steps I took to fix it for me.
inventree
command on SSH terminalinventree config:set VAR=VALUE
inventree config:set INVENTREE_SITE_URL=http://162.243.234.188
(replace the URL with your own URL, unclear if this actually fixed the problem, or if the other steps below were the blockers)inventree config:set INVENTREE_COOKIE_SAMESITE=False
inventree restart
inventree run invoke update
(I may have dealt with the missinginvoke
package earlier but you may get a prompt to just do that if you haven't already- and thanks to StormTrooper for the extra step.inventree restart
Deployment Method
Steps to Reproduce
Describe the problem*
I have tried several iterations of deploying a fresh DO droplet. Each time I am now prompted with the following error when I try to access Inventree:
Steps to Reproduce
Click on Quick Access to Inventree
The usual login prompt is missing, goes straight to server error page
Relevant log output
Details
The text was updated successfully, but these errors were encountered: