guruleenyc

Upgraded from 6.12.6 and all went smooth, no issues to report so far 🙂

This issue hit me yesterday after two months of uptime while on 6.12.6. Thank you for the quick fix to get the array stopped and restarted without needing to reboot. Sent from my SM-N986U using Tapatalk

Offer valid on SKU WD201KFGX bought online through the Western Digital Store. Sales quantities are limited to a maximum of 6 units (3 bundles) per customer. Offer is only valid while supplies last. This promotion is valid between January 22, 2024 and February 4, 2024. https://www.westerndigital.com/products/internal-drives/wd-red-pro-sata-hdd?sku=WD201KFGX Sent from my SM-N986U using Tapatalk

I encountered the issue too with one docker in a started state not being accessible by its webUI. I tried killing it in this manner by PID, but it was not clear what integer was the PID in the grep output. However, I was not able to cleanly stop or restart the docker. I ultimately had to stop all other containers, stop the array (which hung), and eventually had to reboot unraid softly to resolve the issue with one docker. All my other dockers were healthy. I'm on unraid 6.1.2.6

Unraid Mgmt interface / webui should support MFA in this day and age even-though it should NEVER be exposed to the Internet.

THANK YOU!

Greetings friends! Since plugins will not update unless we're on 6.12.x (e.g. Community Apps), I was forced to upgrade unRAID to bleeding-edge which is not how I typically upgrade in general. I am relieved to share that I successfully upgraded from 6.11.5 to 6.12.6. The only issue so far is my Swag docker is not starting, it returns Execution 'server error' popup. There as also a pending Swag docker update I then completed successfully... However, it still does not start with same above error. UPDATE: I had to go into Settings > Management Access and change the HTTPS port from 443 to 4434, even though 'use SSL/TLS' for webGUI was ahready set to 'NO'. When I applied the change, it still tried to redirect me to the webGUI on 4434 w/TLS for some odd reason... I had to force my browser to use HTTP/non-TLS to get back to webGUI. Swag docker starts fine now. [emoji41][emoji106][emoji6]

Same feelings here! 👍

So smart and a great reminder. Thank you

Thank you sharing this guide and example. I found it very helpful. However, for one of my lab Cisco switches (SG300-10), channel-group modes were only Auto (w/LACP) or On without LACP. So far it has been stable in Auto mode.

Anyone using Plexcache script and if so, please share experience? https://github.com/bexem/PlexCache

This also resolve the issue for me. I was already on 25.x and I had to upgrade to 27.x via console CLI of docker and then reverting the repo tag afterwards to finally get back in to GUI. THANK YOU! I also set my docker repo to 'lscr.io/linuxserver/nextcloud:version-27.0.0' to prevent this from happening again and have a controlled upgrade in the future.

This Update All dockers is also looping for me as well on 6.11.5. It removed some of my dockers on the second pass. I stopped it by stopping the array.

I love the idea of features of this plugin, but will it every come out of Beta (badged in app store)?

Thank you! This solved my issue. I guess the variables for the other docker fork were not universal.