LSIO doesnt need or use the WebUI plugin...in fact you are showing screenshots FROM the WebUI, so I'm not sure why you are trying to enable it. It runs the deluge-web daemon which connects directly to the RPC endpoint in deluged.
Just go ahead and navigate to port 8112 for the container.
If it's failing to start it's probably because the host is already using 8112 (default) in the image with deluge-web. It will fail because the port is in use, so this seems normal. Change your port in WebUI and it will probably enable, as this is expected behavior.
You also need to change some of these settings, particularly if you're looking to seed on private trackers.
Uncheck all numbered checkboxes, specifically #1 as this will prevent Deluge from setting the port to the one you have forwarded/exposed in Docker (6881 - which you can change if you do so in both compose and Deluge if you want, this is the default torrent port and generally its more recommended to pick a random port between 10000-65535 than use 6881)
i have done what you told me, change it to port 8113 in the compose and now the UI is availble in that port.
Also unchecked all the numbers in the Network TAB, but still can't enable the WebUi Plugin or connect to it using[url][/url] Sonarr
I'm not sure where your confusion stems from, but to be very clear. You DO NOT need to enable the WebUI plugin for Linuxserver's Deluge container.
What you just did was unnecessary by changing the port to 8113, as your previous screenshots are all from the WebUI to begin with (I assume) when it was running on port 8112, you are needlessly trying to enable WebUI.
You should also use 'docker logs deluge' to see the logging that the container does, it will show you errors (you can set the 'DELUGE_LOGLEVEL' environmental variable to debug if you need to, in the future, get more logging details - but you do not need to do so in this case)
Your compose was fine before, your settings in Deluge were not. You fixed those, and can stop trying to enable the WebUI plugin.
The problem with connectivity is unrelated to Docker, you are pasting screenshots from the webui to begin with, so it is clearly functioning. You need to explain your Radarr configuration/instance a bit for me to help you out. Alternatively, if you are new I would suggest checking out the Servarr discord (I'm there) and we can discuss this in more detail there "in person" if you need. Simply tag me when you join, my username is @zak.ary FYI.
Are you running Radarr in a docker instance as well? If so are you using a custom docker network? You shouldn't be referencing docker -> docker communication with the router/host IP...use a custom docker network instead.
Timeouts are generally due to firewalls, but you should probably go the Servarr forums or Discord for help with Radarr. Clearly the WebUI is working so Deluge is functioning properly.
Deluge
