Closed draculya666 closed 10 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Likely need to remove the custom webui location from your config.
It looks like is not downloading the files and creating the /themepark folder. I pulled this from the logs:
Variables set: 'APP_FILEPATH'=/config/qBittorrent/qBittorrent.conf 'TP_DISABLE_THEME'= 'TP_HOTIO'= 'TP_DOMAIN'= 'TP_COMMUNITY_THEME'= 'TP_SCHEME'= 'TP_THEME'=overseerr
Downloading qBittorrent webui to "/themepark"..please wait
Download finished
Downloading qBittorrent webui icons to "/themepark/xxx"..please wait
Download finished
Stylesheet set to overseerr on /themepark/public/index.html
I've also removed the variables: DOCKER_MODS: ghcr.io/gilbn/theme.park:qbittorrent TP_THEME: overseerr
from the container which gives this log: [custom-init] No custom files found, skipping... WebUI will be started shortly after internal preparations. Please wait...
**** Information **** To control qBittorrent, access the WebUI at: http://localhost:8080
[ls.io-init] done.
but the problem persists
UPDATE:
Changed "WebUI\AlternativeUIEnabled= " from true to false and reagined access.
I'll check with the themapark team if something more is needed but the mod variables are exclusive to use with lnuxserver.io containers, which made me to report it here. Thx for all the help
You need to check in with the theme park mod to see if there are changes needed to be made.
Changed "WebUI\AlternativeUIEnabled= " from true to false and reagined access.
I'll check with the themapark team if something more is needed but the mod variables are exclusive to use with lnuxserver.io containers, which made me to report it here. This is the only container with issues, since all the arr's have the same docker mod variable and are working fine
While yes they have exclusive lsio env's (and Gilbn is part of our team) - they aren't developed exclusively by us and in our docker mod repo so you would need to report issues directly to them.
Is there an existing issue for this?
Current Behavior
when accessig the IP I get this message in the browser "Unacceptable file type, only regular file is allowed." The arr's are able to connect. Only the WebUI ins't. Already removed the docker mods for the custom theme args to no avail
Expected Behavior
No response
Steps To Reproduce
run the docker
Environment
CPU architecture
x86-64
Docker creation
Container logs