Mathew R.

Hi All, I apologize in advance if this might have been mentioned before, but after doing several google searches with varying search terms and finding some existing reports, none of the troubleshooting steps I came across resolved the issue I am experiencing. Unraid Version: 6.12.6 Some background, My WireGuard Client (Peer) was not working (connection would be established but I would have no network or internet access - configuration in WireGuard on Unraid is set to Remote Tunneled Access) and so in trying to troubleshoot, I tried deleting the Peer from the VPN Manager Settings in Unraid (among other things). Upon re-creating the Peer in Unraid, I am no longer able to download the Peer Configuration. The eye icon is greyed out. In reading some of the other reports on this issue, there are some instances where WireGuard wasn't deleting the old Peer Configurations from the Flash Drive Config Folder and this was causing some issues. For my situation, the Peer Folder on the Flash Drive is empty even though the VPN Manager in Unraid shows I have a Peer setup. I also tried deleting the Tunnel and peer while monitoring the Config Folder and see the Tunnel configuration gets deleted (there is no Peer data to delete so that folder stays empty), and when I create a new Tunnel, I see those configuration files generated in the Config Folder as well. I'm left scratching my head trying to figure out what's going. Any help is greatly appreciated! Unraid Version: 6.12.6 UPDATE: Resolved It appears the issue manifests if the Peer Name field is left empty. This seems like it is a bug since the default configuration settings indicate the Name Field is Optional. Gonna leave this post in case anyone else encounters the issue too so they can try what worked for me to see if it helps them.

I as well can also confirm this issue has been present for a little while now.

I'm currently dumbfounded... The issue seems to now be specific to FireFox (although I had never thought previously to test with a different browser prior to the 6.9.0 Stable release). e.g., When updating the temp values in FireFox, they appear to save initially, but then revert randomly. In Chrome, when updating the values, almost immediately, you can see a visual difference. The default values are denoted in a blue toned color rather than being a grayish color in FireFox. I stumbled upon this workaround when looking for reports in the stable build threads and someone else had reported that using a different browser worked. Potentially the problem could also be related to cached data/cookies. I don't really know. Just glad that I am not having the issue anymore. Good luck to you all.

Just updated to the 6.9.0 Stable build and I am still unable to get the temp settings to stick. Is anyone else also still experiencing this issue?

Even if I hadn't, a container update shouldn't modify settings values unless it is noted in the change log (which it was not). I definitely stopped the container before making changes to the settings file though. And, I too changed the repository value to use a previously known working version. For others reporting, it'll be valuable to include the version. The issue is appears to be specific to version 3.00-r0-ls73 - the changes included in that version, at a glance, do not appear to be valid (are at conflict with themselves) and the commit comments for testing of the changes are not specific. Which would lead me to believe that the person who made the changes only tested that the changes resolved their issue, and did no negative testing to ensure existing functionality was retained. Either way, the issue is still present and there has been no new build pushed for this container as of yet. Hopefully this matter gets resolved soon.

I too am experiencing the same issue after updating (authentication/password settings will not stay enabled/true).

Interesting..., In my "smart-one.cfg", I can see the correct temperature values for the cache pools I have, but there are no disks specified for each of the temperature value sets (e.g., where it would display the disk model and serial number, it only displays the pool assignment, "cache, cache2, scratch, scratch2).

Thanks for the tip -Deadalus

I just updated to 6.9.0-rc2 and drive temperatures are no longer being displayed. Instead, I get an asterisks symbol where the drive temperature would normally be displayed. As well, I too am still unable to edit the drive temperature values as seen and reported in 6.9.0-rc1.

I too am experiencing issues with being unable to specify the temperature threshold for any of the disks in my array and pools, after updating to 6.9.0-rc1. This becomes a bit more than annoying when NVMe SSDs are involved due to the average temps for those being higher than the default threshold values. So far, it seems that the only workaround is to change the default values at the OS level. Maybe this thread could be escalated from a status of "annoyance" to "minor"? Thoughts?