bumperjeep

Is there a suggested health check setting? I'm new to docker health checks in general? -e HEALTHCHECK_COMMAND=<command> \ -e HEALTHCHECK_ACTION=<action> \ -e HEALTHCHECK_HOSTNAME=<hostname> \i see that, but there's also a docker compose health check setting, what are other people using for things that need to route through the vpn or privoxy?

I pulled the latest and it fixed my error too. Thanks Binhex! Is this still the right name servers? - NAME_SERVERS=84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1

Hi - I have a routing question. I'm thinking of doing a site to site vpn on my router. I wanted to make sure that there wasn't anything I could do at my router level that would override / mess up the iptables on the container. I'm referring to the iptable rules you describe here https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md. I'm sure that PIA uses a 10. network internally, and my site to site might also be joining to a remote 10. network. The container does not need to talk to the remote network ever, so I'm just double checking I won't break your core functionality.

Is there a preferred VPN provider specifically for this container? It looks PIA is the most supported, does AirVPN or Mullvad work better here?

Even if you move it to blue and force a recheck, it still tries to move back to red because the download isn't complete.

No, it's pointing to /media/red because that's where I want it saving 95% of the time. I only wanted to change the path for 1 download or ad hoc downloads where i explicitly override it

Hi I've been using the rtorrent container for a while, but switched here since it got deprecated. my default save path is /media/red, but it's pretty low on space, so I wanted to save some torrents to /media/blue. I set the save location when adding the torrent, but it keeps on downloading to red and only moving to blue when it's finished. Is there a way to avoid this behavior? For this specific torrent, I only want to write to blue. I know you could definitely do that with rtorrent, but I can't seem to figure that out with qbit. Thanks!

So I added the following to my rtorrent.rc, execute = {/bin/bash,-c,mkdir -p /config/rtorrent/logs} log.open_file = "rtorrent", /config/rtorrent/logs/rtorrent.log log.open_file = "tracker", /config/rtorrent/logs/tracker.log log.open_file = "storage", /config/rtorrent/logs/storage.log # rTorrent logging verbosity for rtorrent, comment out if logs are too chatty log.add_output = "info", "rtorrent" log.add_output = "critical", "rtorrent" log.add_output = "error", "rtorrent" log.add_output = "warn", "rtorrent" log.add_output = "notice", "rtorrent" log.add_output = "debug", "rtorrent" # rTorrent logging for dht and tracker traffic log.add_output = "dht_debug", "tracker" log.add_output = "tracker_debug", "tracker" # rTorrent logging for storage log.add_output = "storage_debug", "storage" that wrote logs and told me that this line execute = {/bin/bash,-c,mkdir -p /data/incomplete} is causing the error. I never had a mount for /data, that line has always been there. I have no idea why all of a sudden it's been a problem. Might be cool to add those logs to supervisord.log. Anyway, I hope this helps somebody else!

Actually I can't even get rtorrent runing. it's been very stable for a long time, nothing has changed

I'm not using Unraid, I'm using Ubuntu 20.04. I definitely do not want to add / index everything again. In the past, I've moved the docker folder and got everything running fresh and then just moved the folder back and everything worked.

I'm having the same problem, as of 6-14 or 6-15 it went down and I cannot get it back up.

Hi - I just unpinned my Rtorrent version to pull latest, from image: binhex/arch-rtorrentvpn:rtorrent-ps-1.1.r54.ga787dd9-1-28 I'm having a bit of trouble understanding the changes needed in questions 25 and 26. I'm using Sonarr, Radarr and Jackett. Sonarr and Radarr are configured to use Jackett as a provider, but I also had an HTTPS proxy configured for Sonarr and Radarr. I'm using Ubuntu with docker compose. I'm only accessing the web ui for these apps via a VPN (wireguard hosted on this server). My main issue is that torrents from Jackett are not downloading once added to rtorrent Do I need to change or add values? VPN_OUTPUT_PORTS VPN_INPUT_PORTS - LAN_NETWORK=192.168.55.0/24,10.6.0.0/24 (LAN, Wireguard home vpn subnets) I'll try reading the instructions again. I'm also using 9443 for the web port instead of 9080 from the issues a few weeks ago. Since I'm using docker compose, do I need to add networks to my config? I don't have that set up. I can see all of the UIs for the apps, but now no torrents will download. EDIT: I did a little more research and when I download the .torrent directly from Jackett and add it myself to rtorrent, the downloads start in rtorrent, when sonarr adds the torrent to jackett, they don't.

Switching from 9080 to 9443 definitely helped me as well, using the latest stable version. Can somebody explain in more detail what happened with nginx?

I've been using this container for years, and I've been running into a lot of issues lately. I've pinned the container to the last working version: binhex/arch-rtorrentvpn:rtorrent-ps-1.1.r54.ga787dd9-1-28 For some reason, it's failing to start rtorrent. I did a dist upgrade from Ubuntu 18.04 and 20.04 a few weeks ago and I'm not sure if that's part of it. What else can I look through if Rtorrent is failing to start? Is there another log? I'm also getting this error: Unable to successfully download PIA json to generate token from URL 'https://10.0.0.1/authv3/generateToken' I'm also getting this a minutes after the last healthy log message: 2021-02-12 03:48:05,459 WARN received SIGTERM indicating exit request

Thanks! Could this have any impact on Privoxy? My sonarr container is having trouble connecting to the internet through the rtorrent privoxy option.