Wob76

Just playing a little more, I noticed on my box that the v0.3.1 script does exist, if I select that in the GUI I just get no result.

Hi dmacias, I just wanted to say thanks for the latest update, I have mine set to use the beta with a manual server and a timeout of 60 seconds, no more blank results. Thanks, Wob

Thanks dmacias, Your solutions sound like they will do the trick, as I mentioned I mainly use it to test for peak speed dips, and it does a great job at that, just the blank results that are putting me out, so if there could be a check or retry for that it would be great. Thanks, Wob

Hi, Thanks for the great plugin, it is very handy. I have a slight "bug\issue" If I leave my server selection on auto I get poor speed results around 30Mbit/s Down and 3-4Mbit/s up using server (UBC Web Design (Ballarat)). But If I manually select a different server I get around my actual speed connections. I put this down to the server it is landing on, if I manually run speedtest-xml I see the same results. If I run speedtest-cli I get a server (Telstra (Melbourne)) and speeds close to max (91-93 and 34). However if I manually run speedtest-linux I get a different server (Melbourne (Telstra)) and speeds close to max. So there seems to be a change in logic of server selection with speedtest-xml. I am not too worried about gettting a MAX reading, I really run it too see if I get any peak speed drops, so manually selecting the server is OK. But the issue I have then is that I seem to get more blank results back, than if I leave it on auto. I am not sure why it is failing (not much in the logs) but I know my connection is still active at the time of the test, I have other things running to detect dropouts. Is it possible that the -xml could have its server selection tweaked, or if when selecting manual you can have a backup server that is used if no result is returned? Or even the ability to black list some servers? Blank Result Log: Jun 3 00:00:01 TheBox speedtest: Internet bandwidth test started Jun 3 00:00:12 TheBox speedtest: Host: Jun 3 00:00:12 TheBox speedtest: Jun 3 00:00:12 TheBox speedtest: Internet bandwidth test completed Also, when I select "manual" on the settings page, I seem to get the same servers listed multiple times, I can't tell if they are different, name and distance is the same, maybe if it returned the server number as well so we could identify them? Thanks again, Wob Edit: Just some further info, with the plugin on auto it states it is using ping to pick a server, but the ping results are much higher than when I manually select a different server. Auto Jun 3 12:37:54 TheBox speedtest: Internet bandwidth test started Jun 3 12:42:30 TheBox speedtest: Host: UBC Web Design (Ballarat) [151.03 km] Jun 3 12:42:30 TheBox speedtest: Ping: 49.018 ms, Download: 30.90 Mbit/s, Upload: 3.65 Mbit/s Jun 3 12:42:30 TheBox speedtest: Internet bandwidth test completed Manual Jun 3 13:02:17 TheBox speedtest: Internet bandwidth test started Jun 3 13:02:46 TheBox speedtest: Host: AARNet (Melbourne) [225.60 km] Jun 3 13:02:46 TheBox speedtest: Ping: 32.289 ms, Download: 91.89 Mbit/s, Upload: 35.79 Mbit/s Jun 3 13:02:46 TheBox speedtest: Internet bandwidth test completed

Hi, Do you need to turn off the auto update feature within Jackett? It is on by default, I didn't touch it, but a few days ago my container crashed, looking at the logs it appears this was after it attempted to auto update. On a side note, are there an options in unraid to have dockers restart or update on a schedule? Or do I need to look at cron jobs? The new plugins autoupdate seems to be working a treat, something similar for dockers would be nice. Thanks, Wob

not as far as i know, no, i just did a quick test, loaded up a torrent from a public index site and i can see seed/peer counts increasing from a udp tracker, so looks to be working, check your rtorrent.rc file and make sure udp is enabled. Yeah I did do that, I'll do some further digging. Thanks, Wob Sent from my SM-G900I using Tapatalk

I'm with binhex on that, that icon is related to the port checker, which should be checking your listening port, can you screenshot your port setting page? Binhex, do you have any issues with upd trackers? Like I posted. Wob Sent from my SM-G900I using Tapatalk

Hi Myk, Are you talking about the port checker down the bottom? That should be checking whatever port you are using to connect externally, and you need to ensure you have allowed that via your firewall (if you have VPN disabled, which you had said you were doing). If the port checker is not green then your upload speed will be poor. Port 6881 is the port for DHT, I have it disabled as most private tracker sites frown upon it's use. I don't think there is any check for it on the bottom though, so unless you have set your Listening port to the same port number it shouldn't set of any alarms, and I don't think it would be best practice to use a port that low for your listening port. Cheers, Wob

Hi (again), Is anyone having problems with UDP trackers? all my HTTP trackers are working a treat, but all the udp trackers come back with "Tracker: [unable to connect to UDP tracker.]" I don't have many UDP trackers, so haven't noticed it till now, everything else is running a treat a the moment, going out via PIA's Romanian server. Regards, Wob

Not sure how I missed that Thanks, looks good.

Hi binhex, Any thoughts on this? Thanks, Wob

Is anyone else seeing the "Welcome Emby Tester" message since the last update? I am running emby/embyserver:latest not the dev branch, so not sure why I am seeing this. I wasn't too worried to start with, just closed the dialogue and everything seemed OK, but I am also seeing slow downs since the update. I am seeing "Version 3.0.5934.0" in the settings. Is it possible to roll back versions of emby, or will that mess with the database? Thanks, Wob

Hi binhex, I am still having some issues with the multi-user environment. I use authentication on my reverse proxy, and every now and then it passes that auth on to rutorrent, and even though and account doesn't exist with that name it creates a folder under /share/users/ with that username and logs me in, and this messes with ratio's etc as discussed previously. I would like to disable multiuser by adding $forbidUserSettings = false; to the config.php, but you currently don't expose that outside the container. Is there any chance that this will be migrated\linked to the /config file in the future? Or alternatively can I request that the above variable be made the default, since for proper multiuser support requires separate rtorrent installs and scgi ports for each user. (As described here https://github.com/Novik/ruTorrent/wiki/Config) Thanks, Wob

Very odd, and so far it only seems to effect this container, but I don't restart them all that often. running Unraid 6.1.9 I just stopped and then started my CP and rTorrent dockers, both gave me errors, but CP only did it once before starting, rTorrent did it 4 times. Very odd behavior, not sure what has changed. Just need to work out where to direct my call for help. Thanks, Wob

Very odd, and so far it only seems to effect this container, but I don't restart them all that often. running Unraid 6.1.9

Found my problem, I had enabled a Proxy Server in CP at some point, via Privoxy in another docker. Disabling that fixed my issue.

Hi, Just wondering if anyone has the CP docker talking to the Jackett docker? I have Jackett working, Headphones is talking to it fine. But CP spits out the following errors. 05-04 15:11:14 ERROR [hpotato.core.plugins.base] Failed opening url in TorrentPotato: http://192.168.0.250:9117/jackett/potato/torrentleech?imdbid=tt4181052&user=&passkey=xxx If I punch the link into my web browser (inserting the API in passkey) it works fine. I am not seeing any hits in the Jackett logs so it doesn't look like CP is reaching it at all. 192.168.0.250 is my unraid boxes IP address. Thanks, Wob

I am having random issues starting this docker, I am getting various error code, it will eventually start if I just keep trying. I am not seeing any issues with any other containers. # docker start rTorrentVPN Error response from daemon: Cannot start container rTorrentVPN: Link not found Error: failed to start containers: [rTorrentVPN] # docker start rTorrentVPN Error response from daemon: Cannot start container rTorrentVPN: adding interface vethd5ab1df to bridge docker0 failed: could not find bridge docker0: no such network interface Error: failed to start containers: [rTorrentVPN] # docker start rTorrentVPN Error response from daemon: Cannot start container rTorrentVPN: could not set link down for container interface vethbee3906: no such device Error: failed to start containers: [rTorrentVPN] # docker start rTorrentVPN Error response from daemon: Cannot start container rTorrentVPN: adding interface veth9110d40 to bridge docker0 failed: could not find bridge docker0: no such network interface Error: failed to start containers: [rTorrentVPN] Any ideas?

tbh i have as much experience with rutorrent as you so i dont know the answer to this right now :-), off the top of my head you could try creating a custom label for each user account and then set each user account to create all torrents with that label, then they can easily see their torrents on the left under the "labels" dropdown. if you find a better more elegant solution then please post it here. Thanks for the response, it was more out of interest as I currently don't have a strong need for multiuser, for the moment I'll stick with admin as my user. I am still waiting for some torrents to hit seed ratio of 1.0 to see if the issue is resolved. Wob

Hi, Thanks for the reply, I have just completed a fresh install of the docker to see if I could narrow down the problem. I think my issue is being caused by multiple users. I created a new user and deleted admin but it seems that admin is still used (the folder under share\users is recrated on reboot of the docker). I am assuming it's called via a script somewhere. Anyway, if I recreate admin and log in, I see the same torrents, but it has its own set of ratios, so I am thinking that is my problem. I think I will just go back to using the admin account. Do you know if it possible in a multiuser environment to have the torrents only appear under that user? Thanks,Wob no changes from me in regards to plugins, one thought though, have you modified the rtorrent.rc file by any chance and re-enabled the watched section? if so this can conflict with the rutorrent "autotools" plugin, so just double check you havent got this happening. This caused me some headaches as downloading torrents would suddenly just disappear halfway through a download, took me a while to realise these two things are in conflict, i know this is different to your problem but you might want to double check all the same. Hi, It's still working fine using 0.9.6-3-24, so not sure what has changed, just double checked my rtorrent.rc file and watched section is still all commented out. # Watch a directory for new torrents, and stop those that have been # deleted. Note please ensure you disable the "AutoMove" in rutorrent # otherwise there could be a conflict that can cause deletion # of partially downloaded torrents. #execute = {/bin/bash,-c,mkdir -p /downloads/watched} #schedule = watch_directory,5,5,load_start=/downloads/watched/*.torrent #schedule = untied_directory,5,5,stop_untied= #schedule = untied_directory,5,5,remove_untied= Any other suggestions, or a way I can debug what is pausing them? Thanks, Wob hi, i think the reason your NOT seeing this in release 24 is that release 24 had an issue with initialization of the rutorrent plugins, so basically i had some code in the rtorrent.rc file which was supposed to fix the rutorrent plugin system initializing but it didnt always work, if you dont have the plugins initialised then any time based plugins wont work, such as RSS feed, autowatch, automove, scheduler etc, so i ended up being quite aggressive with this and poking the init script every time we do the while loop, and this fixed the issue, i now see the scheduler kick in correctly side note:- opening up the webui does trigger the init as well, but as this is a headless box i didnt want to have to do this. however, i think since the issue is fixed and the plugins are initialising correctly its caused a side effect for you, in as much as if the plugins are running then one or more of them is casing a conflict with your queue, probably due to a config change somewhere (im not seeing this issue btw). so in short i think the issue is a configuration based one and not a bug, i think my advise would be step through anything you have configured and maybe backout your change for each plugin one at a time, leave it for a while and see if it fixes the problem, maybe start with any sort of plugin that either monitors ratio or moves files around on completion, these are the ones most likely to be causing you issues. A quick bit of googling also points at these things for potential causes of paused state torrents:- 1. permissions issue (either with incomplete or completed folder) 2. download path doesn't exist 3. corrupt torrent none of the above 3 cases really explain why it works with release 24 and not the latest, but i thought i would put it out there incase it triggers something you might of remembered doing.

Hi, I just tried the latest (0.9.6-3-29) and still seeing this issue, if I roll back to 0.9.6-3-24 it works fine. Happy to try and diagnose if you can point me at logs or something to work with. Thanks, Wob no changes from me in regards to plugins, one thought though, have you modified the rtorrent.rc file by any chance and re-enabled the watched section? if so this can conflict with the rutorrent "autotools" plugin, so just double check you havent got this happening. This caused me some headaches as downloading torrents would suddenly just disappear halfway through a download, took me a while to realise these two things are in conflict, i know this is different to your problem but you might want to double check all the same. Hi, It's still working fine using 0.9.6-3-24, so not sure what has changed, just double checked my rtorrent.rc file and watched section is still all commented out. # Watch a directory for new torrents, and stop those that have been # deleted. Note please ensure you disable the "AutoMove" in rutorrent # otherwise there could be a conflict that can cause deletion # of partially downloaded torrents. #execute = {/bin/bash,-c,mkdir -p /downloads/watched} #schedule = watch_directory,5,5,load_start=/downloads/watched/*.torrent #schedule = untied_directory,5,5,stop_untied= #schedule = untied_directory,5,5,remove_untied= Any other suggestions, or a way I can debug what is pausing them? Thanks, Wob

no changes from me in regards to plugins, one thought though, have you modified the rtorrent.rc file by any chance and re-enabled the watched section? if so this can conflict with the rutorrent "autotools" plugin, so just double check you havent got this happening. This caused me some headaches as downloading torrents would suddenly just disappear halfway through a download, took me a while to realise these two things are in conflict, i know this is different to your problem but you might want to double check all the same. Hi, It's still working fine using 0.9.6-3-24, so not sure what has changed, just double checked my rtorrent.rc file and watched section is still all commented out. # Watch a directory for new torrents, and stop those that have been # deleted. Note please ensure you disable the "AutoMove" in rutorrent # otherwise there could be a conflict that can cause deletion # of partially downloaded torrents. #execute = {/bin/bash,-c,mkdir -p /downloads/watched} #schedule = watch_directory,5,5,load_start=/downloads/watched/*.torrent #schedule = untied_directory,5,5,stop_untied= #schedule = untied_directory,5,5,remove_untied= Any other suggestions, or a way I can debug what is pausing them? Thanks, Wob

Hi binhex, Something seems to have changed with the latest update. Any torrent I have with a ratio over 1 is being paused, I have most of my torrents set by ratio group to autodelete at 1.5 or 2.0 but they will not make it as they get paused. I unpause them and a second later they are paused again. The issue only started this morning when I pulled down a docker update. Is there a log file that will tell me why they are being paused? Thanks, Wob Update: As a test I pulled down binhex/arch-rtorrentvpn:0.9.6-3-25 and it is working without the pausing issue. Scratch that, still effects 0.9.6-3-25. Update 2: OK, I have waiting a bit longer this time, have been running 0.9.6-3-24 for 20min and it hasn't yet pasued them yet, I'll update if it does but that seems to be the version before whatever changed.

I think he meant that was the torrent he was downloading, as per the image, not the OS he was using.

Hi All, Has anyone managed to work out a way to implement a "Minimum seed time"? I am using the extratio plugin to set my ratio's based on public\private trackers. I have a few ratio's set up, and they work fine, but the Ratio plugin doesn't have a min seed time, the "Time,h" is the max seed time. So as such if my ratio is about set % my torrent will be removed, regardless if it has only just finished downloading. This can cause some issue with various trackers. This thread (http://www.torrent-invites.com/showthread.php?t=252590) tells me an option is command line tool rtcontrol (https://code.google.com/archive/p/pyroscope/wikis/RtControlExamples.wiki) but I am hoping there is some trick within rutorrent that I can't work out. Thanks, Wob