-
Notifications
You must be signed in to change notification settings - Fork 68
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
Setting web_path results in 404 after setup #120
Comments
are you proxying the container to be /ampache through something like nginx/etc? The container is set to the / path on the webroot you would probably need the local_web_path set as well depending on your setup. There are some issues with docker/proxying that i'll have a search for and see if there's anything in the wiki. cause i'm sure we've had this issue with people before |
I'm not proxying yet, just testing directly. But I'm planning to proxy via either caddy or apache. I'll check |
Adding |
I found a way to fix the 404, but I'm not sure how to fold this into the container so you can easily deploy a new container. I ended up appending the following to
The issue is that docker can't know what the alias will be until after the initial ampache setup in the web UI. |
I'd recommend adding a docker environment variable that can be passed into the ... unless I'm missing something and there's a better way to do this. But on my previous installation (that I'm migrating from) |
I tried to get this baked into my docker compose file, but kept running into issues. So my solution is to script this so after a
Where
|
Docker Compose:
Startup command:
Database connects properly to my host and I am able to have this work (build catalog, stream music, etc) without setting
web_path
in the setup web UI.However, if I set the
web_path
in the web UI to (for example)/ampache
, after the setup completes it only ever returns 404 for/ampache
(also tried/ampache/index.php
or/ampache/login.php
).Going to
/
redirects (302) to/ampache/login.php
which 404s.The text was updated successfully, but these errors were encountered: