ColdChuck

thanks for the links above, tracked it back via github and arch already have the patch in place, i wondered why i wasnt seeing the issue Np! By the way, for anybody wanting to roll back, it is as easy as appending ":52" to the "Repository" field and update the container. Thanks a lot Finally a fix / workaround to the underlying problem. I got it working by adding this suffix. Working for me too. Thanks! Sent from my SM-G935W8 using Tapatalk

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 Take a look here, this might be of interest https://github.com/binhex/arch-rtorrentvpn/issues/10 Issue solved (i think) by altering the tTorrent config. Sent from my SM-G900F using Tapatalk How did you fix it finally? Having the same issue. It was working fine with https trackers up to a couple days ago but since then all I got are timeouts. ok so assuming your issue is this, if it isn't then please ignore this fix (shown in rutorrent):- Tracker Status: Tracker: [Peer certificate cannot be authenticated with given CA certificates] If this is the issue then one way of fixing this is to edit rtorrent.rc file (rtorrent configuration file) and add the line:- network.http.ssl_verify_peer.set = 0 This basically tells rtorrent to ignore ssl verification for all trackers. Just to be clear this works for the docker image i created, so im not talking specifically about the LSIO version here, but i see no reason why this shouldn't also work for the LSIO docker image. Yeah I already tried that but it didn't fix the problem. The error I have is: Tracker: [Timeout was reached]

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 Take a look here, this might be of interest https://github.com/binhex/arch-rtorrentvpn/issues/10 Issue solved (i think) by altering the tTorrent config. Sent from my SM-G900F using Tapatalk How did you fix it finally? Having the same issue. It was working fine with https trackers up to a couple days ago but since then all I got are timeouts.