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
Local Install from script doesn't work. Problem with password and file permissions #625
Comments
Found a few of the issues.
Still not up and running as it's giving an error for invalid e-mail address but, it's a step closer. |
Workaround is to use the CLI. sudo librephotos-cli createadmin USERNAME USER-EMAIL |
I got the exact same issue. Still not managed to get it working on a fresh ubuntu 20.04. |
On the first startup, you should see a "First Time Setup" page where you can create your admin user. The backend probably crashed, because your system hasn't the right requirements. It works fine in the singleton docker image. The second issue is already fixed. |
Hi,
|
Hi.
Workaround:
Good luck! :-) |
running this (minus the sudo) inside the container generates the blow error
|
To resolve: |
With this, you are essentially setting the secret key value to |
it does not work in my side :/ |
When Submitting please remove every thing above this line
π Bug Report
log
filesπ Description of issue:
Started with a completely fresh and fully updated Debian install. I followed the instructions for the local Install. Once install is done the web page is accessible but I can't get past the login screen.
Here is what I have done to try and fix it. I've narrowed down two issues.
I still can't get past the login screen. Mostly because I don't know the username and password. Trying to run librephotos-cli reveals problem number 2.
π How can we reproduce it:
Fresh install of Debian and than follow the instructions for local Install. I've done it three times with the same results. I may have missed something in the instructions but I have followed them fairly closely.
Please provide additional information:
The text was updated successfully, but these errors were encountered: