binhex

OK so thats the older template you have there, template updates are NOT pushed out to clients, if you want the latest template then you will need to remove the existing user template and reinstall from CA - i would recommend making a note of all your existing settings before doing this.

well strictly speaking its not an error, its a deprecation ;-), not sure of the fix for that off the top of my head tbh.

yep, PIA requires a poll to keep the port open and has done for some time (years).

ok that looks alright, just to double check try left click container, console then type 'touch /data/torrents/delme.txt' does it create a file without error?, look on your host can you see file '/mnt/user/data/torrents/delme.txt' ?

what has been there from the beginning?, "Path: /shared"? ,that has only been added in the past couple of weeks, screenshot please.

click on ' Show more settings ...' at the bottom in the edit screen

OK can you please also paste a screenshot of Options/Downloads in the qBittorrent web ui, i am particular interested in the completed and incomplete paths, my suspicion is that is not correctly defined and therefore it cannot start the torrent as it has nowhere to save to.

That's totally expected, we need to poll the port at least every 15 minutes to keep it open, so to ensure we are within the 15 minutes period we poll every 10 minutes:- https://github.com/binhex/arch-int-vpn/blob/1c9a9a33d8bd53526766b128e8cd110507a945ca/run/local/tools.sh#L872-L875 EDIT - if it bothers you then i can set this to only be visible when DEBUG is set to true but it does no harm and shows you what your currently assigned incoming port is.

most probably path related:- I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

you can do either, do keep in mind though most vpn providers limit the bandwidth for a single tunnel so you may get better speeds if you simply enabled the vpn for each qbittorrentvpn container instead.

Thanks!, i have been revamping all the templates and typo's and copy/paste mistakes are bound to creep in, now corrected.

Alright thanks for the explanation, i have now implemented a new env var, to use it do the following:- 1. left click the container and select 'edit' 2. go to the bottom and click on 'Add another Path, Port, Variable, Label or Device' 3. select 'config type' 'variable' 4. set the 'key' to be 'JAVA_CUSTOM_ARGS' and set the value to be the arguments you want setting 5. click 'add' click 'apply' and check logs i have tested this with your example given above and the server starts up, not sure if it's running any more efficiently but that is for you to find out, I'm just happy it's not broken by the inclusion of the additional args :-). Note:- New users will see this option as i have added it to the template, so they would simply edit the value and off they go. p.s. If you have success with a combination of arguments and wish to share them here for the community then please do!.

if you have switched user then you will need to reset permissions for the container, delete the file /config/perms.txt then restart/start the container.

Port forwarding is not used by SABnzbd BUT if you route other containers through the network of this container then it is entirely possible you may want an incoming port, thus the reason it was added.

Are you on about two containers talking to each other whilst both being in the privoxyvpn network?, if so then don't use the ip address, simply set it to 'localhost'.

You must have an older template, you will need to add it in:- click on edit for the container click on Add another Path, Port, Variable, Label or Device set config type to variable set key to STRICT_PORT_FORWARD and set value to 'no' Not sure where you have seen 'VPN REMOTE' but its not a valid env var and therefore will do nothing, if you want to change endpoint then Please see Q10 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

I've not had a request to add such advanced options to be honest, are your a Java guru? 🙂 not right now, nope, but if you can tell me why you need it then i will consider inclusion of a CUSTOM_JAVA_OPTIONS (or siimilar named) env var.

you both have the same issue, you have set STRICT_PORT_FORWARD to 'yes' but are attempting connection to a endpoint that does not support port forwarding, either change the endpoint you are connecting to to be a port forward enabled endpoint (see your log for a list of these) or set STRICT_PORT_FORWARD to 'no' if you do not require an incoming port.

When all your Windows machines start BSODing cos of Crowdstrike and UNRAID just sits there in a corner chugging along, happy days 🙂 Took me 5 hours to fix two Windows servers in two different cloud platforms this morning!.

As should be the case when using another containers network, in this case a vpn container, you should have no network defined and no ports for the container joining the vpn network.

Similar issue, try the suggested fixes:-

I'm a P2000 user myself, no probs with hw transcoding running binhex-plex (plex-pass is too bleeding edge for me).

It's possible, i know the BBC try to block known ip ranges for VPN's, so you maybe blocked.

nope, its not a bind mount, its a docker volume, so therefore no forward slash, its correct as it is, FYI its a new feature that has been added to the latest template, it will be used to store the incoming port and then shared between containers.

works for me using chrome browser.