Cat_Seeder

Members
  • Content Count

    81
  • Joined

  • Last visited

Community Reputation

16 Good

About Cat_Seeder

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. How many torrents are you seeding? And how fast are your drives? Rutorrent's PHP backend isn't exactly the fastest one, and honestly, after 1500 or so torrents it's easier to manage everything from the command line. I have SSD caches and well tuned Linux box, even so, deleting the data of a big torrent file using Rutorrent's File Manager often makes the UI unresponsive. If you are dealing with a few hundred torrents or less then rutorrent is manageable, otherwise I deeply recommend getting familiar with pyrocore. Using the CLI feels weird at first, but once you get used with it there's r
  2. You can make it run automatically on startup. See A2 here - https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md . For sinology: https://help.synology.com/developer-guide/integrate_dsm/run_with_system_boot.html
  3. And everything is working again. Thanks Binex, you are awesome. I know that eventually we'll need to jump off rtorrent-ps (unless a miracle happens and it pick up the pace again). Hopefully there's a way to do it without having to force users to expose RPC2 mounts and someone will find a way to make file manager before that. For now, I'm glad to be on good ol' versions :).
  4. For the old version of the container with rtorrent-ps + old version of file-manager (before it was split on its own repo) see: https://github.com/binhex/arch-rtorrentvpn/issues/96 For the latest version of the container + newest version of file manager I can't get it to work at all. Had to revert back. Please do let me know if you figure out.
  5. rtxmlrpc is part of pyrocore. @binhex, without pyrocore we'll not have rtxmlrpc, and reverting to xmlrpc means that port-forwarding will need /RPC2 mounts and we'll be back discussing security shenanigans. I understand that you want to get alway from rtorrent-ps, but can you maybe include an individual release of pyrocore in the image?
  6. I've installed an old version manually. Can't get the newer version working for the life of mine.
  7. Well, with the last update my ancient version of rutorrent's file manager plugin is officialy dead. Did anyone get the newer version of https://github.com/nelu/rutorrent-filemanager, https://github.com/nelu/rutorrent-filemanager-media and https://github.com/nelu/rutorrent-filemanager-share to work? I can't live without file manager.
  8. No comments about security, but it's certainly fast, and so far it has been stable. Thanks @binhex, sending another beer your way. By the way, did the autodl-rssi + recent version of php issue got sorted? Kind regards,
  9. The unofficial script below already works with OpenVPN. https://github.com/thrnz/docker-wireguard-pia/blob/master/extra/pf.sh
  10. PS. Looks like someone already managed to create a bash script to make port forwarding work with next-gen servers. It's experimental but according to the author comments it should also work with OpenVPN. https://github.com/thrnz/docker-wireguard-pia/blob/master/extra/pf.sh .
  11. I got port forwarding working with the Spainish server (one of the old ones), before that I could make it to work with servers in Switzerland but it no longer works for me. Unfortunately, until PIA stabilises old servers or provide APIs to port forward on next-gen servers there's no much that can be done other than server hopping and praying.
  12. Have a look at nginx logs for suspicious activity, particularly requests to /RPC2 from unusual IP addresses. Make sure to secure both ruTorrent and RPC2 with strong passwords (or disable RPC2 entirely I'd you don't need it). Don't use the defaulr auto-generated passwords as they are logged in plain text. If you can, do not expose anything over the internet (you can use a VPN to access your box). If you need to expose rutorrent do the internet then make sure to use a hardened reverse proxy (nginx-proxy / traefick, etc), Https only, with a real certificate (e.g., Let's Encrypt) and a strict fail
  13. You are looking for network.port_range.set, for further information check rtorrent guide at https://rtorrent-docs.readthedocs.io/en/latest/cookbook.html The container README.md also has a sample configuration for AirVPN demonstrating how to change incoming ports: https://github.com/binhex/arch-rtorrentvpn/blob/master/README.md
  14. Privoxy is starting fine at port 8118. Make sure to expose that port (e.g., -p 8118:8118 if you are using docker CLI) and then configure your end machine to use the host's IP address and port 8118. No need for FoxyProxy, Chrome / OS settings work fine. You can check that it's working on http://config.privoxy.org/
  15. Looks like it. I'm building a custom image from source and can't reproduce the issue either.