Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

14 Good

About Cat_Seeder

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. 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,
  2. The unofficial script below already works with OpenVPN. https://github.com/thrnz/docker-wireguard-pia/blob/master/extra/pf.sh
  3. 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 .
  4. 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.
  5. 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 fail2Ban configuration. Having said all that, keep in mind that there are vectors of attack other than your torrent client (e.g., if someone got access to your private tracker username / password somehow, or if one of the private tracker admins messed up / if your own machine was compromised, etc). I know that this is generic advice, but I hope it helps.
  6. 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
  7. 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/
  8. Looks like it. I'm building a custom image from source and can't reproduce the issue either.
  9. Well, the easier alternative is to follow binhex advice and wait for someone more familiar with autodl-rutorrent codebase to have a look at the issue that you have reported. If you want to troubleshoot the issue by yourself I wouldn't expect much hand-holding, sorry. However, if you are ok with the frustration of being stuck, I'm not discouraging you from going down that route, trying to fix my own problems is how I got to learn a thing or two to share with the community. I'm not an arch guy but by what I understood you can clone the package source and run makepkg or install some of the many utilities to work with AUR packages. --- Other than trying to downgrade PHP you may also try to debug and investigate why you are getting errors from autodl-rutorrent plugin. Maybe you have a misconfiguration issue, or maybe something that used to be normal isn't anymore. PHP 7.4 is known to be much more strict than PHP 5.6. Having a quick look at your ticket and the source at https://github.com/autodl-community/autodl-rutorrent/blob/master/getConf.php#L46-L61 it looks like something that is assumed by the code to be a an array is actually a boolean ($userInfo maybe?). Once you understand where the code is chocking it's going to be easier to understand what is happening (wrong UID maybe? You can always log the uid to the console and verify if it exists in the container). Or maybe you can take the shotgun approach and modify the code to fix the issue. E.g., for the hypothetical and unverified scenario above you could add a check to confirm that $userInfo is an array: if (is_array($userInfo) && file_exists($userInfo['dir'].'... Assuming that you need a code change to fix your issue you may as well open a PR and contribute it upstream - even if you are not a PHP Developer, I'm certainly not :). Just my 2 cents.
  10. Hey @td00, you can actually do it by yourself, although I've been running the container with PHP7 with no issues. In order to create your custom image running php5.6 first clone rtorrentvpn repo: https://github.com/binhex/arch-rtorrentvpn Then edit the following line to include the dependencies that you want: https://github.com/binhex/arch-rtorrentvpn/blob/master/build/root/install.sh#L53, for instance, you can replace php-fpm and php-geoip with php56-fpm and php56-geoip Finally you can run docker build command to build your custom image and run it locally with docker run. For more info about how to do that have a look at https://stackify.com/docker-build-a-beginners-guide-to-building-docker-images/
  11. Hi Nora, unfortunately there ain't much that I can do to help since both problems are in the IRC side of things. As I've previously recommend, I would get acquainted with IRC (see https://opensource.com/article/16/6/irc-quickstart-guide for a quick start) as well as with the specific rules for each one of your trackers (you can generally find a Rules and FAQ for each private tracker) before even attempting to use autodl-irssi. Once you feel confident - IRC looks complicated but it really isn't - join each one of the tracker's respective IRC channels to figure out what went wrong. In the server where your bot has been k-lined you will have to join the tracker's IRC channel, respectfully ask to talk to an ops and try to understand for how long your bot has been banned. Depending on the tracker and channel it can take several hours until an ops can answer you - just wait and be polite. If it was banned permanently I would - again very respectfully - try to explain that you are new to autodl-irssi and inadvertently logged in as root, ask him if it's possible to lift the ban against your bot. Personal anecdote: I once had a VPN misconfiguration spam a tracker by quickly logging in and logging out of it (my torrent client logged in using dozens of different IPs in a few minutes). I don't have to say that I was banned. This what a very prestigious tracker associated with other very prestigious trackers that also banned my account. I was told by a lot of people that admins from this particular tracker were ruthless and that there wasn't much that I could do. By patiently waiting several days and politely explaining my mistake on IRC I managed to get unbanned. As for your second problem, once logged in to the right IRC server with a real client you can get a better understanding of why your bots are being ghosted. I can only guess, but two possibilities are that you are either: 1) Using the same user id as another user or 2) Mostly likely, you are logging in with two different IRC clients using the same set of credentials at the same time (e.g., you may be using the same user id and IRC key on two different channels from the same server, or maybe you are starting two different containers, both running autodl-irssi with the same credentials against the same server). I hope that this helps.
  12. No problem. If I were you I would join your private tracker IRC channel and talk with mods to understand if you haven't been k-lined permanently and, maybe, if you can get unbanned (careful on how you approach mods, some private trackers are terrible). This is definitely on the IRC side of things instead of the container. If you are not familiar with NickServ I would Google for it (long story short, you want to register a unique username for your bot, make sure that only one process is ever using this nick and that autodl-irssi correctly identifies it).
  13. To my untrained eyes The PGID and PUID looks ok. I'll leave the in-depth analysis of the logs to binhex. I was thinking about your problem though, are you always testing and getting K-Lined on the same server? If so, could you try a different one? Nowadays most servers are pretty reasonable and use bots that only temporarily ban users logging as root (generally for a few minutes), however, there are exceptions to the rule...
  14. Try deleting the entire contents of /mnt/user/appdata/binhex-irssi and /mnt/user/Downloads/autodl. It's a long shot but some leftovers from previous runs may be getting in the way. PGID and PUID should be the same as the host user. That's ok. Docker doesn't map usernames (I.e., they don't match), all it does is to assign the host UID to the container user. For more info see: https://medium.com/@mccode/understanding-how-uid-and-gid-work-in-docker-containers-c37a01d01cf Start by simplifying your setup so that you can get acquainted with the container. Stop both containers, remove them and prune docker system (docker system prune -af . Be warned that this command will discard all images and their related containers) This time start from scratch with a single container and IRSSI enabled. Use fresh folders (as in, the folders in the host should be empty when you first start the container), make sure to set the right PGID and PUID on the first run and make sure that all files are created with the right permission this time. With this new single container open rutorrent and configure a single filter / tracker / IRC server (if you are not acquainted with using rutorrent autodl-irrsi plugin see https://www.rapidseedbox.com/kb/use-rutorrents-autodl-irssi-plugin for more info - do not copy your IRSSI configuration files from other containers), check if autodl-irssi has connected as expected and new files are being downloaded correctly. Once you get to this point, if autodl-irssi is working correctly it should be easy to add your other trackers your on top of that. No problem. Hopefully the above steps will help.
  15. -v /mnt/user/Downloads/autodl:/config \ -v /mnt/user/appdata/binhex-rtorrentirssi:/config If that's not a copy and paste error the above lines are wrong. What the two lines above are doing is to mount two different folders from the host (/mnt/user/Downloads/autodl and /mnt/user/appdata/binhex-rtorrentirssi) to the same place in the container (/config). This does not make much sense from a file system perspective and I really don't know what docker would try to do with it, this may be the cause of your issue. What you actually need is something like: -v /mnt/myuser/myrtorrentvpnfolder/data:/data \ -v /mnt/myuser/myrtorrentvpnfolder/config:/config Where /mnt/myuser/myrtorrentvpnfolder is a valid folder that you've created in your host. The folder above and everything bellow it should be owned by the user and group that you are passing to PUID and PGID. I would suggest creating fresh folders in the host and starting over (stop and delete your container and start everything from scratch pointing to the new folders).