scottc

Members
  • Content count

    252
  • Joined

  • Last visited

Community Reputation

0 Neutral

About scottc

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. No problem at all Jackett is what I use also
  2. You could use Jackett or Cardigann dockers for indexers
  3. I ran into this problem when I first installed radarr. The issue is the mapping for downloads. Add ( or change ) the container mount point from downloads to downloaded. radarr is looking for a directory named downloaded not downloads. what i did was just add a new path variable in the docker template and mapped /downloaded to the download directory for deluge
  4. Yah, that is the one drawback to updating from within radarr, when you restart or update the docker it defaults to the version in the docker file. I just remind myself to go update it in radarr if I update the container ( or restart the server )
  5. You can update from within radarr. Goto System -> Updates and update to the latest version.
  6. use the --progress switch in your rsync command will give you an idea of how many files are left to transfer like this rsync -avh --progress /mnt/user/PlexData/ root@192.168.1.107:/mnt/user/PlexData/
  7. A 403 Forbidden Notice could also be coming from a mod_security rule on the server. Not sure who runs the servers but they might want to whitelist the wiki ( or find the rule that is blocking your IP when on the wiki )
  8. Is your system a dual CPU system? the MB you have in your server specs is a single CPU MB. If that is the case and you only have a single CPU you may want to redo your CPU Pinning. You are using 10 core's for your WIN 10 VM and 4 for your LibreELEC VM. and this could be causing some of your issues
  9. You should be updating by using the update plugin option Go to the Plugins page and click Check for Updates. Afterwards it will tell you a new version of unRAID is available; click the update button and reboot your system, done!
  10. Upgraded with no issues
  11. I just tested this on my install, made sure all disks were spun down. Restarted the plex docker with no issues and did not spin up any of my hard drives, then did a force update and again completed with no issues and did not spin up any of my hard drives.
  12. No issue with upgrade here
  13. Couldn't you change the mover settings to run something like monthly or weekly? then it would not be moving stuff as often
  14. Yup, Latest update fixed the issue for me also Does this mean that there haw been an additional CrashPlan update since and that the 2nd fix took care of whatever the issue was in the first fix, or does it mean that it took 2 installs of the first (and only recent) fix to make it work? Also, what's been fixed/updated? I'm only 48GB into a 1TB photo backup, and it took several days for CP to settle itself down and actually start making progress. I don't want to kill off the backup if it's for something minor that won't really impact me. Many, many thanks to gfjardim for getting this docker working in the first place! There is an update to the CP docker and the update to the docker should not affect what you have already uploaded. when CP starts it should scan what has already been uploaded and start where it left off
  15. I just updated by Crashplan Docker and I'm having the same problem. I have the same problem. Just updated CP and VNC connection is not working and CP client also can't connect to server. Try to update again. That solved it for me. Sent from my SGP771 using Tapatalk Yup, Latest update fixed the issue for me also
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.