Squid

Actually, due to changes made at dockerHub a couple of months ago, you are entirely on your own All CA does is basically fill out the repository. It is now impossible to fill anything else out automatically by CA, and you have to read the dockerHub / github instructions

The reason why its not a defect and purely a configuration issue is this All apps whether available on the Apps tab or manually set up are the exact same. The only difference between some random container on dockerHub, and something available from Apps is that a template is available. When you hit "Add Container", and manually enter in all that info required to get the app to install via dockerHub, all you are doing is creating a template.

It's installing no problems. No defect. If there's a problem, it's with how you've configured everything on the template / any changes to whatever ini files etc it wants, and you should be able to find documentation on the dockerHub page.

mdcmd spindown x mdcmd spinup x But, simplest way is to simply set drive spindown timers in the drive's settings. That way unRaid will spin down the drives when not accessed.

I think you have a MAC. That ._Pro.key is a metadata file created by it. It is finding your key Apr 13 02:34:02 MediaServer emhttpd: error: get_key_info, 564: Invalid argument (22): get_message: /boot/config/._Pro.key (-3) Apr 13 02:34:02 MediaServer emhttpd: Pro key detected, GUID: 0..1 FILE: /boot/config/Pro.key But I think that your actual problem may be a bug in rc6. (I believe that the fix for the bug even though it was in the OS code prior to rc6 being released, didn't actually make it into the release version somehow) From Update OS, reinstall the "Previous Version" and then reboot and check for updates.

No it's my fault. A piece of experimental code I was working on mistakenly wound up in the release version. Check for updates

Only by running uptime

It's supposed to start then back up if they were running. Sent via telekinesis

Your other option is to do a playlist and ask mymedia to play x playlist Sent via telekinesis

My real complaint though (and it's a general alexa problem) is that you can't include any activity within a task. It sucks not having being able to have Alexa set an alarm and have it play a tune from MyMedia

Works for me. "Ask my media to play the album Dark Side Of The Moon"

IIRC it was something like $5.99 per year for the option that has 3 "friends" That's less than a coffee at Starbucks.

From /var/local/emhttp/var.ini. It's changed on every reboot of the server.

I use it constantly. Only issue i have is i cant get this to work for friends to be able to stream to their alexa. But there are some thread in the project's forum about that but have just never gotten around to investigating further

If you did that in Settings - Docker, it actually won't work without a uninstall / reinstall See this: https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564326

Very strange, as I always install CA on every version of unRaid, and one of the servers is currently running RC7. But either way, glad you got it going.

*should* be fixed next release, if it's coming from where I think it is.

Hit Advanced settings. You can leave any particular container running the entire time

Feb 17 21:50:52 VAULT emhttpd: shcmd (151): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 25 # Share exists on disk1,4 You will get far far better performance by moving the docker.img to the cache drive Set the Share settings for the system share to be Use Cache: Prefer Fastest way to get it onto the cache drive: Then Settings, Docker, Disable the service. Delete the docker.img file, then re-enable the service then Apps, Previous Apps and check everything off. Slower way: Settings, Docker, Disable the service, then Main, Array Operations and run Mover. Whenever its finished you can re-enable the docker service

Not following what you mean by this.

The "parse" error doesn't make a whole lot of sense. Delete "community.applications.plg" from /config/plugins on the flash drive then try rebooting and see if that fixes it. Failing that, Reboot into Safe Mode and see if it will then install and connect. Beyond that, I'd guess that it may be something with your network bonding, but I'm not a network guy

Did you try what was suggested?

Problems with the docker.img. Docker.img full. Problems with the cache drive. Post your diagnostics

Post the diagnostics Sent via telekinesis

Try clicking the link first to open it, then copy it from the URL in the browser bar