Login Issues

[benpayne]

I have a deployment using the docker container deployed to kubernetes. I've had this site running for several months. But I had it setup to deploy "stable", so it was periodically updating and would require DB migration. I'd jump on and do the migration when it showed up and all was good. But recently I did the migration, all looked good, but now I can't login. I'm able to access it from my main browser, I think because of a cookie. But on another browser it fails to login. I've been using google for SSO, but I've disabled this for now and it still fails. It just gives and "authentication error" always. Even on my main browser where I can access the site, I get auth failures if I try and create and change anything. I'm struggling with how to debug this. nothing obvious is showing on the server logs. Any ideas on how to get something to indicate the issue would be greatly appreciated. I've not fixed this deployment at 0.14.3, all migrations are done and the server and workers are updated to 0.14.3.

[SchrodingersGat]

@benpayne after updating to version 0.14.x you will need to review your "site access settings":

https://docs.inventree.org/en/latest/start/config/#server-access

In particular:

• Are you running behind a proxy?
• Are you trying to access the server from a different host?

[benpayne]

@SchrodingersGat when you say "site access settings", can you be more specific to what you're referring to. What there a change in 0.14.x that I specifically need to pay attention to? If you can point to the Issue or commit that would be helpful.

[benpayne]

Ok just notices this in the server:

 Forbidden (Origin checking failed - https://inventree.brsoft.io does not match any trusted origins.): /accounts/login/   

So I guess your saying there's an issue with CORS and the something in 0.14.x changed with regard to this...

[wolflu05]

That error is fine, that exists always, because somewhere is a source map recerenced that does not exist, but as we are already in rewriting the frontend noone has investigated this further.

And regarding the access options, have you had a look at https://docs.inventree.org/en/stable/start/config/#server-access ? How have you configured INVENTREE_SITE_URL, and how do you access Inventree?

[benpayne]

So setting INVENTREE_SITE_URL resolved this issue. I was a bit confused since "base_url" was set in the config already. Not sure what the difference between "base_url" and "site_url" is, both are now set to the same value and it works.

[SchrodingersGat]

@benpayne base_url was not actually doing anything - the variable was mis-labelled in an older version and may have just "stuck around" in your configuration.. Apologies!

[benpayne]

Ok good to know.

Maybe it should be removed from the documentation then too? It's still in the "Basic Options" section just above the link mentioned earlier.

[SchrodingersGat]

@benpayne thanks for letting me know - that's an error in the docs. I'll get that fixed ASAP

[pyhtoncoder0]

I am new to InvenTree and over all a novas at docker. However I too am running a production system under :stable. After doing my update last night I am having this exact issue. However I'm not sure where to specify INVENTREE_SITE_URL. Do I just add this under "environment" in the docker-compose/.env files?

hosted on docker
Id like to remove all proxy stuff tbh. But I don't know how. I use other services to tunnel securely into the network. Any help just removing all this would be appreciated also. However mean time i've just left it as I don't know how to remove properly. I attempted a bare metal installation without proxy but was never able to even access the service locally. I apologize, I know helping with these issues is tedious. I'm a new IT admin of sorts and really struggling right now. I have a full team of people down my case to fix this and I don't really know what I'm doing.