-
Notifications
You must be signed in to change notification settings - Fork 704
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
[bug] "Oops! Invalid account" when using password_only middleware for local folder #687
Comments
I wonder if I can get some help here? |
It took me a while to understand how everything works as well, unfortunately there is absolutely no documentation if you are not a paying customer. I also got the 'invalid account' error a few times, and in my case the problem was that the path was not correct. In your screenshots the path is empty as well. And as far as I understand, the passthrough authentication is best used for example if you are trying to login with SSH, and you can passthrough the credentials from the login page of Filestash to SSH. If you just want users and passwords, the htpasswd authentication is the easiest. Just don't forget to fill in your Admin password and the correct path in the two fields below under LOCAL. Also remember that if you run Filestash under docker you need to pass your storage to your docker container, and use the correct path from inside the docker container. |
Oh I see. Now it is clearer for me. Thank you so much! I got it working now with htpasswd. |
Description of the bug
I am trying to use
password_only
to allow user entering just password to access my local folder.After filling up both password and path fields, I tried to log in as the user. But was greeted with this error
Also something is weird. If I chose
username_and_password
, I still getting only 2 fields showing up,Admin Password
andPath
. I don't understand if this is how it should be or there is a mistake somewhere.Step by step instructions to reproduce the bug
Can you replicate that error from the demo?
No, since my issue is for local storage.
Observed behavior
Greeted with error when trying to login user.
Expected behavior
Able to view files.
The text was updated successfully, but these errors were encountered: