binhex

not really, im afraid you are going to just have to work through this yourself as its a nginx reverse proxy issue specific to your setup, there is nothing i can change to fix this.

interesting, for me this just works, no delay and no missing favicon etc

its possible that the later version of rutorrent just doesnt play nicely with reverse proxy baseuri, i can confirm however it does work correctly for subdomain (im using the ngins reverse proxy manager docker container), not really much i can do to fix up the baseuri issue.

im pretty sure the speed improvement was due to the latest version of rutorrent, i noticed an instant improvement on the bump up to 3.9, even noticed deletion of torrent+data seems to be quicker, which is probably my top dislike of rtorrent/rutorrent (still my preferred though). as always thank you for the donation!.

but surely autoupdate updates automatically via autoupdate.....right? 😁 j/k

yes i did forget about it, just pushed the change, new image building with the max mem bumped up to 768M

see if Q16. from the following link is relevant:- https://forums.unraid.net/topic/44108-support-binhex-general/?tab=comments#comment-433612

rtorrent vpn faq heading from the following link:- https://forums.unraid.net/topic/44108-support-binhex-general/?tab=comments#comment-433613

yep, as long as that particular ip address DOES support port forwarding then it should work.

i think you will find this is a warning, and it will carry on and attempt to get a incoming port regardless.

see link below Q9. for examples on how to configure this- https://forums.unraid.net/topic/44108-support-binhex-general/?do=FindComment&comment=433612

you have:- STRICT_PORT_FORWARD defined as 'yes' but:- us-west.privateinternetaccess.com is not a endpoint that supports port forwarding, see your supervisord.log file for a list of endpoints that support port forwarding.

absolutely!, 192.168.1.0/24 is just the default.

rclone isn't found because rclone isn't installed inside the container you would have to either run rclone on the host or fork my code and include rclone in the build of the docker image Sent from my EML-L29 using Tapatalk

The issue is regards socks proxy not HTTP proxy which is what privoxy is. so you are fine to use it however they may remove the proxy feature completely from jackett unless they get support from some other developers. Sent from my EML-L29 using Tapatalk