Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unraid 6.12.2

Featured Replies

Web GUI becomes unresponsive within 1 hours of a reboot. All Dockers and VMS continue to run but unable to log into unRAID web GUI. 

 

Solved by JorgeB

  • Author

Are you asking for the sys log or something else?

 

Rig details 

Intel Core i7-12700K

ASUS ROG Strix Z690-G Gaming WiFi

CORSAIR Vengeance 64GB (2 x 32GB) RAM DDR5 5200

5 - Seagate IronWolf Pro 12TB

SAMSUNG 980 PRO M.2 2TB (cache drive)

SAMSUNG 970 EVO PLUS m.2 250GB (VM drive)

MSI 2070 super (VM GPU)

 

 

 

1 hour ago, T_Matz said:

something else?

 The diagnostics grabbed via the command line  (Use SSH or the local attached keyboard / monitor)

  • Author

Ive tried multiple times, when the WEBGUI stops responding I am able to SSH into my UNRAID server but when I enter the diagnostics command it never completes. It just sits there blinking. under the command. If I reboot the machine i am able to log into the WEBGUI and also SSH into the UNRAID server the diagnostics will complete.

 

with UNRAID 6.11.5 did not give me these issues

 

  • Author

Bump

  • Community Expert
  • Solution

Try changing to IPv4 only.

  • Author

I changed it to ipv4 only. The GUI has been good now for an hour. I will update if it becomes unresponsive again

Came here because I've been having a similar issue, but mines been going since about 6.11.5. I will try the ipv4 step and see what happens. Thank you!

Since upgrading to 6.12.x I have had a problem where after a day or two, the gui becomes unresponsive.  Will not even time out, browser just keeps acting like it is trying to open the gui page.  I just moved to IPv4 only to see if this helps, but that doesn't seem like a solve.  Looking for any pointers you may have.

Edited by Merk

On 7/5/2023 at 2:33 PM, DirtyDarrell said:

Came here because I've been having a similar issue, but mines been going since about 6.11.5. I will try the ipv4 step and see what happens. Thank you!

Came back because I'm already set to ipv4 only as well. Also following for any advice

I encounter an issue similar to the post. The host (6.12.2) GUI became unresponsive but all my docker services (except binhex-qbittorrentvpn) and VM were still functioning normal. After SSH in and kill the qbittorrent container process, the host GUI became available again. There are some error events logged in the syslog.

 

Jul  9 01:58:04 Gandor kernel: CPU: 1 PID: 10534 Comm: qbittorrent-nox Tainted: P           O       6.1.36-Unraid #1
Jul  9 01:58:04 Gandor kernel: Call Trace:

 

I tried switching over to hotio's qbittorrent-vpn docker, but I also saw related error to "qbittorrent-nox segfault" when stop/restart the container. I am not sure if these are related or not.

 

Update: I switched over to hotio's qbittorrent-vpn "legacy" version, which uses libtorrent 1.2.x. So far has not see the segfault error message. I will keep this setup for the next 2 weeks or so and report back any findings. I think my issue is related to this.

 

gandor-diagnostics-20230709-1925.zip

Edited by jfoxwu

  • Author

Switching to just ipv4 fixed my issue

On 7/6/2023 at 8:19 AM, Merk said:

Since upgrading to 6.12.x I have had a problem where after a day or two, the gui becomes unresponsive.  Will not even time out, browser just keeps acting like it is trying to open the gui page.  I just moved to IPv4 only to see if this helps, but that doesn't seem like a solve.  Looking for any pointers you may have.

It has been a week since moving to IPv4 only and I still haven't experienced the problem with the gui.  So i believe this work-around solved the original problem.  Good thing I don't need IPv6 right now.

Edited by Merk

  • Author
2 hours ago, Merk said:

It has been a week since moving to IPv4 only and I still haven't experienced the problem with the gui.  So i believe this work-around solved the original problem.  Good thing I don't need IPv6 right now.

I haven't had any issues either since switching to IPv4. It does suck not having IPv6 capabilities 

Did anymore try the 6.12.3rc3 with the ipv6 fixes?

Just updated to Version 6.12.3 2023-07-14.  Changed back to IPv4 + IPv6.  If it makes it a week, I'll consider it solved.

On 7/15/2023 at 9:32 AM, Merk said:

Just updated to Version 6.12.3 2023-07-14.  Changed back to IPv4 + IPv6.  If it makes it a week, I'll consider it solved.

It is now 6 days later, GUI back to being un-responsive.  I will need to switch IPv6 off again. 

  • 2 weeks later...

10 days in from turning IPv6 off and no issues.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.