azzkickr

Nope, it's not that. When I use openvpn I get pretty much the same result. No matter if I set the network to br0 with manual IP or bridge I get this: 2023-07-22 01:59:12.952067 [INFO] VPN_ENABLED defined as 'yes' 2023-07-22 01:59:12.993899 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-07-22 01:59:13.027176 [INFO] LEGACY_IPTABLES is set to '' 2023-07-22 01:59:13.059809 [INFO] Not making any changes to iptables version 2023-07-22 01:59:13.095296 [INFO] VPN_TYPE defined as 'openvpn' 2023-07-22 01:59:13.145227 [INFO] OpenVPN config file is found at /config/openvpn/vpn.ovpn 2023-07-22 01:59:13.787129 [INFO] VPN_ENABLED defined as 'yes' 2023-07-22 01:59:13.827101 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-07-22 01:59:13.861508 [INFO] LEGACY_IPTABLES is set to '' 2023-07-22 01:59:13.897722 [INFO] Not making any changes to iptables version 2023-07-22 01:59:13.932693 [INFO] VPN_TYPE defined as 'openvpn' 2023-07-22 01:59:13.979816 [INFO] OpenVPN config file is found at /config/openvpn/vpn.ovpn Nothing in the jackett log

Thanks mate, luckily I run both ovpn and wg on that host, so I'll use ovpn. Cheers!

ok, I ran docker update --restart=no jackettvpn and I was able to pull this [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.6.0.14/24 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] resolvconf -a wg0 -m 0 -x [#] wg set wg0 fwmark 51820 [#] ip -6 route add ::/0 dev wg0 table 51820 Error: IPv6 is disabled on nexthop device. [#] resolvconf -d wg0 -f [#] ip link delete dev wg0 dos2unix: converting file /config/wireguard/wg0.conf to Unix format... Warning: `/config/wireguard/wg0.conf' is world accessible [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.6.0.14/24 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] resolvconf -a wg0 -m 0 -x [#] wg set wg0 fwmark 51820 [#] ip -6 route add ::/0 dev wg0 table 51820 Error: IPv6 is disabled on nexthop device. [#] resolvconf -d wg0 -f [#] ip link delete dev wg0 2023-07-20 15:40:12.946123 [INFO] VPN_ENABLED defined as 'yes' 2023-07-20 15:40:12.987235 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-07-20 15:40:13.041482 [INFO] LEGACY_IPTABLES is set to '' 2023-07-20 15:40:13.079474 [INFO] Not making any changes to iptables version 2023-07-20 15:40:13.122723 [INFO] VPN_TYPE defined as 'wireguard' 2023-07-20 15:40:13.172875 [INFO] WireGuard config file is found at /config/wireguard/wg0.conf 2023-07-20 15:40:13.224638 [INFO] VPN remote line defined as 'redacted.url:51820' 2023-07-20 15:40:13.262943 [INFO] VPN_REMOTE defined as 'redacted.url' 2023-07-20 15:40:13.308949 [INFO] VPN_PORT defined as '51820' 2023-07-20 15:40:13.363519 [INFO] VPN_PROTOCOL set as 'udp', since WireGuard is always udp. 2023-07-20 15:40:13.397795 [INFO] VPN_DEVICE_TYPE set as 'wg0', since WireGuard will always be wg0. 2023-07-20 15:40:13.444095 [INFO] LAN_NETWORK defined as '192.168.0.0/24' 2023-07-20 15:40:13.481143 [INFO] NAME_SERVERS defined as '1.1.1.1,1.0.0.1' 2023-07-20 15:40:13.522578 [INFO] Adding 1.1.1.1 to resolv.conf 2023-07-20 15:40:13.583798 [INFO] Adding 1.0.0.1 to resolv.conf 2023-07-20 15:40:13.621964 [INFO] Starting WireGuard... 2023-07-20 15:40:27.456979 [INFO] VPN_ENABLED defined as 'yes' 2023-07-20 15:40:27.495986 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-07-20 15:40:27.529427 [INFO] LEGACY_IPTABLES is set to '' 2023-07-20 15:40:27.570345 [INFO] Not making any changes to iptables version 2023-07-20 15:40:27.604935 [INFO] VPN_TYPE defined as 'wireguard' 2023-07-20 15:40:27.657478 [INFO] WireGuard config file is found at /config/wireguard/wg0.conf 2023-07-20 15:40:27.705489 [INFO] VPN remote line defined as 'redacted.url:51820' 2023-07-20 15:40:27.748991 [INFO] VPN_REMOTE defined as 'redacted.url' 2023-07-20 15:40:27.786596 [INFO] VPN_PORT defined as '51820' 2023-07-20 15:40:27.826672 [INFO] VPN_PROTOCOL set as 'udp', since WireGuard is always udp. 2023-07-20 15:40:27.859728 [INFO] VPN_DEVICE_TYPE set as 'wg0', since WireGuard will always be wg0. 2023-07-20 15:40:27.899063 [INFO] LAN_NETWORK defined as '192.168.0.0/24' 2023-07-20 15:40:27.952981 [INFO] NAME_SERVERS defined as '1.1.1.1,1.0.0.1' 2023-07-20 15:40:27.996475 [INFO] Adding 1.1.1.1 to resolv.conf 2023-07-20 15:40:28.043966 [INFO] Adding 1.0.0.1 to resolv.conf 2023-07-20 15:40:28.077873 [INFO] Starting WireGuard... 2023-07-20 15:40:47.124586 [INFO] VPN_ENABLED defined as 'yes' 2023-07-20 15:40:47.162833 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-07-20 15:40:47.199465 [INFO] LEGACY_IPTABLES is set to '' 2023-07-20 15:40:47.231396 [INFO] Not making any changes to iptables version 2023-07-20 15:40:47.265764 [INFO] VPN_TYPE defined as 'wireguard' 2023-07-20 15:40:47.329410 [INFO] WireGuard config file is found at /config/wireguard/wg0.conf 2023-07-20 15:40:47.376947 [INFO] VPN remote line defined as 'redacted.url:51820' 2023-07-20 15:40:47.417351 [INFO] VPN_REMOTE defined as 'redacted.url' 2023-07-20 15:40:47.454613 [INFO] VPN_PORT defined as '51820' 2023-07-20 15:40:47.490609 [INFO] VPN_PROTOCOL set as 'udp', since WireGuard is always udp. 2023-07-20 15:40:47.524309 [INFO] VPN_DEVICE_TYPE set as 'wg0', since WireGuard will always be wg0. 2023-07-20 15:40:47.562895 [INFO] LAN_NETWORK defined as '192.168.0.0/24' 2023-07-20 15:40:47.600653 [INFO] NAME_SERVERS defined as '1.1.1.1,1.0.0.1' 2023-07-20 15:40:47.640980 [INFO] Adding 1.1.1.1 to resolv.conf 2023-07-20 15:40:47.681245 [INFO] Adding 1.0.0.1 to resolv.conf 2023-07-20 15:40:47.714688 [INFO] Starting WireGuard... My run command is this: docker run -d --name='jackettvpn' --net='br0' --ip='192.168.0.201' --privileged=true -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Badger" -e HOST_CONTAINERNAME="jackettvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_TYPE'='wireguard' -e 'VPN_USERNAME'='' -e 'VPN_PASSWORD'='' -e 'WEBUI_PASSWORD'='redacted' -e 'LAN_NETWORK'='192.168.0.0/24' -e 'TCP_PORT_9117'='9117' -e 'PUID'='99' -e 'PGID'='100' -e 'RESTART_CONTAINER'='0' -e 'NAME_SERVERS'='1.1.1.1,1.0.0.1' -e 'UMASK'='002' -e 'HEALTH_CHECK_HOST'='one.one.one.one' -e 'HEALTH_CHECK_INTERVAL'='300' -e 'HEALTH_CHECK_SILENT'='1' -e 'ADDITIONAL_PORTS'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:9117]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/DyonR/docker-templates/master/Icons/jackettvpn/jackettvpn-icon.png' -v '':'/blackhole':'rw' -v '/mnt/user/appdata/jackettvpn':'/config':'rw' --restart unless-stopped 'dyonr/jackettvpn' ec51c7bbd7d2b160ecd390a2f93f080fb0f41285572dfd556d82bcd1d5b43a0c The behaviour. root@Badger:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ec51c7bbd7d2 dyonr/jackettvpn "/bin/bash /etc/open…" 4 minutes ago Restarting (2) 18 seconds ago jackettvpn And I get a timeout trying to log on to 192.168.0.201:9117 This is the contents of /mnt/user/appdata/jackettvpn/Jackett/Logs/log.txt root@Badger:/mnt/user/appdata/jackettvpn/Jackett/Logs# cat log.txt 07-20 00:31:32 Info Starting Jackett v0.21.491 07-20 00:31:33 Info Environment version: 6.0.20 (/opt/Jackett/) 07-20 00:31:33 Info OS version: Unix 6.1.38.0 (64bit OS) (64bit process) 07-20 00:31:33 Info Jackett variant: CoreLinuxAmdx64 07-20 00:31:33 Info File /etc/issue: Debian GNU/Linux 11 \n \l 07-20 00:31:33 Info Running in Docker: Yes (image build: unknown) 07-20 00:31:33 Info ThreadPool MaxThreads: 32767 workerThreads, 1000 completionPortThreads 07-20 00:31:33 Info App config/log directory: /config/Jackett 07-20 00:31:33 Info Using proxy: Disabled 07-20 00:31:33 Info Using FlareSolverr: No 07-20 00:31:33 Info Using HTTP Client: HttpWebClient2 07-20 00:31:33 Info Loading Native indexers ... 07-20 00:31:33 Info Loaded 75 Native indexers. 07-20 00:31:33 Info Loading Cardigann indexers from: /config/cardigann/definitions/, /etc/xdg/cardigan/definitions/, /opt/Jackett/Definitions 07-20 00:31:35 Info Loaded 520 Cardigann indexers. 07-20 00:31:35 Info Loaded 595 indexers in total 07-20 00:31:35 Info Adding aggregate indexer ('all' indexer) ... 07-20 00:31:35 Info Adding filter indexer ('type:public' indexer) ... 07-20 00:31:35 Info Adding filter indexer ('type:private' indexer) ... 07-20 00:31:35 Info Adding filter indexer ('type:semi-public' indexer) ... 07-20 00:31:35 Warn No XML encryptor configured. Key {ea18d026-1121-4fd4-a659-cb2665990748} may be persisted to storage in unencrypted form. 07-20 00:31:35 Info Jackett startup finished in 4.308 s Hosting environment: Production Content root path: /opt/Jackett/Content Now listening on: http://[::]:9117 Application started. Press Ctrl+C to shut down.

My file browser is fine, maybe I was not clear enough. So let me rephrase. 1. After installation I have run the docker with wg off, it started normally, log file was created and filled with usual stuff. 2. I have copied the wg0.conf file to wireguard directory. Enabled wireguard in docker config. 3. The docker starts, shows up as running, but every attempt to click on logs or console here: [picture attached] the pop up windows immediately disappears. When I click on the "Logs" button at the right time, the window shows a ton of quickly scrolling text (like linux boot) and then immediately closes. 4. The log file jackettvpn created in step one is not updated, the file modification time does not change and nothing is being added. Therefore it is difficult for me to diagnose. Is there any way to make the docker not restart (I did follow the Dyon's instruction from a few posts up) or to force it to log everything somewhere, so I can actually find out what's wrong with it? Thanks

I'm also unable to get it to work. After enabling wireguard, the log file is not updated anything, the log and console windows disappear immediately. I have tried the wg0.conf file on another machine, works flawlessly. I can't even tell you anything more as there is nothing in the logs...

Yeah, while it does spin down sas drives, the auto fan control almost immediately spins them up again, since update to 6.10 Which is kinda dumb. But auto fan invokes smartctl to check the temperature and that wakes the disks down. So at the moment you can use either one or the other.

would you be able to share the link?

It worked for me. I mean when I emptied the exclude drives box it worked fine for fan control The problem is that this plugin was waking up my sas drives (sata were fine) every five minutes when it was pulling the temp reading via smartctl. I had to remove the plugin. Now I have fans at 100% all the time, but at least my drives are sleeping. and 12 drives x 20 Watts 24h x 365 days at current electricity prices... no thank you.

Ha, in my case it was the dynamix auto fan control. The moment I removed it the disks started behaving. I think tt's because the plugin keeps reading the disk temperature every 5 minutes. By the way on 6.9.something it worked absolutely fine. The minute I upgraded to the .10.rc it got broken. I have a feeling that the plugin should check what drives are spun up and only take the temperature of those, instead of waking up all of them. Anyway so now I have my disks nicely sleeping, but fans at 100%. Oh well

Fixed. First, I ran btrfs rescue super-recover -v /dev/sdg1 that showed that all supers are valid, no need to recover. So then I ran btrfs rescue zero-log /dev/sdg1 cleared the log, and voila!

Hi all Today I was replacing a hot swappable sas drive, when I accidentally pulled a cable out from a drive that is in a physical raid0 configuration and part of a large cache pool. So, two drives in raid0 as "Raidhdd" cache pool. After reboot the drive shows as Unmountable: Not mounted. After the initial heart attack, I ran the btrfsck which showed no problems. I mounted the drive in /mnt/cache-large. All the data is fine. However, the Main tab of the Unraid GUI still shows it as unmountable: Not mounted, weirdly, and the docker containers don't see it. Any ideas? [EDIT] Nope, please forgive me, I am an idiot. cache-large is the other cache drive. I am unable to mount the "raidhdd" pool, of course. I don't know what I was thinking...