RuTorrentVPN Plus Plus

RuTorrentVPN Plus Plus is a Docker container that bundles the ruTorrent BitTorrent client with OpenVPN, Privoxy, and DNS-over-TLS to give self-hosters a…

  • Downloaders
  • Network Services
  • Tools & Utilities
RuTorrentVPN Plus Plus is a Docker container that bundles the ruTorrent BitTorrent client with OpenVPN, Privoxy, and DNS-over-TLS to give self-hosters a ready-made privacy-focused torrenting setup.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

32/100 Low

Maintained
0GitHub repository is archived
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
100128 MB minimum RAM
Security check
85no serious findings, CI

Availability: platform listings confirmed today, links checked 31 days ago

GitHub stars
0
Open issues
0
Last commit
2020-09-17
License
GPL-3.0
Activity
stale

Checked 12 days ago - source: GitHub (testdasi/rutorrentvpn-plus-plus)

Resources & Compatibility

Minimum requirements: 128 MB RAM. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Initial OpenVPN configuration On first run the container stops because no OpenVPN profile is present. Copy at least one .ovpn file to the host path mapped to /config/ovpn_files. If your provider supplies separate certificate files (.crt and .pem), place them in the host path mapped to /config/ovpn; providers such as Private Internet Access embed certs in the .ovpn file so that step can be skipped. Restart the container after t source
  • Upstream deprecation The upstream binhex/arch-rtorrentvpn image is no longer maintained; use the testdasi/rutorrentvpn-plus-plus repository and image. source
  • Maintenance status The GitHub repository is archived, so expect no new releases and limited upstream maintenance. source
  • OVpn file placement Copy at least one .ovpn file to the host folder mapped to /config/ovpn_files; place separate .crt/.pem certificate files in /config/ovpn only if required, then start the container. source
  • Repository maintenance status The upstream GitHub repository is archived; assume no active upstream maintenance for this container. source
  • Initial OpenVPN configuration First run stops until at least one .ovpn file is copied to the host path mapped to /config/ovpn_files; separate certificate files go in /config/ovpn if needed, then restart. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why does the container stop on first start?

It stops when no OpenVPN profile is present. Copy at least one .ovpn file to the host path mapped to /config/ovpn_files, and restart after adding separate certificate files to /config/ovpn if needed.

Which ports should be published?

Publish 9080 for the HTTP ruTorrent UI, 9443 for the HTTPS UI, and 8118 for Privoxy. The container also needs the NET_ADMIN capability for the VPN tunnel.

Why does the web UI password not use the old default?

If WEBUI_USER and WEBUI_PASS are not defined, the password is randomised instead of using rutorrent. Define the user and password environment variables to set known credentials.

What should I do if ruTorrent has no activity or peers?

Troubleshooting often involves enabling DHT, adding functional trackers, or changing peer discovery settings. These changes commonly resolve tracker-related activity issues.

Answers sourced from github.com, help.rapidseedbox.com, hub.docker.com

Community

Collected 49 days ago - public community threads