July 8, 20232 yr I recently upgraded to 6.12.2, from (I think) 6.5.x. One of my switches had a brief disconnection, and since that point, I haven't been able to access to web GUI from a browser (http://[local ip address]/Main). Other connections like SMB work just fine. And I'm still able to locally access the terminal. Rebooting the server did end up resolving the issue. However, this issue has happened again (switch had an interruption, web GUI stopped working). So this time I went to the machine, logged in to the terminal and ran `diagnostics`. The text cursor went to the next line, and nothing happened. I went to bed, came back the next day, and it's still nothing. I attempted to run `diagnostics` via ssh, and the same behavior is happening. And I did verify there is no new diagnostics file generated. What are the next steps I can use to diagnose this issue? Edited July 9, 20232 yr by Software2
July 9, 20232 yr Author Whoops, I don't know why my brain insisted on putting a 1 in front of the versions. I shall try that and report back. Thanks!
July 9, 20232 yr Author Diagnostics attached Edited July 13, 20232 yr by Software2 Issue resolved, diagnostics did nothing
July 9, 20232 yr Spotted nothing obvious in the diagnostics and it looks like the GUI should be available on 192.168.1.16. have you tried clearing your browser’s cache? Have you tried booting in Safe Mode in case you have a plugin causing problems?
July 9, 20232 yr Author Hmm, well thanks for taking a look. I did try accessing the GUI on multiple computers without success. I've not tried booting into safe mode, since rebooting normally resolves the problem, at least temporarily. Since I have at least noticed this problem when my network switch had a dropout, I'm replacing that component and I'll hope as a side effect this issue can be avoided. Is there any indication of why diagnostics hung previously?
July 9, 20232 yr Author This has happened a third time, and just like before, diagnostics is unresponsive. While the machine is in this state, is there anything I can try to identify what's going on?
July 9, 20232 yr Author Attached Edited July 13, 20232 yr by Software2 Issue resolved, syslog did nothing
July 10, 20232 yr Jul 8 17:43:54 Unraid nginx: 2023/07/08 17:43:54 [alert] 13455#13455: *602 open socket #5 left in connection 14 Jul 8 17:43:54 Unraid nginx: 2023/07/08 17:43:54 [alert] 13455#13455: *594 open socket #28 left in connection 16 Jul 8 17:43:54 Unraid nginx: 2023/07/08 17:43:54 [alert] 13455#13455: *588 open socket #29 left in connection 17 Jul 8 17:43:54 Unraid nginx: 2023/07/08 17:43:54 [alert] 13455#13455: *634 open socket #26 left in connection 18 Jul 8 17:43:54 Unraid nginx: 2023/07/08 17:43:54 [alert] 13455#13455: aborting Jul 8 17:44:06 Unraid nginx: 2023/07/08 17:44:06 [alert] 13880#13880: *658 open socket #6 left in connection 11 Jul 8 17:44:06 Unraid nginx: 2023/07/08 17:44:06 [alert] 13880#13880: *662 open socket #25 left in connection 13 Jul 8 17:44:06 Unraid nginx: 2023/07/08 17:44:06 [alert] 13880#13880: *664 open socket #26 left in connection 14 Jul 8 17:44:06 Unraid nginx: 2023/07/08 17:44:06 [alert] 13880#13880: aborting These start before the boot finishes, try booting in safe model and/or make sure nothing else is trying to access the GUI.
July 13, 20232 yr Author Solution For anyone else that comes across this thread, it's a bug in Unraid that's getting fixed in 6.12.3. For now, the workaround is to disable IPv6.
July 13, 20232 yr Unraid 6.12.3-rc3 is now available which should resolve issues related to IPv6: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6123-rc3-available-r2572/
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.