autoscan VS documentation

Autoscan Docker - This connects to Radarr and Sonarr and sends a message to Plex to update individual shows/movies

Autoscan - Because plex wont be on the file server anymore I had a problem with partial updates. It cant see when they are made. Autoscan connects to your downloader (Sonarr, Radarr) and tells plex to update when needed.

AutoScan - If you use radarr or sonarr this creates an artificial Partial Scan. It will only scan stuff updated by those programs instead of a full scan

I am having problems connecting a deluge client to the docker. When I enter the servers details on the client it finds it ok but it then asks for a username and password ( a). I have read the documentation and posts online that I should add this info to the auth file (b).

Don't know if I can help without more info. Perhaps one of these links can help? - https://www.privoxy.org/user-manual/index.html - https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Hi, I am trying to get setup with the *arrs, specifically I am trying to route Prowlarr's traffic through delugevpn. I followed the spaceinader one tutorial on routing traffic through another container, as well as the binhex FAQ for trouble shooting.

I'm a very novice user and just followed this guide since I use binhex containers whenever possible.

I'm not sure exactly what is wrong with your setup, but it has to do with your OpenVPN config. Try switching to the Wireguard protocol, it's a bit simpler as well as faster down speeds. Look at Binhex's FAQ specifically Q21. Binhex goes over setting up Wireguard on PIA.

So I was sorta right and sorta wrong. The problem was with SABNZB, specifically binhex's SABNZBVPN. After days of poking around the internet, I came across this article:

Binhex VPN Docs

the transcoder directory that you set in the docker settings "/config/transcode" will likely create the folder within the docker container which is not something you should do. either change it to an actual share or use your ram.