StanC

I did upgrade to 7.1.2 a few days after the release. Thanks.

Just thought that I would post this. My unRAID USB Flash Drive died this morning on COLOSSUS which was running version 7.0.1. It was a 32GB Samsung USB 3.1 Flash Bar. It ran great for a couple of years, no complaints. The process for replacement was very easy to follow. Just go to unRAID Connect and download the flash backup, use the USB Creator Tool and install the backup file to a new flash drive. This time I chose a 32GB Sandisk Cruzer drive that I used for a previous build. Reset the boot option in BIOS and I was backup and online in no time. I just had to go through and set the root password, register to the new flash drive, and then reset user account passwords. At the same time I upgraded to 7.1.1. Life is great again!!! Thanks goes out the unRAID Team for making running unRAID enjoyable.

Same with a Asrock X670E Taichi + 7950x I get no sensor detected when I run sensors-detect from the shell. I was able to manually configure the drivers.conf file for the Dynamic System Temp plugin and placed k10temp and nct6775 in it. But only k10temp, nvme, and amdgpu sensors show in the dropdown list. According to the manual (page 11) it shows that they are using chips NCT6796D-S and NCT6686D. Are these supported by nct6775? If I try to run "modprobe nct6775" from the shell I get "modprobe: ERROR: could not insert 'nct6775': no such device"

@SpaceInvaderOne I am seeing the same issue. I am running unRAID 6.9.2 and not able to dump a vbios for my GTX-1080, either as primary or secondary gpu . I was able to dump the vbios of my RX580 as secondary GPU, then swap the cards to dump the 1080, but I get the same error. I have tried the vfio setting as suggested in the script but that did not work either.

@ljm42 I have finally got it working 😀 I did end up recreating the thumb drive after exporting my license key. I wanted to start with a clean build. Since this is my VM Workstation Build (in my signature). Also I wanted to change out a NVMe drive and move the thumb drive to an internal USB 2.0 port, all my external ports are 3.x. I swap out a WDC Black NVMe 1TB with a Sabrent Rocker 4+ 1TB, the WDC was running at 50 degrees which kept sending alerts. The Sabrent runs at around 36 degrees. After swapping out components and went about getting it configured and then went to provision it again. I got a the DNS Rebinding Error message - different but making progress. I am using OPNsense as my router, so I needed to add the necessary Host Override in Unbound DNS service. After that I was able to get the certificate 👍 So now I am good to go. Thanks again.

@ljm42 I am not apposed to this, since this is a brand new build with nothing on it. But would it help if I restart with a clean build (fresh copy of unRAID OS, new server name, etc.)? Or is it that my email address is being blocked by LetsEncrypt?

Currently waiting on a resolution in the thread below. Apparently my SSL Cert requests has been borked and waiting to see if the team can get it resolved.

@ljm42 Is there anything else I can try to resolve this?

@ljm42 - still getting the same error

@ljm42 Making some progress. Performed a rollback to verison 6.9.2. Hard coded Cloudflare DNS servers into the Network settings, disabled my OPNsense Firewall rule DENY External DNS. Rebooted the unRAID server and now receiving the following: Not too sure what this is telling me.

Same results. I have even uninstalled the plugin, rebooted the server, and reinstalled the plugin. So for now, I have completed removed the plugin from all of my servers, since it does not work. Also noting that the addition of the QR Code is nice, but in the IOS app I did not see an option to scan a QR Code. The only options are Discovery or Manual when adding a server. I have also remove the app from my iPhone and iPad.

Does this plugin work when a server is configured under Management Access to us ####.unraid.net? Currently I have two server configured as such and I am not able to configure or access them. When I click on the link on the plugin settings to bring up the QR Code it fails "cannot access this site". I look at the URL and it is using https with port 2379, if I change the url to http and port 2378 then the page comes up. If I remove the Management Access settings (unprovision the server from *.unraid.net) then the plugin works just fine. So maybe there is a something going on that is preventing this plugin from working on *.unraid.net.

Did some further testing by swapping out the flash drive, since for this build I was still using the trial key. Still got the same issue. I updated to 6.10.0-rc2 and then tried again, still the same issue. But the system log revealed something with 6.10 that did not exist in 6.9. Below is the excerpt from the log: Nov 24 09:09:17 PRIME emhttpd: shcmd (114): /usr/bin/php -f /usr/local/emhttp/webGui/include/ProvisionCert.php Nov 24 09:09:17 PRIME root: Error: Server was unable to provision SSL certificate Nov 24 09:09:17 PRIME emhttpd: shcmd (114): exit status: 1 Nov 24 09:09:17 PRIME emhttpd: shcmd (115): /etc/rc.d/rc.nginx reload Nov 24 09:09:17 PRIME root: Checking configuration for correct syntax and Nov 24 09:09:17 PRIME root: then trying to open files referenced in configuration... Nov 24 09:09:17 PRIME root: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok Nov 24 09:09:17 PRIME root: nginx: configuration file /etc/nginx/nginx.conf test is successful Nov 24 09:09:17 PRIME root: Reloading Nginx configuration... Nov 24 09:09:20 PRIME nginx: 2021/11/24 09:09:20 [alert] 2269#2269: *9524 open socket #26 left in connection 8 Nov 24 09:09:20 PRIME nginx: 2021/11/24 09:09:20 [alert] 2269#2269: *9522 open socket #18 left in connection 10 Nov 24 09:09:20 PRIME nginx: 2021/11/24 09:09:20 [alert] 2269#2269: *9512 open socket #13 left in connection 16 Nov 24 09:09:20 PRIME nginx: 2021/11/24 09:09:20 [alert] 2269#2269: aborting The second line says it was not able to provision the cert. Do not know if this is a bug or if the unRAID provision site (https://keys.lime-technology.com/account/ssl/provisioncert) has an issue. Got the site URL from looking through the php file from the first line in the log excerpt above. Should this be reported as a bug?

I am also seeing this same issue on a brand new build of 6.9.2.

Has this been resolved? I am getting the same thing a brand new build 6.9.2.