scottc

Members
  • Content count

    254
  • Joined

  • Last visited

Community Reputation

0 Neutral

About scottc

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. @tman12 the AHD file you are looking for will be within the docker container itself. Personally I use the linuxserver jacket docker and have configured all the different sites i use in that. But i have not had any problems with this type issue ( although I do not use AHD )
  2. This sounds like something with Radarr itself and would not have anything to do with the docker itself. I would post a bug report at https://github.com/Radarr/Radarr/issues
  3. No problem at all Jackett is what I use also
  4. You could use Jackett or Cardigann dockers for indexers
  5. 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
  6. 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 )
  7. You can update from within radarr. Goto System -> Updates and update to the latest version.
  8. 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/
  9. 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 )
  10. 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
  11. 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!
  12. Upgraded with no issues
  13. 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.
  14. No issue with upgrade here
  15. Couldn't you change the mover settings to run something like monthly or weekly? then it would not be moving stuff as often
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.