Hi everyone!

 

Currently running unRaid 6.6.7 and I'm having a blast! About a month into using the software and just purchased my license key for basic :)

 

I'm having an issue where I select the "Gray" theme in Display Settings and everything looks fine for a few minutes, then eventually the system will auto-convert the theme back to Black.

 

I've tried deleting my cache in Chrome, as well as changing the default-black and dynamix-black files in /usr/local/emhttp/plugins/dynamix/styles to .BAK to remove the theme from the options, but doing this breaks the unRaid GUI overall as shown in my attached screenshot. 

 

I've tried researching the issue myself, but I was unable to find any other threads/posts with people experiencing the same problem :( 

 

Please let me know if anyone has any suggestions or wants some specific logs! (I'm not sure what logs would be applicable here besides the error messages when it tries to load the Black theme I renamed) 

Apr 12 13:30:21 wecanstream nginx: 2019/04/12 13:30:21 [error] 28135#28135: *197674 open() "/usr/local/emhttp/webGui/styles/default-black.css" failed (2: No such file or directory), client: [redacted], server: , request: "GET /webGui/styles/default-black.css?v= HTTP/1.1", host: "wecanstream", referrer: "http://wecanstream/Main"
Apr 12 13:30:21 wecanstream nginx: 2019/04/12 13:30:21 [error] 28135#28135: *197594 open() "/usr/local/emhttp/webGui/styles/dynamix-black.css" failed (2: No such file or directory), client: [redacted], server: , request: "GET /webGui/styles/dynamix-black.css?v= HTTP/1.1", host: "wecanstream", referrer: "http://wecanstream/Main"

 

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

 

8 minutes ago, rahmor said:

in /usr/local/emhttp/plugins/dynamix/styles

Like most of the Unraid OS, this folder is in RAM, so any edits there won't survive reboot anyway.

 

If you have an adblocker, whitelist your server. You might also try a different browser to see if it makes a difference.

Hi trurl & thanks for the suggestions!

 

Attached you can find the complete diagnostics zip.

 

I currently use uBlock Origin and have already whitelisted my server, and the issue also persists in Internet Explorer. I will give Firefox a try as soon as I can!

wecanstream-diagnostics-20190412-1400.zip

Why do you have an SSD in the array? Since you don't currently have parity I guess it doesn't matter but not something you will want if you ever plan to use Unraid as a NAS.

 

My best guess is a problem with flash. Put it in your PC and let it checkdisk. While there make a backup.

I have an SSD in the array because currently all my media is stored on an external NAS. These two drives were the only spare ones I have until I can get some more 10TB WD's that go on sale.

 

I ran a chkdsk on the flash drive (results attached) but it did not find any errors. 

 

If the flashdrive is an issue, how difficult would it be to migrate the configuration and license to a new one being that I just purchased the license? I remember reading that you get 1 change a year, is that valid right from the purchase date? Haha. 

 

I'm assuming the configuration is as easy as copying over the unRAID files I backed up from the flash drive just now to the new one? 

 

Thank you again for your assistance with this

Are you using a USB2 port for your flash on your server? USB3 is sometimes not as reliable. You can always take the config folder backup from flash and put it on a new install and you will be good to go.

 

But we don't really know if that is the problem. Have you tried it again to see if the problem is still there?

I agree with @trurl that the symptoms suggest a possible problem writing to the USB stick so that your configuration changes are not getting saved although I did not spot anything in the diagnostics to confirm that.

 

As well as trying the recommendation of using a USB2 port (if you have one), have you tried booting in Safe Mode (which stops all plugins loading)  to see if the problem still occurs?   Doing so would at least rule out whether or not a plugin is the cause of your problem.