MothyTim

Oh, strange because I’m seeing this in Lidarr settings?

Is this docker going to be updated anymore? As I see there has been a new version of Lidarr available for a while now? Cheers, Tim

Of course! Just it was a few pages back on the thread and didn't want it forgotten!

Anyone???

Just bumping this hoping someones got an answer? Cheers, Tim

Hi, autofan has stopped working after upgrading to 6.9.1 it was working fine in 6.9.0 and all the betas and RC's. Its annoying as finally my drives spin down and now something else is broken. Not sure what info is needed but I have this in syslinux: acpi_enforce_resources=lax and this in my GO file: modprobe it87 force_id=0x8628 Hopefully someone knows what has changed to stop this working? I have also asked in plugin's page! Cheers, Tim tower-diagnostics-20210312-1429.zip

Hi, autofan has stopped working after upgrading to 6.9.1 it was working fine in 6.9.0 and all the betas and RC's. Its annoying as finally my drives spin down and now something else is broken. Not sure what info is needed but I have this in syslinux: acpi_enforce_resources=lax and this in my GO file: modprobe it87 force_id=0x8628 Hopefully someone knows what has changed to stop this working? Cheers, Tim

Ok, which is exactly how mine was configured! How have you tested it? Have you used console in sonarr/radarr etc to check that they are actually going out through your VPN? If not then you don't actually know! Cheers, Tim

Why is it not accurate?? Privoxy is not working and infact consantly restarts, quite a few others are reporting the same! As Jackett is working fine conected directly through DelugeVPN container not using the proxy, you don't need to use proxy for Radarr/Sonarr etc so have turned it off in both!(Hopefully that is correct?) I have tried turning it on to test privoxy but iplocation still reports as home so privoxy is not working there either! Ignored addresses is just to allow Radarr/Sonarr etc to connect to local network if you're using proxy so not relavant here, but is how it's set in Bazarr! Hoping for a fix soon. Cheers, Tim Forgot my docker run command in last post! root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='proxynet' --privileged=true -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='********' -e 'VPN_PASS'='*********' -e 'VPN_PROV'='pia' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='10.19.64.0/24' -e 'NAME_SERVERS'='209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -e 'VPN_CLIENT'='wireguard' -e 'ADDITIONAL_PORTS'='9117' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -p '9117:9117/tcp' -v '/mnt/user/Downloads/':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' 'binhex/arch-delugevpn' 1098a4d6c1e7d3c8e349c7f554c30f3fa1bf4df4f26c3f392be20c23a47c9c0f A more complete log attached: delugevpnlog.rtf

Hi, so a few hours of reading and trying things out leads me to think that privoxy is broken! I've changed Jackett to use the delugeVPN container network so I can switch off proxy in jackett and sonarr/radarr etc meaning they now connect to jackett for indexing ok! And Plex ok! The only container I'm trying to proxy is bazarr, but when I look up location through its console it reports as my home not Toronto like it should? Both DelugeVPN and Jackett report as Toronto! Also in ignored addresses wildcards don't work for me, I have to put the ip address of my server for Bazarr to be able to connect with Sonarr and Radarr! My log shows privoxy restarting all the time. I see others are reporting the same, any idea on the issue? Or is it a bug? Cheers. Tim 2021-03-02 20:48:44,275 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 2021-03-02 20:49:14,451 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2021-03-02 20:49:14,452 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-03-02 20:49:15,470 DEBG 'watchdog-script' stdout output: [info] Privoxy process started 2021-03-02 20:49:15,471 DEBG 'watchdog-script' stdout output: [info] Waiting for Privoxy process to start listening on port 8118... 2021-03-02 20:49:15,479 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 2021-03-02 20:49:45,610 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2021-03-02 20:49:45,611 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-03-02 20:49:46,615 DEBG 'watchdog-script' stdout output: [info] Privoxy process started 2021-03-02 20:49:46,616 DEBG 'watchdog-script' stdout output: [info] Waiting for Privoxy process to start listening on port 8118... 2021-03-02 20:49:46,618 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 2021-03-02 20:50:16,783 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2021-03-02 20:50:16,784 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-03-02 20:50:17,789 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2021-03-02 20:50:17,794 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118

Thanks for that, I'd noticed that occasionally it would scroll but haddn't noticed it was when my finger was on the empty space!

Yep I guess that helps! 🤣

map /var/run/dbus/ to /var/run/dbus/

I can't see the rest of your config, have you mapped /var/run/dbus/ ??

Have had very few problems with the beta's since 22, but drives not spinning down issue still not fixed for me! None of my drives have spun down since upgrading from beta 35 to rc1! Was hoping rc2 would fix this! Also Dashboard and Docker page still don't scroll on iPad in Chrome or Safari. But then docker page never has, keep hoping it'll be fixed though! Diagnostics attached. tower-diagnostics-20201221-1416.zip

They say they'll be releasing config files for Wireguard soon! So perhaps thats the way to go?

I would try the Tomato firmware first, freshtomato is currently still updated and gives you all the features that UniFi or pfsense do and won’t cost you any more! If you want better Wi-fi then ubiquity is hard to beat!

Hi, with TP-Link easy smart switches you can’t remove any ports from main vlan, the first table in the screen shot is a bit of a red-herring as nether vlan is selected so the table isn’t showning anything, with vlan 50 only the trunk port and the port connected to server should be untagged the ports to the cameras should be tagged and pvid set to 50. The router with FreshTomato firmware supports vlans and multiple DHCP servers, it’s what I’ve been using for 5 years or so and works well.

Hi, The Asus RT-AC68U doesn't support VLAN's with the stock firmware, you'll need FreshTomato for that! Google will tell you how! Do your cameras support VLAN if not you will need to set the ports they're connected to to tagged and set the PVID.

Ah OK good to know!

It's only the docker page, everything else is fine! It's the same in Safari and Chrome.

Has anyone noticed a problem with USB passthrough to Docker? It was working ok in 6.8 but not since updating to 6.9 betas. Is there something different that I've missed? Cheers, Tim

Docker page doesn't work at all on iPad and hasn't for quite a while! Keep hoping it'll be fixed with each new update? It just locks-up and won't scroll.

Ok thanks working again! I still have the issue of it taking my unassigined drives temp but I can't exclude it? And it doesn't start on reboot? Attached diagnostics in case they help! Cheers, Tim tower-diagnostics-20200621-1344.zip

Hi, load the modules through go file. After last nights update AutoFan is completly broken, if I try to enable one of the controllers they all enable and there is no apply button! And it stays stopped!