I have a pretty big problem: I finally scheduled a parity check every month that runs in off hours and is therefore (how I understood it) stretched over multiple days at the start of each month. We have the 4th day of the month right now, so the parity check should be done by now. I didn't access the server-webui since the new month and therefore don't know if my problem has anything to do with the parity check but it's the only thing I changed, so I guess it is.

Like the title said, I am now completely unable to access my servers webui either through a browser or putty ("connection refused"). I run Tailscale but neither the https or the normal adresses work. With a bit of searching on the internet I think the problem could be that the UI sort of crashed or didn't restart properly during one of the parity checks. I want to restart the server now (safely because there's alot of very important files on there) but I can't access the console. Not through the webui because, well I can't access that and not by connecting a keyboard to the server because the server would only recognize that after a restart. So I'm screwed, can you help me? I feel very helpless and I really don't have much skill when it comes to those technical problems.

Thanks in advance!

Edited September 3, 2025Sep 3 by KimiLen

See if you can access the server via the CLI/SSH, if you can get the diagnostics and reboot, if that is also not working, you will need to force a reboot.

2 hours ago, JorgeB said:

See if you can access the server via the CLI/SSH, if you can get the diagnostics and reboot, if that is also not working, you will need to force a reboot.

Unfortunately, as I said in my original post, using Putty (so trying to access the server via SSH or telnet) also got me the error "connection refused". Could be that I've done it wrong in some way and that it's complicated somehow by me using tailscale on the server, but idk.

Do the diagnostics need to be created or are they already there and it's possible that I can download them from a folder right now?

Edited September 4, 2025Sep 4 by KimiLen

If you cannot access the server, you cannot get the diags. Force a reboot and post new diags after that; they may include the previous syslog depending on the version/settings you are using.

59 minutes ago, JorgeB said:

If you cannot access the server, you cannot get the diags. Force a reboot and post new diags after that; they may include the previous syslog depending on the version/settings you are using.

kimiserver-diagnostics-20250904-1324.zipI did forced shutdown and after a restart, I was able to connect to the WebUI again. Here are the diagnostics. I hope it saved the stuff that happened before the forced shutdown. I'm happy that I can access the UI again but am still worried that it might happen again, so I really want to find the error that caused it and fix it

2 minutes ago, KimiLen said:

kimiserver-diagnostics-20250904-1324.zipI did forced shutdown and after a restart, I was able to connect to the WebUI again. Here are the diagnostics. I hope it saved the stuff that happened before the forced shutdown. I'm happy that I can access the UI again but am still worried that it might happen again, so I really want to find the error that caused it and fix it

Okay a few minutes later and now I can't access the servers WebUI again! This time, the error is "Connection timed out". Plus, I can't access the files anymore through the file explorer!

Edited September 4, 2025Sep 4 by KimiLen

7 minutes ago, KimiLen said:

Okay a few minutes later and now I can't access the servers WebUI again! This time, the error is "Connection timed out". Plus, I can't access the files anymore through the file explorer!

I was able to connect to the WebUI again, but can't access the files through the file explorer anymore, the server isn't even found under "network". I stopped the parity check now, that started again instantly after the reboot. I still don't know how the initial problem came to be

Edited September 4, 2025Sep 4 by KimiLen

syslog-previous is not enabled, and if the server is crashing so quickly, it suggests more a hardware issue, but enable the syslog server and post that after the next crash.

Just now, JorgeB said:

syslog-previous is not enabled, and if the server is crashing so quickly, it suggests more a hardware issue, but enable the syslog server and post that after the next crash.

The Server didn't crash, I just forced a shutdown and then rebooted. Since then I was able to connect to the server, then came the "time out" error and without doing anything the webui worked again. But since this one and only reboot, the server isn't available anymore through the file explorer. I have also changed the interval of parity checks now to be not cumulative but take the whole first day of every month. I don't know if this will change anything. Do you have any idea, how this all happened (and how I can connect to the server via file explorer again)?

Edited September 4, 2025Sep 4 by KimiLen

If the server didn't 'crash and you still have access to it, post new diags, if you lost access

6 minutes ago, JorgeB said:

enable the syslog server and post that after the next crash.

or you lose access again.

2 minutes ago, JorgeB said:

If the server didn't 'crash and you still have access to it, post new diags, if you lost access

or you lose access again.

I have access to the webui, not through the file explorer. But here's a new diagnostics file, with syslog server now enabled

kimiserver-diagnostics-20250904-1353.zip

I assume you mean you cannot access the shares over SMB? If yes, post a screenshot from the Shares page.

2 minutes ago, JorgeB said:

I assume you mean you cannot access the shares over SMB? If yes, post a screenshot from the Shares page.

No, the Server isn't even showing up in the file explorer. I had saved the shares and the "TOWER" generally in the left-hand bar, but I can't access it through that and in the "network" section, it's not showing up anymore.

Why did you start another thread? We could have continued here.

Boot in safe mode in case it's a Tailscale issue and retest.

I openend a new thread because the issue was so different to my original issue. What should I test or do to test exactly? The Server is shown as "online" in the tailscale "machines" site

19 minutes ago, KimiLen said:

What should I test or do to test exactly?

Just boot in safe mode.

31 minutes ago, JorgeB said:

Just boot in safe mode.

I did, now I can't access the server again "Connection timed out". And it's not marked as "online" in tailscale

Edited September 4, 2025Sep 4 by KimiLen

I don't see anything logged that explains that; I suspect a config problem with the flash drive, you can try redoing the flash drive, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.

Just now, JorgeB said:

I don't see anything logged that explains that; I suspect a config problem with the flash drive, you can try redoing the flash drive, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.

I can't access the server or the files. I'm screwed again, like at the start of this whole discussion

You just need to shutdown the server (by force if required) and remove the flash drive, then use your desktop to do the flash reset.

I managed to restart the server safely and now have this diagnostics to show for it

kimiserver-diagnostics-20250904-1925.zip

I removed the user and added it again through the webui and then managed to access the shares in the file explorer! The server still is not showing up in the "network" category of the file explorer tho.

Anyway, I still have no clue why the initial problem happened and how I can prevent it in the future

Edited September 4, 2025Sep 4 by KimiLen

See if the server shows up if you stop the array; that is known to happen for some users.

Regarding the initial issue, no idea what it could have been. You can leave the syslog server running and post that if it happens again.

6 minutes ago, JorgeB said:

Regarding the initial issue, no idea what it could have been. You can leave the syslog server running and post that if it happens again.

Could it have something to do with me activating the parity check?

4 hours ago, KimiLen said:

Could it have something to do with me activating the parity check?

Should not be the case unless the parity check triggered a hardware error of some sort.