DBJordan

Can you navigate using your browser address bar to http://yourserver:9595 ? If that works, but you can't get there by clicking the web ui from the unraid docker page, try updating the advanced docker settings for that container to explicitly point to http://yourserver:9595 (the default is something like http://[IP]:[PORT]).

Is it possible qbittorrent's ability to handle dropped packets is more robust than some of the other applications we're using? qbittorrentvpn seems to run qbittorrent ok for me, but even when I connected to that Amsterdam endpoint I'm getting intermittent failures for other programs. From within the qbittorrentvpn container: sh-5.1# while [ true ] > do > curl ifconfig.me > echo "" > done 181.x.x.x curl: (6) Could not resolve host: ifconfig.me 181.x.x.x curl: (6) Could not resolve host: ifconfig.me 181.x.x.x 181.x.x.x 181.x.x.x curl: (6) Could not resolve host: ifconfig.me curl: (6) Could not resolve host: ifconfig.me Edit: might also be that only PIA's ns lookup is wonky right now, which might also explain some of what we're seeing. Edit #2: looks like changing the NAME_SERVERS to 1.0.0.1,8.8.8.8 per posts later in this thread did the trick. Thanks!

Also using PIA. I think something is amiss at PIA. I've tried OpenVPN, Wireguard, and a couple different servers. Packets are getting dropped left and right, DNS resolutions are hit or miss, etc. Started a day or two ago.

I'm not sure I 100% understand the FAQ, but here's what works for me in 6.11.0-rc5. For the VPN (in my case, binhex-qbittorrentvpn), I have: <?xml version="1.0"?> <Container version="2"> <Name>binhex-qbittorrentvpn</Name> <Repository>binhex/arch-qbittorrentvpn:latest</Repository> <Registry>https://registry.hub.docker.com/u/binhex/arch-qbittorrentvpn/</Registry> <Network>bridge</Network> <MyIP/> <Shell>sh</Shell> <Privileged>true</Privileged> ... <WebUI>http://[IP]:[PORT:8080]/</WebUI> <TemplateURL>https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/qbittorrentvpn.xml</TemplateURL> <Icon>https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png</Icon> <ExtraParams/> <PostArgs/> <CPUset/> <DateInstalled>1663291762</DateInstalled> <DonateText/> <DonateLink/> <Requires/> ... <Config Name="radarr port" Target="7878" Default="" Mode="tcp" Description="" Type="Port" Display="always" Required="false" Mask="false">7878</Config> ... <Config Name="VPN_INPUT_PORTS" Target="VPN_INPUT_PORTS" Default="" Mode="" Description="" Type="Variable" Display="always" Required="false" Mask="false">7878,9117,8989,8686,5299,9696,8787,8191,5800,5900</Config> <Config Name="VPN_OUTPUT_PORTS" Target="VPN_OUTPUT_PORTS" Default="" Mode="" Description="" Type="Variable" Display="always" Required="false" Mask="false">7878,9117,8989,8686,5299,9696,8787,8191,5800,5900</Config> <Config Name="AppData Config Path" Target="/config" Default="/mnt/user/appdata/binhex-qbittorrentvpn" Mode="rw" Description="" Type="Path" Display="advanced-hide" Required="true" Mask="false">/mnt/user/appdata/binhex-qbittorrentvpn</Config> </Container> For radarr, I do have the network set to use the VPN container, and I've deleted the 7878 port references from it (except in the WebUI): <?xml version="1.0"?> <Container version="2"> <Name>radarr</Name> <Repository>linuxserver/radarr:nightly</Repository> <Registry>https://hub.docker.com/r/linuxserver/radarr/</Registry> <Network>container:binhex-qbittorrentvpn</Network> <MyIP/> <Shell>sh</Shell> <Privileged>false</Privileged> <Support>https://forums.unraid.net/topic/53758-support-linuxserverio-radarr/</Support> <Project>https://github.com/Radarr/Radarr</Project> <Overview>Radarr - A fork of Sonarr to work with movies &#xE0; la Couchpotato.</Overview> <Category>Downloaders: MediaApp:Video</Category> <WebUI>http://172.16.100.100:7878</WebUI> <TemplateURL>https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/radarr.xml</TemplateURL> <Icon>https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/radarr.png</Icon> <ExtraParams/> <PostArgs/> <CPUset/> <DateInstalled>1661877324</DateInstalled> <DonateText/> <DonateLink/> <Requires/> <Config Name="Host Path 2" Target="/downloads" Default="" Mode="rw" Description="" Type="Path" Display="always" Required="true" Mask="false">/mnt/user/Saidar/_Downloads/movie/</Config> <Config Name="Host Path 3" Target="/movies" Default="" Mode="rw" Description="" Type="Path" Display="always" Required="true" Mask="false">/mnt/user/Saidar/Videos/Movies/</Config> <Config Name="Key 1" Target="PUID" Default="99" Mode="" Description="" Type="Variable" Display="always" Required="false" Mask="false">99</Config> <Config Name="Key 2" Target="PGID" Default="100" Mode="" Description="" Type="Variable" Display="always" Required="false" Mask="false">100</Config> <Config Name="binhex connector" Target="/data" Default="" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/Saidar/</Config> <Config Name="AppData Config Path" Target="/config" Default="/mnt/user/appdata/radarr" Mode="rw" Description="" Type="Path" Display="advanced-hide" Required="true" Mask="false">/mnt/user/appdata/radarr</Config> </Container> I guess I'm abandoning the internal container network or something by doing this, but it works.

Try explicitly specifying (hard coding) the WebUI. Maybe my screen shot wasn't clear enough-- what got it working for me was changing: http://[HOST]:[PORT:9117] to http://172.16.100.100:9117

Try explicitly specifying the WebUI. Change <WebUI>http://[IP]:[PORT:9000]</WebUI> to <WebUI>http://192.168.198.12:9000</WebUI>

Well, I have it working, although I'm not sure it's the most elegant solution. Everything is now working. I just updated webui to hard code the url of the webui instead of relying on things like [HOST], [IP], and [PORT]. See screen capture.

Update: I posted the solution to my issue and marked the original thread over in General as solved. Original text follows: I posted this question over in general support, but this thread might be a better place for it. Screenshots are in the other post. Anyone know what I might change in my docker configurations to get the WebUIs to work for other dockers?

Thanks for the reply. I tried changing HOST to IP without success. I'll check out the container support thread to see if anyone has any ideas.

Hi Squid, Just updated to 6.11-rc3 and seeing the same. Can get to the web ui by specifying my ip:port in the browser address bar but not by clicking from the docker page.

Version: 6.11.0-rc3 I've successfully set up a custom network to route traffic on some of my containers through a VPN. When I try to use Unraid to navigate to the docker's web interface by clicking the docker's icon and drop list, it doesn't work. It opens a new tab that Chrome tells me is called about:blank#blocked. I have to instead enter unraid's url:port in the address bar manually to get to the web UI and am hoping there's a simpler way. Any ideas on how to make the WebUI work from the Unraid page?

I just wireguard working with PIA, but don't seem to be able to find the list of endpoints in the logs, so I'm stuck with the default. Am I looking in the wrong place? Log attached. Thanks for any help. supervisord.log

No problems so far. Thanks for the help trying to get the old hardware working. Can you mark this one solved or whatever it is you do? I'll make a new topic if anything new pops up.

Hmm I'm going to try to replace the motherboard and cpu. They're getting long in the tooth, anyway. Will let you know how it goes!

Still get some intermittent reboots a few times a week. Had a crash and reboot just before 0500. Auto-starting the array after unexpected shutdown is disabled, so the logs say nothing after reboot until I logged in to the webpage at 1123. Have noticed the automated mover exits with a 1. When I run it manually, it completes with return code of 0. Any thoughts on whether this is an indicator as to why the system is subsequently rebooting? Logs attached. SyslogCatchAll-2022-07-17.txt