qBittorrent 5.0 w/local theme-park docker

[Lebowski89]

Hi

Deploying a Hotio qBittorrent container locally with a local theme-park container along side. Have followed the following steps which have worked for every other Hotio container (that has a theme-park file in the docker-mods folder of theme-park):

Have bound the theme-park file to the qBittorrent container:

  - '{{ qbittorrent_themepark_paths_location }}/docker-mods/98-themepark-qbittorrent:/etc/cont-init.d/98-themepark'

Have given the qBittorrent container the following theme-park envs:

  TP_SCHEME: 'http'
  TP_DOMAIN: '{{ qbittorrent_themepark_domain_local }}'  (machine ip + host port of theme-park container)
  TP_HOTIO: 'true'
  TP_THEME: '{{ qbittorrent_themepark_domain_local_theme }}' (hotpink)

(And have made sure the above variables have values and that the theme-park container is up and serving themes to other containers)

The result is this:

No theme has been applied. The theme-park container logs show nothing, but the qBittorrent container shows this:

And this is added to the qBittorrent config file:

I'm also running themes via traefik subfiltering on the same container (with the csp headers) and it correctly provides a theme:

Not sure why it isn't working. Have had no issue with lidarr/radarr/sonarr/whisparr/prowlarr - and the only thing I've really had to change between them was the value following '98-themepark-'... 98-themepark-radarr, 98-themepark-sonarr, 98-themepark-qbittorrent, etc.

Edit: Contents of the docker-mods folder in the theme-park container appdir shows the qbittorrent file

Any ideas?

Container info:

[GilbN]

Do you have any errors in the browser console? Does the html get edited with the theme park style tags when you look at the elements in the browser console?

[CLHatch]

Looking at the config file screenshot, the underlying issue appears to be the same as this issue, the config lines being placed in the wrong section. #688

[Lebowski89]

Can confirm, that's all it was - wrong section. Thanks :)