-
-
Notifications
You must be signed in to change notification settings - Fork 810
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
Log in issue when site URL changed #8750
Comments
@Corn-101 I have just tried to reproduce this but it seems to be functioning as intended on my end.
You should be able to find some docker logs as well as information from your browser, please post anything you can find |
Thank you. This is exactly the instructions I have followed, it seems my pasted link didn't work. Hopefully these logs have some hint, what's going on. Location of Caddyfile, .env and docker-compose is /opt/inventree/. INVENTREE_EXT_VOLUME=./inventree-data as well as config.yaml is located in this inventree-data -folder. My understanding is that it does accept the credentials, but it somehow fails to redirect to the home page... |
I managed to fix this. I had to add following lines to .env file: |
Deployment Method
Steps to Reproduce
Describe the problem*
I previously opened topic in Q&A of this but it seems it's not monitored so hopefully get answers from here. Here's the original post: https://github.com/inventree/InvenTree/discussions/8666#discussioncomment-11632144
So the issue is that Inventree Docker production installation when I change INVENTREE_SITE_URL from .env file from default inventree.localhost to
INVENTREE_SITE_URL="http://192.168.1.102"
I cannot login anymore. It seems to check the credentials as if I input deliberately wrong username/pwd, I get error message. But with correct credentials it just refreshes the page but wont let me in. With the default inventree.localhost I can log in normally. I've also tried to change the Caddyfile site url, but it didn't help. I've also tried to install everything from scratch (fresh Debian 12 install etc.) already two times, and every time the same issue. Could this be bug or am I missing something? Thank you.Steps to Reproduce
Relevant log output
The text was updated successfully, but these errors were encountered: