Replies: 5 comments
-
|
I have also used I also tried |
Beta Was this translation helpful? Give feedback.
-
|
I have also tried editing both Still cannot load the frontend, Here is more context for the error about headers: |
Beta Was this translation helpful? Give feedback.
-
|
I was able to build manually and can access everything through the browser. The only environment variable I set was I'm curious why |
Beta Was this translation helpful? Give feedback.
-
|
Since I've got this up and running, I am having the "Error writing file" issue. I posted in the existing issue. |
Beta Was this translation helpful? Give feedback.
-
|
To answer your original question, if you revert any edits, you should be able to either Alternatively, you can
Regarding the |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using docker (with GPU) and can't seem to find the right spot to enable
ALLOW_ALL_HOSTSWhen I clone the repo and start the containers using
docker-compose -f docker-compose.gpu.yml -f docker-compose.prod.yml -f docker-compose.prod.selfhost.yml upthe following error appears in the docker logs when attempting to visit http://10.0.80.10:80 (IP address of the docker host running Spleeter-web):The browser on my laptop shows:
Bad Request (400)Makes sense. However, when I add
=1to- ALLOW_ALL_HOSTSunder theapiservice indocker-compose.gpu.yaml, the container won't start:Removing
=1and starting the containers again gets the app to start, but I still cannot access it from a remote host.Where's the right spot to enable
ALLOW_ALL_HOSTS?Thanks!
Beta Was this translation helpful? Give feedback.
All reactions