Thoradia Add-ons

    Quote from yelkao

    Is there a known issue with https trackers with the rutorrent/rtorrent add-ons ?
    http torrents work fine but when using https , I get Tracker: [Timeout was reached] and of course no peers or seeds
    I have tried setting http_capath = /etc/ssl and tested the trackers https url with curl successfully

    Is there something else I am missing?

    Please provide a log, see post #176

    http_capath is deprecated, see rTorrent 0.9 Comprehensive Command list (WIP) · rakshasa/rtorrent Wiki · GitHub

    If you find out a way to make https trackers work, I will gladly update rtorrent accordingly.

    Thank you in advance for your feedback

    Not really had issues with https trackers in the past running rtorrent on Raspbian and even an entware deploy on my router.
    I am using Librelec 8.0.2 on rpi3 and have been running rtorrent/rutorrent in docker successfully so will revert to that in the interim. I suspect the problem could be related to libcurl and openssl versions in Libreelec. When I find some time I will look at setting up a build environment so I can try rebuilding curl.
    Really liking the other add-ons in this set though. Outstanding job to get all of this running together.

    Quote from yelkao

    Not really had issues with https trackers in the past running rtorrent on Raspbian and even an entware deploy on my router.
    I am using Librelec 8.0.2 on rpi3 and have been running rtorrent/rutorrent in docker successfully so will revert to that in the interim. I suspect the problem could be related to libcurl and openssl versions in Libreelec. When I find some time I will look at setting up a build environment so I can try rebuilding curl.
    Really liking the other add-ons in this set though. Outstanding job to get all of this running together.

    yelkao

    Would you please be so kind to tell me how these are configured in your working rtorrents:

    rTorrent - ArchWiki

    Unclear how to use multiple SSL certs · Issue #468 · rakshasa/rtorrent · GitHub

    Thanks in advance for your feedback

    Quote from thoradia

    Would you please be so kind to tell me how these are configured in your working rtorrents

    After some further testing, I dont think the issue is certificate related.

    For other implementations I have just refered to a ca certificate in .rtorrent.rc

    ie for the docker instance (which is rutorrent 3.7 rtorrent 0.9.6/0.13.6) I am using

    network.http.cacert.set = /rtorrent/ssl/cert.pem

    removing this line causes tracker error

    "Tracker: [Peer certificate cannot be authenticated with given CA certificates]"

    However, running rtorrent in your add-on, I have found that there is no need to do anything with ca certificates as curl is using /etc/ssl/cert.pem by default

    By setting cacert to an invalid file I can force the error Tracker: [Peer certificate cannot be authenticated with given CA certificates]

    leaving capath unset, or referring to a failed certificate file I see no certificate error but eventually eventually get the timeout message. I think this shows that it accepts the certificate but will still not connect to the tracker properly.

    I suspect the issue is curl/libcurl related There are certainly some protocol and feature differences between the build in the docker image I am using compared with the curl in libreelec.

    pi3mc:~ # docker exec rpi-torrent curl -V

    curl 7.39.0 (armv7l-unknown-linux-gnueabihf) libcurl/7.38.0 OpenSSL/1.0.1k zlib/1.2.8 libidn/1.29 libssh2/1.4.3 librtmp/2.3

    Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smtp smtps telnet tftp

    Features: AsynchDNS IDN IPv6 Largefile GSS-API SPNEGO NTLM NTLM_WB SSL libz TLS-SRP

    pi3mc:~ # curl -V

    curl 7.52.0 (armv7ve-libreelec-linux-gnueabi) libcurl/7.52.0 LibreSSL/2.4.4 zlib/1.2.8 librtmp/2.3

    Protocols: file ftp ftps http https rtmp rtsp

    Features: AsynchDNS IPv6 Largefile NTLM NTLM_WB SSL libz UnixSockets HTTPS-proxy

    Looking at rpi-torrent-box/compiletorrent.sh at master · sdelrio/rpi-torrent-box · GitHub I would think that curl may need configuring prior to build with configure --enable-ares --enable-tls-srp --enable-gnu-tls --with-zlib --with-ssl


    I think I need to I build my own libreelec to test further and I wont have the time to attempt that this weekend

    Thanks for the feedback.

    I suggest to wait for LibreELEC 8.2, where openssl replaces libressl.

    Thoradia, first thank you for hard work putting this repo together.

    I'm trying to migrate my rtorrent and active torrents from the old openelec/libreelec unofficial repo install.

    Have a couple of problems with it: timezone is hardcoded somewhere and off by one hour, rutorrent scheduler does not work properly,...

    The problem is, the old addon doesn't use rtorrent.rc but passes all the config as parameters when starting rtorrent.

    I have currently both addons installed (only one active at a time) and confirmed working.

    So, the steps for me to migrate my torrents i guess would be:

    - translate all the settings from old addon XML to new rtorrent.rc

    - copy the session files

    - stop the old service, start a new one and hope for the best :)

    Problem is old addon has one option that I don't know how to port to new vanilla rtorrent: "Sort Series in Season Dirs".

    I have that option enabled due to Kodi scraper sometimes having problems with a certain filenames not being recognized. And the download dir is also nice and tidy.

    I figured out it uses some custom shell script (complete.sh) which does all the work.

    Found this on github, perhaps it's the same thing?

    Will have to try if it all works, am worried if the new rtorrent would pick up the series that are in sorted folders.

    Quote from csh

    Problem is old addon has one option that I don't know how to port to new vanilla rtorrent: "Sort Series in Season Dirs".

    I have that option enabled due to Kodi scraper sometimes having problems with a certain filenames not being recognized. And the download dir is also nice and tidy.

    I figured out it uses some custom shell script (complete.sh) which does all the work.

    Found this on github, perhaps it's the same thing?

    Will have to try if it all works, am worried if the new rtorrent would pick up the series that are in sorted folders.

    OE rTorrent/ruTorrent is unmaintained and quite convoluted, I therefore started from scratch.

    Moreover, I do not use rTorrent/ruTorrent, I therefore need you to tell me what you need and how it works.

    I hope you will be able to fix your problem.

    If you do, tell me how, and I will update the add-on accordingly.

    Quote from thoradia

    OE rTorrent/ruTorrent is unmaintained and quite convoluted, I therefore started from scratch.

    Moreover, I do not use rTorrent/ruTorrent, I therefore need you to tell me what you need and how it works.

    I hope you will be able to fix your problem.

    If you do, tell me how, and I will update the add-on accordingly.

    Thx again for packaging rtorrent, I'l try to configure it for my needs. Not an easy task considering the documentation is sparse and you have to hunt for config examples all over the net :)

    If I find anything useful, will post here.

    Quote from thoradia

    The add-ons are ready for LibreELEC 8.2.

    Please report any issues here.

    Thanks heaps for continuing to update these add-ons. With openssl included, I thought I would give 8.2 a try.
    I compiled libreelec and installed the 8.2 add-ons. Unfortunately ssl trackers were still not working with rtorrent. After a little bit of research I found it is actually a known issue with the 7.52 version of curl that is included in LibreElec.
    So, I modified packages/web/curl/package.mk and replaced PKG_VERSION="7.52.0" with PKG_VERSION="7.53.1"
    Recompiled and ssl trackers work!
    So I no longer need to run rutorrent in docker and have the added bonus that I can set my own root password. It was worth compiling Libreelec just for that anyway. Also using sickrage, couchpotato and jackett with no issues identified. It is a fantastic set of add-ons. Thanks again.

    Quote from yelkao

    Thanks heaps for continuing to update these add-ons. With openssl included, I thought I would give 8.2 a try.
    I compiled libreelec and installed the 8.2 add-ons. Unfortunately ssl trackers were still not working with rtorrent. After a little bit of research I found it is actually a known issue with the 7.52 version of curl that is included in LibreElec.
    So, I modified packages/web/curl/package.mk and replaced PKG_VERSION="7.52.0" with PKG_VERSION="7.53.1"
    Recompiled and ssl trackers work!
    So I no longer need to run rutorrent in docker and have the added bonus that I can set my own root password. It was worth compiling Libreelec just for that anyway. Also using sickrage, couchpotato and jackett with no issues identified. It is a fantastic set of add-ons. Thanks again.

    Great find! Thanks!

    Now we have to determine how to fix.

    rtorrent and transmission refer to libcurl.so.4 provided by LibreELEC.

    LibreELEC 9.0 provides curl 7.54.0, so we can assume that the problem is fixed on LibreELEC 9.0.

    LibreELEC 8.x provide curl 7.52, which is unlikely to change.

    We have several options:

    1. submit a pull request to update curl on LibreELEC 8.x (I would not count on that)

    2. build curl 7.54.1 static in the thoradia build system

    3. build curl 7.54.1 shared in the thoradia build system and ship libcurl.so.4 with rtorrent and transmission.

    I will attempt option 2

    yelkao

    This builds and runs on my system: Commits · thoradia/LibreELEC.tv · GitHub

    I will build rtorrent, rutorrent and transmission from scratch for LibreELEC 8.2 and push them to my repository.

    They should be ready tomorrow morning.

    If you confirm that rtorrent and rutorrent 8.2.5 work on a vanilla LibreELEC 8.2 (with curl 7.52.0), then I will apply the corresponding changes to LibreELEC 8.0.

    Thank you for your help.