zx81

Unfortunately the problem persists. The container from linuxserver works if that is any help. I will follow the help guidelines you linked. Regards. Edit: For anyone having the same issue here is a workaround. The problem is related to test -x failing when run by the user. Changing it to test -f makes it start all the plugins though that is just a workaround as test -x should work under normal circumstances.

I've recently installed rtorrentvpn on a machine running ubuntu. However, I'm getting the below errors and modules will not start. It can however download and upload fine. There are just no modules available. [11.03.2021 12:26:05] WebUI started. [11.03.2021 12:26:11] unpack: Plugin will not work. rTorrent user can't access external program (php). [11.03.2021 12:26:11] rutracker_check: Plugin will not work. rTorrent user can't access external program (php). [11.03.2021 12:26:11] _task: Plugin will not work. rTorrent user can't access external program (php). [11.03.2021 12:26:11] autotools: Plugin will not work. rTorrent user can't access external program (php). [11.03.2021 12:26:11] xmpp: Plugin will not work. rTorrent user can't access external program (php). [11.03.2021 12:26:11] scheduler: Plugin will not work. rTorrent user can't access external program (php). [11.03.2021 12:26:11] history: Plugin will not work. rTorrent user can't access external program (php). [11.03.2021 12:26:11] loginmgr: Some functionality will be unavailable. rTorrent user can't access external program (php). [11.03.2021 12:26:11] ratio: Some functionality will be unavailable. rTorrent user can't access external program (php). [11.03.2021 12:26:11] datadir: Plugin will not work. rTorrent user can't access external program (php). [11.03.2021 12:26:11] create: Plugin will not work. rTorrent user can't access external program (php). [11.03.2021 12:26:11] trafic: Plugin will not work. rTorrent user can't access external program (php). [11.03.2021 12:26:11] retrackers: Plugin will not work. rTorrent user can't access external program (php). [11.03.2021 12:26:11] rss: Plugin will not work. rTorrent user can't access external program (php). [11.03.2021 12:26:11] _task: Plugin will not work. rTorrent user can't access external program (pgrep). [11.03.2021 12:26:11] _cloudflare: Plugin will not work. rTorrent user can't access external program (python). [11.03.2021 12:26:11] screenshots: Plugin will not work. rTorrent user can't access external program (ffmpeg). [11.03.2021 12:26:11] spectrogram: Plugin will not work. rTorrent user can't access external program (sox). [11.03.2021 12:26:11] mediainfo: Plugin will not work. rTorrent user can't access external program (mediainfo). [11.03.2021 12:26:11] rss: Some functionality will be unavailable. rTorrent user can't access external program (curl).

It looks like that may the case. I'm using PIA so I don't get it, though. It's also happening with Mullvad. I've tried running wireguard in the host os and disabling the vpn for rtorrent and the same thing is happening. The supervisord.log is not giving much detail. 2021-02-28 14:35:51,147 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2021-02-28 14:37:51,264 DEBG 'watchdog-script' stdout output: [debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs... If I disconnect rtorrent and wait a while the connection gets responsive in the OS again. The connection is also dropping when torrenting from a windows machine using the same vpn. I guess it's pretty much out of your hands to do anything about this. If you have any suggestions I'd be happy to hear it, though. Regards.

I just tried wireguard as well. It works great for a while and then all of a suddon just drops the connection. curl ipconfig.io hangs for a minute or so and then says could not resolve host. How would I go about debugging this?

For some reason rtorrent stops downloading/uploading after a few gigabytes have been snatched. It will still show peers but all traffic stops. It doesn't happen in another client. I will test whether it's related to network stack sharing with thelounge. I've mapped the port for thelounge and added it to ADDITIONAL_PORTS. I'm not seeing any errors in the log and curl ipconfig.io confirms it's on the vpn ip. I will test some more and see if it's related to the network stack sharing with thelounge. Edit: disconnecting thelounge from the the rtorrentvpn network stack made it resume downloading immediately. Edit 2: Oh well it stopped again, so it doesn't seem to be related to network stack sharing.

Thanks! I managed to get things going. I removed a port I had set up in rtorrent.rc when testing with another vpn provider. Once that was gone the port forwarding started working as expected. Is it in any way problematic to have other containers sharing the network stack of rtorrentvpn to utilize the vpn connection?

Thanks for this great docker, binhex! I'm using this on two machines. a synology and in ubuntu. Using PIA It's working but not port forwarding. Is it supposed to work without the usual port forwarding you have to do from your router? If so I'm must be overseeing somthing as the port icon on the bottom of rutorrent stays red with the hover message "Port is closed". Can you advise?