Torrent Client besides deluge and transmissionbt

    • OMV 3.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Torrent Client besides deluge and transmissionbt

      I'm looking for a alternative to torrent clients that i have used in the past.

      Transmissionbt - just not feature rich enough. basic items i feel were missing
      Deluge - Does a great job but extractor not working the Dev's seem not to care. using execute was a option but i'm not knowledgable to figure it out.

      This leaves me with Docker - I used qbitorrent but i always ran into permission issues that i just couldn't solve.

      Obviously a gui would help me as that is what i'm used to... any thoughts?
    • Deluge have extractor plugin. I was using it.
      Each else client can be installed manually, but IMHO deluge is best available - have all necessary options, plugins and it's lightweight.
      Debian 8.6 Jessie + OMV 3.0.latest Kernel: Linux 4.8.0-0.bpo.2-amd64
      Processor: Intel Core 2 Duo E8400@3GHz
      Memory: 4GB RAM
      OS-HDD: Samsung SSD 120 GB +LVM

      Full media and download center configured.

      BIG and special thanks for OMV-Extras team for great plug-ins (especially: TeamSpeak, VirtualBox, Sonarr, Radarr, and rest I use :))

      ------------------------------

      Wise guy don't know everything, he can search or ask!
      Don't ask me via PM!
    • Symbiot wrote:

      make sure you place the config dir outside the docker container so you can edit rtorrent.rc

      Mind explaining how to do that? I've got the rtorrent/rutorrent docker container running, forwarded the web GUI port to a different one, mapped the shares to the container, but I'd prefer to do the configuration through the .rc file than the rutorrent settings. I'm still testing in a VM, so no issues deleting this image and creating it again if necessary.
    • flvinny521 wrote:

      Symbiot wrote:

      make sure you place the config dir outside the docker container so you can edit rtorrent.rc
      Mind explaining how to do that? I've got the rtorrent/rutorrent docker container running, forwarded the web GUI port to a different one, mapped the shares to the container, but I'd prefer to do the configuration through the .rc file than the rutorrent settings. I'm still testing in a VM, so no issues deleting this image and creating it again if necessary.
      Oh and you remembered to set PGID & PUID (just read what you wrote about qbittorrent.)
    • Symbiot wrote:

      Nothing special. Just as I wrote, make sure you map the config dir to an external folder... like your "downloads" etc.
      I assume you've done that :) just wanted to point it out.

      Anything writted in the .rc file will overwrite any webui changes you make anyway.

      Per the container info, the rtorrent.rc file resides at /downloads/, so I could map this directory as follows?



      Symbiot wrote:

      Oh and you remembered to set PGID & PUID (just read what you wrote about qbittorrent.)

      Actually I'm not the OP, I wasn't using qbittorrent. I hadn't done this but I'll make sure this time.

      The post was edited 1 time, last by flvinny521 ().

    • this is my setup of linuxserver/rutorrent

      I'm mapping download share & config folder to external folder/drivers.. as you're doing with srv/...... ->/downloads

      I don't know the container you're using so can't comment too much on it. If it maps config to downloads then that should be fine.. however the comment I made regarding PGID & PUID are only used with linuxserver containers.. well I've only seen it with those and I tend to look to linuxserver dockers first.



    • Symbiot wrote:

      this is my setup of linuxserver/rutorrent

      I was using the diameter container simply because it had more stars. I have it completely working, except that torrents won't download after they're imported from the watch folder (so not working at all, then?). They just stay inactive forever, no error messages, but no data being transferred. I'm going to try the linuxserver container and I'll make a thread elsewhere if I still have trouble.

      Yup, same issue with the linuxserver container. I can add torrents to the watch folder and they're loaded into the web UI, but even though seeds and peers are detected, I never download any data. Weird. Maybe I'll try on a live install rather than a VM.

      The post was edited 1 time, last by flvinny521 ().

    • Symbiot wrote:

      this is my setup of linuxserver/rutorrent

      Sorry to bother you again. I've looked into this and even chatted with some people on the #docker IRC channel. They seem to think it's a conflict between the bridged Docker network and my own physical network. Was there anything special you had to do in order to prevent any conflicts? My setup looks very similar to the one you inserted in your above post, with the exception of me using different ports than you. Anything I need to do outside of the container settings?
    • Symbiot wrote:

      outside the container no.. can you post a ss of your setup window?

      I'm running this inside a VMWare Player VM, which is set to network bridge mode, so the VM is connected directly to my physical network. I assume this is not the issue since OMV has no problems downloading except from within Docker. Can't stretch the window to fit it all in one image:


      The post was edited 1 time, last by flvinny521 ().

    • And the client in (in)action:



      with a nearly untouched rtorrent.rc:

      Source Code

      1. execute = {sh,-c,/usr/bin/php7 /usr/share/webapps/rutorrent/php/initplugins.php abc &}
      2. execute.nothrow = rm,/run/php/.rtorrent.sock
      3. network.scgi.open_local = /run/php/.rtorrent.sock
      4. schedule = socket_chmod,0,0,"execute=chmod,0660,/run/php/.rtorrent.sock"
      5. schedule = socket_chgrp,0,0,"execute=chgrp,abc,/run/php/.rtorrent.sock"
      6. log.open_file = "rtorrent", /config/log/rtorrent/rtorrent.log
      7. log.add_output = "info", "rtorrent"
      8. min_peers = 40
      9. max_peers = 1200
      10. max_uploads = 15
      11. #download_rate = 10000
      12. #upload_rate = 5000
      13. schedule = watch_directory_1,5,5,"load.start=/downloads/watched/*.torrent"
      14. directory = /downloads/incoming
      15. session = /config/rtorrent/rtorrent_sess
      16. schedule = low_diskspace,5,60,close_low_diskspace=100M
      17. # ip = 178.32.28.51
      18. bind = 0.0.0.0
      19. port_range = 51413-51413
      20. check_hash = yes
      21. use_udp_trackers = yes
      22. encryption = allow_incoming,try_outgoing,enable_retry
      23. dht = auto
      24. dht_port = 6881
      25. peer_exchange = yes
      26. # network.http.ssl_verify_peer.set=0
      27. # scgi_port = 0.0.0.0:5000
      28. encoding_list = UTF-8
      29. # system.umask.set = 022
      Display All

      The post was edited 1 time, last by flvinny521 ().

    • Symbiot wrote:

      if your vm is in host mode for the network config then that part should be ok, but we need to make sure that you've opened the correct port/ports in your router.


      Sorry for the delay, I was having some issues with my ISP gateway/router. IPv6 has proven difficult on the Edgerouter, but I went ahead and switched back to it anyway. I'll worry about that later.

      Anyway, yes, the ports are (and were) correctly forwarded. Since the VM is connected directly to my network, the ports test open from any machine.
    • flvinny521 wrote:

      Symbiot wrote:

      if your vm is in host mode for the network config then that part should be ok, but we need to make sure that you've opened the correct port/ports in your router.
      Sorry for the delay, I was having some issues with my ISP gateway/router. IPv6 has proven difficult on the Edgerouter, but I went ahead and switched back to it anyway. I'll worry about that later.

      Anyway, yes, the ports are (and were) correctly forwarded. Since the VM is connected directly to my network, the ports test open from any machine.
      Ok, try changing a few things..

      Increase your port selection... and move it to another range like 49005 -> 49010 so you have 5 ports dedicated to rtorrent and set rtorrent to select random port.
      Then disable dht & udp.. i've changed the below from your config.


      Source Code

      1. port_range = 49005-49010
      2. check_hash = no
      3. use_udp_trackers = no
      4. encryption = encryption = allow_incoming,enable_retry,prefer_plaintext
      5. dht = disable
    • Display Spoiler


      Symbiot wrote:

      Ok, try changing a few things..
      Increase your port selection... and move it to another range like 49005 -> 49010 so you have 5 ports dedicated to rtorrent and set rtorrent to select random port.
      Then disable dht & udp.. i've changed the below from your config.

      Source Code

      1. port_range = 49005-49010
      2. check_hash = no
      3. use_udp_trackers = no
      4. encryption = encryption = allow_incoming,enable_retry,prefer_plaintext
      5. dht = disable

      Oddly enough, making these changes and adjusting my port forwarding accordingly results in "connection refused" responses from canyouseeme. The first time I restarted the container, rtorrent had chosen 49010, and that port wasn't able to be seen. Same thing when I restarted again and it chose 49005. I set it back to a single non-random port (49010) and again the port wasn't able to be seen. I tried 59010 with the same result. I had tested it previously and was definitely seeing open ports. Could it have to do with encryption settings?

      The .rc I was using:


      Source Code

      1. execute = {sh,-c,/usr/bin/php7 /usr/share/webapps/rutorrent/php/initplugins.php abc &}
      2. execute.nothrow = rm,/run/php/.rtorrent.sock
      3. network.scgi.open_local = /run/php/.rtorrent.sock
      4. schedule = socket_chmod,0,0,"execute=chmod,0660,/run/php/.rtorrent.sock"
      5. schedule = socket_chgrp,0,0,"execute=chgrp,abc,/run/php/.rtorrent.sock"
      6. log.open_file = "rtorrent", /config/log/rtorrent/rtorrent.log
      7. log.add_output = "info", "rtorrent"
      8. min_peers = 80
      9. max_peers = 250
      10. max_uploads = 50
      11. #download_rate = 10000
      12. #upload_rate = 5000
      13. schedule = watch_directory_1,5,5,"load.start=/downloads/watched/*.torrent"
      14. directory = /downloads/incoming
      15. session = /config/rtorrent/rtorrent_sess
      16. schedule = low_diskspace,5,60,close_low_diskspace=100M
      17. # ip = 178.32.28.51
      18. bind = 0.0.0.0
      19. port_range = 49005-49010
      20. port_random = yes
      21. check_hash = no
      22. use_udp_trackers = no
      23. encryption = allow_incoming,enable_retry,prefer_plaintext
      24. dht = disable
      25. dht_port = 6881
      26. peer_exchange = yes
      27. # network.http.ssl_verify_peer.set=0
      28. # scgi_port = 0.0.0.0:5000
      29. encoding_list = UTF-8
      30. # system.umask.set = 022
      Display All
      And my forwarding:

      Port 49005-49010, Protocol Both, Forward-to-address 192.168.1.22, Forward-to-port blank (use original port #), and a description.


      Edit - Forgot to specify those ports in the Docker container. Whoops. Testing again. Rtorrent.rc contents in the spoiler.

      OK, seems to be the same result. I do see a very low download speed (0.2 kB/sec) but the completion remains at 0% and rutorrent still reports 0 chunks downloaded. Does rtorrent put the torrent in an "inactive" status if the transfer speed doesn't ramp up after a short time?



      Also, this weekend my brother is going to drop off an SSD I had given him, so I can install OMV on a live system and dual boot. Maybe the VM is the variable that needs to be eliminated.

      The post was edited 5 times, last by flvinny521 ().

    • @Symbiot

      I have installed OMV 3.0.86 on a real system and the media is transferring from my backup onto the pool. I thought maybe removing the VM from the equation would solve my woes, but I'm still not having any luck. I am considering having all my applications run in Docker, and so far I've been successful, but rtorrent just does not want to cooperate.



      And my config:

      Source Code

      1. execute = {sh,-c,/usr/bin/php7 /usr/share/webapps/rutorrent/php/initplugins.php abc &}
      2. execute.nothrow = rm,/run/php/.rtorrent.sock
      3. network.scgi.open_local = /run/php/.rtorrent.sock
      4. schedule = socket_chmod,0,0,"execute=chmod,0660,/run/php/.rtorrent.sock"
      5. schedule = socket_chgrp,0,0,"execute=chgrp,abc,/run/php/.rtorrent.sock"
      6. log.open_file = "rtorrent", /config/log/rtorrent/rtorrent.log
      7. log.add_output = "info", "rtorrent"
      8. min_peers = 40
      9. max_peers = 125
      10. max_uploads = 15
      11. # download_rate = 10000
      12. # upload_rate = 5000
      13. schedule = watch_directory_1,5,5,"load.start=/downloads/watched/*.torrent"
      14. directory = /downloads/incoming
      15. session = /config/rtorrent/rtorrent_sess
      16. schedule = low_diskspace,5,60,close_low_diskspace=100M
      17. # ip = 178.32.28.51
      18. bind = 0.0.0.0
      19. port_range = 60548-60548
      20. check_hash = no
      21. use_udp_trackers = no
      22. encryption = allow_incoming,enable_retry,prefer_plaintext
      23. dht = disable
      24. dht_port = 6881
      25. peer_exchange = no
      26. # network.http.ssl_verify_peer.set=0
      27. # scgi_port = 0.0.0.0:5000
      28. encoding_list = UTF-8
      29. # system.umask.set = 022
      Display All