severanced

This has been a nightmare, isn't there just an option to NOT use SSL? Everything is internal I don't need an SSL link and nothing I do works.

So, it's strange, but after I powered it up after a commandline "powerdown" shut down if I go to the hostname i get an NGINX error but going to the IP address I get the gui for now. Usually this only lasts a day or so before it starts to fail.

I hope someone can help me, for the past couple of weeks my server has been having issues where the webGui either crashes with an NGIX error or just doesn't come up at all, the shares and apps seem to be available and I'm able to SSH to the server but I can't bring anything up in the web. One time I was able to bring it back with restarting PHP but the latest one I couldn't bring it back at all. I hope the diagnostics can help bring some light to it. diagnostics-20250602-0913.zip

Thank you @trurl I had to remove the network.cfg file and I had to remove the reservation from my router and then the system started up with an IP, looks like something was jacked there that only came to light now.

@trurl How do I get diagnostics out of the server when I can't reach it?

Hello, I hope you can help, I just updated my server to 7.0.1 and now the system doesn't start up properly. I get the error "Error (ERR_MODULE_NOT_FOUND): Cannot find package 'execa' imported from /usr/local/unraid-api-/dist/cli.js Anyone know how I can solve this? I do get a login in the CLI but no web page.

So I managed to fix the issue by switching the vDisk from VirtIO to SATA and somehow that brought it back up

And just for reference I get a generic "No Bootable Device" error when trying to start the VM even when the disk seems to be connected.

After some updates to my VMs and upgrading to 7.0.0 it seems I'm not able to launch my VMs any more. I get an error even though I can see the disk in my file system and it's selected in the properties. The primary disk location is set as "Manual" but when I change it to Auto or Cache it seems to update forever and never stick. Is there something I can do to get my VMs to launch again? I'm including some diagnostics even though I'm not sure if they're relevant. I did apply the most recent patch 1.0.0 and rebooted. diagnostics-20250217-1913.zip

Thank you, that looks like that fixed it, I went and updated a bunch of shares that were also set incorrectly from the upgrade

I did all of that, things are looking a bit better, but the mover still seems to not be moving things. I enabled the logging and started the mover. As an example one share I expected to be moved is called "Cloud" diagnostics-20250217-1323.zip

Hey everyone, I hope you can help, I was getting notifications that my cache was getting full so I tried to run the mover manually and in the logs it just shows : Feb 17 09:17:21 emhttpd: shcmd (1576155): /usr/local/sbin/mover start &> /dev/null & I'm getting some errors about the [Appdatabackup] and when I check the Fix Common Problems I see it says "Unable to write to Docker Image" - Docker Image either full or corrupted, I hope you can help. This is 7.0.0 diagnostics-20250217-0922.zip

I've been having issues with my Unraid server for a while now. Every couple of weeks or so it'll suddenly become unresponsive and I'll have to do a hard shutdown. I tried doing some syslog checking and created another issue for that here: Unfortunately it looks like the syslogs didn't have anything useful. I randomly checked the monitor on my server and while my server is still responsive I noticed a "metadata corruption" error on the screen. I've included it in the attachments. Any idea what this might be about, if it might be causing the hard stops and how I might fix it?

Thanks, I've been buying parts to build a new server, motherboard, memory Etc. My concern with these crashes was that I was going to be taking a piece of hardware that was causing the crash to the new server.

Hi, My server had a hard crash again and I had to do a hard shutdown. I was able to pull some syslogs and some diagnostics, I hope these will point to something that might be causing the crash. syslog-10.1.1.29.log crusherjoe-diagnostics-20231010-2357.zip