VPN provider - Possible connectivity issues will of course cause a drop in the vpn tunnel and thus all connections to the usenet provider, a quick re connection (which will happen as ive coded it to re-establish tunnel if it drops) could then result in existing connections still being present and thus the issue regards too many connections until they drop.ĭisclaimer - all of the above are maybe's, i currently have no proof of any of the above causing the issue. Usenet provider - As mentioned previously the provider maybe incorrectly identifying multiple connections from the same IP (due to VPN) as being from the same client, thus the too many connections. ISP throttling of VPN traffic - i have seen and heard of this, i know ISP Virgin in the UK does this. So i guess it could be any/all of the following at play:. I have successfully downloaded a 17GB rar'd nzb with no issues, no errors were shown in the /config/logs/ file and it unpacked fine, downloads speeds also seemed very acceptable, being close to maxing my line out. SABnzbdVPN:- Latest Docker release, currently this is SABnzbd v2.3.5 VPN endpoint:- CA Vancouver ( port 1198 protocol UDP) In that case im currently unable to reproduce the problem, details as follows:. I use Sonarr and Radarr to send but any download should present these timeouts once SABNZBDVPN gets the job. Set VPN_ENABLED = yes or no and compare the results.
Usenetserver unraid setup install#
Install Docker Container > Enter VPN credentials > Configure SABNZBDVPN Download Directories > Send a file > Monitor Download
0 kommentar(er)
