Jump to content

uraid

Members
  • Posts

    40
  • Joined

  • Last visited

Posts posted by uraid

  1. Thank you binhex but as the others said it was not the issue. The error message does not include 'CA cert' inside it, only timeout.

    As I said earlier (https://lime-technology.com/forum/index.php?topic=47299.msg530444#msg530444) and as 3psus said, this seems like an issue with the curl package, and the next scheduled release is in February.

    If someone can find a solution before the next release of curl it would be awesome! :)

  2. If I update it from 'docker exec -t -i rutorrent /bin/bash'- would it be changed just for rutorrent or for all dockers? Just curious.

    Anything you do from the command line within a docker only affects the current installation of that docker.

    Thank you. Now just to figure out how to get gcc installed on the docker lol

    Note I said the "current installation". If you ever have to reinstall for any reason anything you did from docker exec would have to be reapplied. Making your own docker with the changes already applied is the way to make them stick for a reinstall.

    Oh got it :)

    It's very strange that I'm the first one that encounters problems with https trackers on this container :o

  3. If I update it from 'docker exec -t -i rutorrent /bin/bash'- would it be changed just for rutorrent or for all dockers? Just curious.

    Anything you do from the command line within a docker only affects the current installation of that docker.

    Thank you. Now just to figure out how to get gcc installed on the docker lol

  4. skyline7349, you need to edit the /mnt/user/appdata/rutorrent/rtorrent/rtorrent.rc for changing some of the settings.

     

    I'm not sure that gets to the root of his problems, he's got issues with several docker containers and I'm willing to bet there is one root cause.

    Ok I think I missed this.

    By the way, I think my problem from page 14 is caused by the curl version in the docker image.

    If I update it from 'docker exec -t -i rutorrent /bin/bash'- would it be changed just for rutorrent or for all dockers? Just curious.

     

    Sources for the problem:

    https://github.com/rakshasa/rtorrent/issues/457

    https://github.com/curl/curl/issues/1174

    https://github.com/rakshasa/rtorrent/issues/501

  5. Hi there :)

     

    I built my new unRAID server 2 days ago and am very happy with it.

    I just have one question - did anyone encounter problems with the rutorrent docker?

    When my torrents have HTTPS trackers, it just times out. When I change them to http it works as normal.

    I already tried those rtorrent settings that didn't work: 'network.http.capath.set = /etc/ssl/certs', and 'network.http.ssl_verify_peer.set = 0'

    I verified the trackers are online when it timed out (3 different trackers, all of them works on my workstation).

     

    Thanks a lot in advance and hope to contribute to the community in the future!

×
×
  • Create New...