MyKroFt

Shut down the docker, remove the rtorrent.lock from the session folder and you should be good to go Myk

ok, this works /boot/scripts/rrm.sh #!/bin/bash IFS="/" read -ra PARTS <<< "$(pwd)" mv "$1" "/${PARTS[1]}/${PARTS[2]}/.Recycle.Bin/" alias rrm="/boot/scripts/rrm.sh" test on junk file to make sure Myk

Maybe a alias for rm - that instead of just deletes the file, moves it to the recyclebin folder in that share? something like (not tested - not very good at bash) alias rrm="IFS="/" read -ra PARTS <<< "$(pwd)" ; mv $0 /${PARTS[0]}/${PARTS[1]}/.Recycle.Bin/" rrm would be for recycle delete, leaving rm for perm delete looks like it might have to be made into a bash script and have the rrm alias call the bash script instead Myk

When - not if rTorrent crashes and the check script sees it and goes to restart it - the OpenVPN connection has been lost - but never gets reconnected. I have to actually stop and restart the container for the OpenVPN tp AirVPN to get reconnected - in the meantime all my seeds\ connections have been lost at the tracker (timeout - take 60 min for this tracker) so it needs to restart OpenVPN also when rTorrent gets restarted? Myk UPDATE: Seems like any time a Torrent finishes downloading - rTorrent crashes and the web interface can reach it - have to restart the container

You should be able to set it to /data once during a torrent download and it should be remembered - its is case sens..... Myk hmm very odd, so you have this file in /config/openvpn/:- http://www.ipvanish.com/software/configs/ca.ipvanish.com.crt is that correct?, looking at that cert it isnt from PIA (see attachment), im pretty sure the crt file you have in /config/openvpn/ is not the one from the above url, can you double check please, also just ensure there is only a single crt file in there, it could be picking up the PIA cert in there if you previously had it set to pia before switching to custom. edit - keep in mind ipvanish does NOT support incoming ports (port forwarding), so using ipvanish for torrents is going to be slow at best (https://support.ipvanish.com/customer/portal/articles/1969161-port-forwarding) I ended up switching to PIA for faster speeds. Thanks. My next issue is that even though I have the download directory set to /data it keeps saving my downloads to /downloads .. Any idea on how to make it save there permanently? I have the /data directory setup in the configuration file

Anybody? Sent from my SM-G920V using Tapatalk

Its happening with the ruTorrentVPN container as well.... Been like this for 2-3 days now Myk

I think it is 10 min - wihich is SBs min watch/scan time Myk

I have sabVPN move the completed download to a holding location and have a watched folder in SickBeard looking at SABs holding location. SickBead is what moves, renames before moving it into my TV share in the array Myk

ok, never thought of it that way sqlite3 downloaded and installed, sql command executed, and my recent tv on the dashboard is back to normal thanks for the tip! Myk

So far everything looking good.... Myk

I need to run the following in order to fix some TV On Deck problems with some dates that got to 2038 somehow - others via plex forms have had this problem also - if not running in a docker I could work my way thru but - but in a docker I am not sure how to proceed sudo service plexmediaserver stop && sudo sqlite3 /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db "UPDATE metadata_items SET added_at = created_at WHERE DATETIME(added_at) > DATETIME('now');" && sudo service plexmediaserver start Suggestions please..... Thanks Myk

Just installed this docker and am getting the same thing - windows client is working just find on my 3 win 10 machines - they are getting out to the server WUI is not loading as well Ideas? Myk

Ok, will give it a shot and let ya know Thanks Myk

Thank You! much appreciated Myk

Also when I get the above error - I have to restart the container as it slowly dies and can not connect to the trackers... Myk

ok, this is aparently my problem: 2016/05/30 08:29:31 [error] 700#0: *923 client intended to send too large body: 2312290 bytes, client: 192.168.0.204, server: localhost, request: "POST /php/addtorrent.php?torrents_start_stopped=1&dir_edit=%2FSeeds&label=PD HTTP/1.1", host: "192.168.0.104:9080", referrer: "http://192.168.0.104:9080/" Does the php.ini need to be told to allow larger file upload? torrent has 5804 files in it..... Myk

Ok, getting my seeds etc moved from Deluge over - but I have hit a roadblock and I searched and tried editing the .rc for hours last night - but I am suck at 10 total seeds/downloads. I tried editing the global up/down variables - but I can not get past 10 Ideas please - new to this torrent program Thanks Myk

I am not getting the crashplan warning anymore after updating today.... Thanks! Myk

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 I am now connecting vpn so I have the port forwarded via the vpn providor. The DHT port is what is hollaring on this setup where I was ok on the Deluge one Status bar attached Also I am not worried as I told the config to leave private torrents as is and announce them anywhere else Myk looking at that screenshot it looks like your incoming port is not open (red icon), i dont think that icon is showing you issues with DHT, what vpn endpoint are you connecting to?. AirVPN when I mouse over the red ! I get - 6881: Port is closed which is what DHT is set to I have 26118 as my inbound port, that is forwarded at AirVPN, also forwarded thru my router to unRAID like my other port that is configured for the DulugeVPN docker. But when testing at AirVPN - the 26118 fails. I have green bar for the Deluge one and a blue bar for the rTorrent one at AirVPN Am not sure what I am doing wrong as I want to move to ruTorrent - like it much better Myk

Latest version isntalled but it is hollaring about the crashplan docker: Docker application CrashPlan does not have the same webUI interface as what the template author specified The webUI the author specified is http://[iP]:[PORT:4280]/vnc.html?autoconnect=true&host=[iP]&port=[PORT:4280] and the webUI you are using is http://[iP]:[PORT:4280]/vnc.html?autoconnect=true&host=[iP]&port=[PORT:4280]. If you are specifying an absolute port (IE: PORT:xxxx is missing from your specified webUI address, then you will have issues should you ever have to change the host port on the docker applications's settings. In the same vein, specifying an absolute IP address in the webUI will cause issues should your server's IP address ever change. Note that the PORT:xxxx refers to the Container's port, not the host port. There may however be perfectly valid reasons to change the default webUI entry on the application. They are the same? Thanks Myk

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 I am now connecting vpn so I have the port forwarded via the vpn providor. The DHT port is what is hollaring on this setup where I was ok on the Deluge one Status bar attached Also I am not worried as I told the config to leave private torrents as is and announce them anywhere else Myk

I have noticed this as well... Also mine is hollering about port 6881 on the bottom status - never had that with the DelugeVPN one.... Myk

K, that fixed it up and is now working and getting to the UI as well.... Thanks Myk

Any ideas? Thanks Myk