Skip to content
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] fresh instance of filestash setup page gives an error #706

Closed
nahsi opened this issue Jul 3, 2024 · 4 comments
Closed

[bug] fresh instance of filestash setup page gives an error #706

nahsi opened this issue Jul 3, 2024 · 4 comments

Comments

@nahsi
Copy link

nahsi commented Jul 3, 2024

Description of the bug

Cannot setup a fresh instance of filestash

Step by step instructions to reproduce the bug

mkdir filestash && cd filestash
curl -O https://downloads.filestash.app/latest/docker-compose.yml
docker-compose up -d

and then go to http://localhost:8334

Can you replicate that error from the demo?

Nope. Only happens on fresh install.

Observed behavior

The requested module '../../model/config.js' does not provide an export named 'get'

Expected behavior

Fresh instance of filestash can be setup

@nahsi nahsi changed the title [bug] [bug] fresh instance of filestash setup page gives an error Jul 3, 2024
@uwu64
Copy link

uwu64 commented Jul 3, 2024

I'm also experiencing this issue. I followed the install guide with the same commands as @nahsi

Some more info - I get the same error message as above when using Chromium, but on Firefox the error message is ambiguous indirect export: get

Going to http://address:8334/about seems to work fine

@zemzema
Copy link
Contributor

zemzema commented Jul 4, 2024

Same problem here!

@uwu64
Copy link

uwu64 commented Jul 6, 2024

Happy to report that it seems to work as of latest updated 8 hours ago. I did the upgrade procedure and was able to set admin password and begin configuring Filestash.

Only at this point I'mm running into another issue with HTPASSWD + Local where no matter what path I choose, it shows Oops Not found error...

@nahsi
Copy link
Author

nahsi commented Jul 23, 2024

Since it works I think it can be closed.
@uwu64 you mind creating another issue for it?

@nahsi nahsi closed this as completed Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants