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.

Yes, the proxy.conf was enabled by the mod it appears and it is stock at the moment.

I'm trying to get the Swag Dashboard working. I have the Swag docker port configured to 81 and 443 respectively and it has been working fine my other subdomains. However, after enabling the dashboard mod, configuring an A record for 'dashboard.domain.com' to point to my server IP that Swag is listening on, I get a nginx 504 time out error when trying to go to https://dashboard.mydomain.com . I'm coming from an internal LAN subnet that is within the allowed IP ranges stated in the domain.subdomain.conf file as well. The Swag docker logs are not reporting any issues either. Any ideas on what I may be missing or doing wrong?

I was able to resolve the 'socket failed to connect' error while using Swag/nginx using a proxy-conf file like this below. I was not successful when trying to use a site-conf server { listen 443 ssl; listen [::]:443 ssl; server_name <YOURSUBDOMAIN>.*; include /config/nginx/ssl.conf; add_header X-Frame-Options "SAMEORIGIN" always; add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; add_header X-Content-Type-Options "nosniff" always; client_max_body_size 0; location / { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app <IPADDRESS>; set $upstream_port 13378; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_hide_header X-Frame-Options; proxy_max_temp_file_size 2048m; } }

I had a similar issue with the Ghost docker. Creating the appdata folder in advance with the elevated rights noted above moved me forward. But I also had to create the MariaDB user manually as 'username'@'172.17.0.1'. Thank you!

For any of my peers banging their head against the wall with this error during install: "nextcloud MySQL username and/or password not valid" , following these steps resolved the issue for me: https://www.thesmarthomebook.com/2022/12/03/unraid-set-up-nextcloud-with-mariadb/

I was not able to resolve this until I uninstalled and stopped all the following: Dynamix fan plugin Telagraf Varkin InfluxDB HDDTemp

Greetings Ya'll, I just upgraded from 6.8.3 and all went smooth with no issues so far. I also got my nvidia card working again with the new plugin. Thank you!

Just upgraded from 6.8.2 to 6.9.1 and reinstalled this plugin with my nvidia GTX 1060 and all is working fine again. Thank you.

Hey Y'all! I just stumbled upon this.... I'm going to test out the Zabbix agent on my unraid. But can anyone share if they had any issues with it or their review of it?

Anybody have any eventual ssd failures shortly after this warning? If so, what was your make and model of the drive?