-
Notifications
You must be signed in to change notification settings - Fork 801
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] Redirecting to 127.0.0.1:8334 #787
Comments
Thank you very much, I wrote the domain name, it helped. It didn't work like that before. |
Would love to get your insight onto how to make this better then. The main reason this was added (very recent addition indeed) is many people had this configured but wouldn't be able to login with a end user message showing: "not allowed" which was confusing as to why it wasn't allowed, hence this solution to redirect the user to the correct URL if he's coming from something wrong. |
Hi, I think updating setup instructions at https://www.filestash.app/docs/install-and-upgrade/ could be enough. Now it's possible that people just curl docker-compose.yml, run "docker-compose up" and try to reach application without knowing about variable "APPLICATION_URL=127.0.0.1:8334" in docker-compose.yml. If instructions would have a step about validating / updating docker-compose.yml file with some explanations about its content before "docker-compose up"-part, people might get APPLICATION_URL-variable right before trying to reach app. I had checked contents of docker-compose.yml so I was able to guess why I'm redirected to 127.0.0.1:8334. |
[bug] Redirecting to 127.0.0.1:8334
The text was updated successfully, but these errors were encountered: