uraid

For those that want a workaround to get it working again after last update broke it: Pull the version before the last (6 days earlier than it) - 2.8.8-cbf850a0-Ubuntu18-ls122 Worked for me in the meantime

Hi Peter, Great plugin! Thanks for your work. Is there an easy way to block LAN access without using iptables?

Could it be that your vpn credentials have expired? Try to login manually from your pc using the OpenVPN config.

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.

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!

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

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

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

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

You need to access the docker directly and make a change to nginx.conf: docker exec -t -i rutorrent /bin/bash Then inside the docker: vi /etc/nginx/nginx.conf Use this guide here to know what to add / edit: http://www.juanjchong.com/2014/setting-up-rtorrentrutorrent-on-ubuntu-14-04-using-ngnix/

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!