[bug] Local storage backend shows Oops! Not found error

[uwu64]

Description of the bug

After logging in to a simple setup with HTPASSWD authentication and Local storage, the screen shows an error and no further action is allowed. I notice that no matter what is entered into the Path of admin panel, GET request is sent to host:8334/api/files/ls?path=%2F and returns 404 every time. I have verified that directories do in fact exist on my machine

Step by step instructions to reproduce the bug

• Install Filestash docker image per installation guide and choose an admin password.
• Go to Backend tab, deselect all choices except LOCAL for storage backend and HTPASSWD for authentication middleware.
  • Alternatively, use PASSTHROUGH instead of HTPASSWD, with username_and_password as strategy
• Enter some test user in HTPASSWD, like testuser:fogbank
• Under Attribute Mapping, select the name of the Local storage backend, then enter your admin password, and choose any path that exists, like /home/. If using Passthrough, /home/{{ .user }}/ should work, according to this reddit post by the main author.

Can you replicate that error from the demo?

No

Observed behavior

Navigating to host:8334 redirects to host:8334/files/ and the error Oops! Not found is displayed after a brief loading spinner.

Expected behavior

Directory is visible and can interact with folders and files

[simonoricardo]

I encounter the same issue using PASSTHROUGH and direct.

I'd be happy to rollback to an older version if anybody would know one on which it is not broken, for the time being :)