lightsout

For sure I appreciate the effort. I'll definitely come back here if it happens again. And helpful for anyone who runs into the same issue.

Honestly I have no idea but that's helpful if it happens again. I did what was recommended. Can't remember exactly but partially started over. Didn't touch the array but got rid of all plugins and turned off all dockers. The problem went away and I slowly started adding things back to see if it acted up again. Haven't had any issues since.

edit - seems to be resolved.

I got it working with tailscale.

All good thanks man.

To sent you a pm if you don't mind to hide ip's.

I keep trying to figure out what that is but nothing works.

I am using the wireguard app on my phone and connecting it to my routers vpn. I can access all the others arrs with my home local ip (192.168.1.x) but qbitorrent never works.

Any idea what one would add to be able to access from mobile data?

Thanks I am not looking to open up unraid remotely. Basically I have a wireguard vpn in my router that I want to be able to connect to to interact with qbit throughh nzb360. I can do it with every arr app except qbit. I will do more testing.

No it's intentionally not. It's 192.168.0.0/24 I added that to the wg config and qbit wouldn't load. Any help on how to do that. Also how would I know what ip range to add for my phone on Mobile data.

I am running qbitorrentvpn with airvpn and wireguard. All works great. I also have a wireguard vpn on my asus router that I can turn on to access my home lan remotely. When I do this I can access all my other arr stack dockers remotely. (through nzb360 or web browser, such as sab, radarr, sonarr, etc.) But I cannot access qbit remotely, I believe this is related to the vpn in this docker. My home lan is simple, 192.168.1.0/24 everything on that same network, no vlans or docker networks. I have entered the home lan address (192.168.1.0/24) in the config for this docker. Is there something I need to do in my wireguard config file inside the docker container so that I can access qbit like all my other arrs from outside the network. Hopefully the way I have explained it makes sense.

Ok thanks. I have to imagine it is something to do with the custom VPN setup of this version. But idk. I'll go ask over there.

Anyone help a guy out here? I have a bunch of well seeded torrents that add in the "stalled" condition. The tracker is having no issue, I am connectable, port is forwarded in air on, VPN server is up and good. It's not every torrent even from one site. Really at a loss been dealing with it on and on.

I don't think its permissions because restarting the container sometimes gets it to work. It comes and goes. Not sure if this is the correct log 2024-08-19 09:47:07,535 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'up'... 2024-08-19 09:47:07,540 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2024-08-19 09:47:07,543 DEBG 'start-script' stderr output: [#] ip link add wg0 type wireguard 2024-08-19 09:47:07,544 DEBG 'start-script' stderr output: [#] wg setconf wg0 /dev/fd/63 2024-08-19 09:47:07,545 DEBG 'start-script' stderr output: [#] ip -4 address add .... dev wg0 2024-08-19 09:47:07,545 DEBG 'start-script' stderr output: [#] ip link set mtu 1320 up dev wg0 2024-08-19 09:47:07,547 DEBG 'start-script' stderr output: [#] resolvconf -a wg0 -m 0 -x 2024-08-19 09:47:07,555 DEBG 'start-script' stderr output: [#] wg set wg0 fwmark 51820 2024-08-19 09:47:07,555 DEBG 'start-script' stderr output: [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820 2024-08-19 09:47:07,556 DEBG 'start-script' stderr output: [#] ip -4 rule add not fwmark 51820 table 51820 2024-08-19 09:47:07,556 DEBG 'start-script' stderr output: [#] ip -4 rule add table main suppress_prefixlength 0 2024-08-19 09:47:07,558 DEBG 'start-script' stderr output: [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1 2024-08-19 09:47:07,559 DEBG 'start-script' stderr output: [#] iptables-restore -n 2024-08-19 09:47:07,560 DEBG 'start-script' stderr output: [#] '/root/wireguardup.sh' 2024-08-19 09:47:08,629 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2024-08-19 09:47:16,950 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address .... 2024-08-19 09:47:16,950 DEBG 'start-script' stdout output: [info] WireGuard interface 'up' 2024-08-19 09:47:16,951 DEBG 'start-script' stdout output: [info] VPN provider 'airvpn' not supported for automatic port forwarding, skipping incoming port assignment 2024-08-19 09:47:17,030 DEBG 'watchdog-script' stdout output: [info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP .... different, marking for reconfigure 2024-08-19 09:47:17,032 DEBG 'watchdog-script' stdout output: [info] qBittorrent not running 2024-08-19 09:47:17,032 DEBG 'watchdog-script' stdout output: [info] Removing session lock file (if it exists)... 2024-08-19 09:47:17,040 DEBG 'watchdog-script' stdout output: [info] Attempting to start qBittorrent... 2024-08-19 09:47:17,098 DEBG 'watchdog-script' stdout output: [info] qBittorrent process started [info] Waiting for qBittorrent process to start listening on port 8181... 2024-08-19 09:47:18,854 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8181