Jessssuhh

Solved it!! It was an authentication issue with my .ovpn creds. Turns out if the VPN portion can't initialise properly, QBittorrent won't unpack at all.

Yea you'd think so but I've found the logs to be pretty surprisingly generic. The only error/warning I got was the following: 2024-08-24 01:59:38,930 DEBG 'start-script' stdout output: [warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN Which is fine because it is accessed exclusively locally anyway. It seems to completely skip the actual QBittorrent part of the start up logs. Like it'll load the environment variables up top, hang for a minute or so, and then go into the ovpn portion of the start up log (which the above warning is from).

I realised on re-read I think my reply to you came across a little harsher than I intended. Good vibes here I promise haha! If you have any ideas for things you would trouble shoot if it were an unraid system, that would be helpful. In my experience they do line up pretty well; same concept different GUI, you know. Had to follow an Unraid youtube tutorial to get it installed in the first place haha!

It's on TrueNAS Scale. This is *the* support location for QBVPN according to Binhex' docs. it is still running on docker so the logs and permissions are much the same. If you know of a QBVPN support location that is specific to TrueNAS Scale, lemme know. I had it running successfully til I messed around with Tailscale. QBVPN was stuck in disconnected mode. I've uninstalled tailscale, have uninstalled QBVPN, but reinstalling QBVPN with duplicate settings is giving me the above.

I'm having a very strange issue where qbittorrentvpn is not unpacking qbittorrent at all. Like within the folder I have the openvpn folder for .ovpn config, and supervisor.log, but no qbittorrent folder and no webUI. I do have net_admin added and I am literally running the thing as a root user as a part of the troubleshooting.. utterly bewildered. Anyone have any ideas?? Edit: Solved Interestingly qbittorrent doesn't even begin to unpack if the vpn portion can't initialise properly. So if you're having the same issue I have had, troubleshoot your vpn credentials if your logs has this undefined in repetition: [UNDEF] Inactivity timeout (--ping-restart), restarting The issue I was having was that the config generator tool on torguard does not account for a modified port if you're using a Dedicated IP or Port Foward. It simply fills in generic port 1195 regardless of what your dedicated IP or Port Foward is set to. Quite interesting that QB didn't unpack at all, really had me going down a rabbit hole of user permissions and silent kubernetes errors..