On 12/19/2025 at 1:32 AM, 8GDWLbk9HRKtlJJvaiFG said:

Is there any detail anywhere about this? I was hoping it would fix the "The backup disk image could not be created." error on MacOS Tahoe, but I'm getting the same error even after the upgrade.

Yes there is:

1. https://www.samba.org/samba/history/samba-4.23.4.html

2. https://bugzilla.samba.org/show_bug.cgi?id=15926

Upgraded using Brave browser. No Issues. Keep up the great work!

Merry Christmas

Upgraded from 7.1.4 -> 7.2.3.

Everything worked great! Runs with surprisingly less CPU%. Perfect! Thank you very much for your work!!

Merry Christmas.

Does this one fix all the weird UI bugs? Just confirming before I jump in 😀

25 minutes ago, marmot74 said:

Does this one fix all the weird UI bugs? Just confirming before I jump in 😀

What weird UI bugs are you referring to? I haven't had any with this or previous versions. And I don't see any posts from your history describing any.

On 12/18/2025 at 3:58 PM, ljm42 said:

Unraid 7.2.2 had over 95,000 installs in about four weeks!

Out of Curiosity, how many uninstalls?

On 12/25/2025 at 11:22 AM, trurl said:

What weird UI bugs are you referring to? I haven't had any with this or previous versions. And I don't see any posts from your history describing any.

The white background banner situation that's mentioned a lot in the previous few releases.

I have a pool disk that I use for my downloads pool that went down and to start the array I can't just check "Yes, I want to do this" anymore... I would have to erase that pool to use the main array and re-create it later when I get a new drive.

22 minutes ago, MonadProxy said:

I would have to erase that pool to use the main array and re-create it later when I get a new drive.

If the pool is a single device, this is expected, and it's not the erase button you would need to use; it's the "remove". In case of a multi-device pool, it means it's not being detected as redundant. If it's the latter, please create a new post in the general support forum and post the diagnostics

52 minutes ago, JorgeB said:

If the pool is a single device, this is expected, and it's not the erase button you would need to use; it's the "remove". In case of a multi-device pool, it means it's not being detected as redundant. If it's the latter, please create a new post in the general support forum and post the diagnostics

Mhh curiously enough I was not asked for this before upgrading to 7.2.3 (I was on 7.2) and yes you are right I used the wrong term it is remove and not erase. That being said since that was a single drive pool that I use for scratch and the drive died, I just removed it until the replacement arrives so no worries here.

Upgraded from 7.0.1 to 7.2.3 without problems

Upgraded both my servers from 7.1.4 to 7.2.3. As others have reported I also noticed a lower CPU % with 7.2.3 (nice benefit). Everything went smooth and everything appears to work but now I get these errors is my syslog for both servers.

[WARNING] [pool www] server reached max_children setting (50), consider raising it.

It seems to happen most when first logging into the GUI and doing anything GUI related, if I am not logged in the errors do not occur in the syslog. I will create a separate post with the diags.

9 hours ago, SShadow said:

[WARNING] [pool www] server reached max_children setting (50), consider raising it.

It seems to happen most when first logging into the GUI and doing anything GUI related, if I am not logged in the errors do not occur in the syslog. I will create a separate post with the diags.

I'm not getting that warning anymore. Don't know what changed but I like it. ;)
I do have Unraid Connect plugin installed.

Edit: Jinxed it...
Jan 4 04:26:20 Server php-fpm[9243]: [WARNING] [pool www] server reached max_children setting (50), consider raising it

Edited January 4Jan 4 by Niklas

the message means, you have too many open (GUI) sessions.

Use fewer clients, or consider to log off before you close the browser tab.

This can happen easily if you run the browser in private mode (or set the setting to delete everything on closing the window). UNRAID still has the session open then and they add up and up and up...

So its more a sign that you are doing something wrong instead of beeing a bug in UNRAID (if you raise the limit it will still happen, just later)

3 hours ago, MAM59 said:

the message means, you have too many open (GUI) sessions.

Use fewer clients, or consider to log off before you close the browser tab.

This can happen easily if you run the browser in private mode (or set the setting to delete everything on closing the window). UNRAID still has the session open then and they add up and up and up...

So its more a sign that you are doing something wrong instead of beeing a bug in UNRAID (if you raise the limit it will still happen, just later)

Session time-out after xx minutes, hours, or days of inactivity has to be invented. But then the user can't do it wrong.

Edited January 4Jan 4 by b52
more clarity

4 hours ago, MAM59 said:

the message means, you have too many open (GUI) sessions.

Use fewer clients, or consider to log off before you close the browser tab.

This can happen easily if you run the browser in private mode (or set the setting to delete everything on closing the window). UNRAID still has the session open then and they add up and up and up...

So its more a sign that you are doing something wrong instead of beeing a bug in UNRAID (if you raise the limit it will still happen, just later)

The user is doing something wrong when we get warnings in syslog? Nah.

This just started to happen very frequently compared to before. I have the same use pattern since years. Something has changed. I use one session at a time as usual. Then sure, you could open two tabs in some cases when needed (like copying data between templates etc) but it should absolutely be able to handle that. I don't buy the "You're holding it wrong"-thing. 😉

Edited January 4Jan 4 by Niklas

2 hours ago, Niklas said:

I use one session at a time as usual. Then sure, you could open two tabs in some cases when needed (like copying data between templates etc) but it should absolutely be able to handle that. I don't buy the "You're holding it wrong"-thing.

Better you do 😉

The thing is, how you leave the session.

UNRAID has no session timeout, so if you just close the window of/in the browser, it remains open.

And then it depends on your browser's settings, if you have set them strict and paranoid, the browser "forgets" everything once he is reopened someday. So a "new" session is started on UNRAID (making them TWO running ones).

And if this happens over and over again, you finally reach the configured limit of 50 and the warning starts to begin.

If you restart unraid (or at least the NGINX Server for the GUI) all old sessions will be erased from memory too and the count begins again with "1".

If the browser is configured to remember the old session, it is picked up again and just resumed, no new session is created.

But again, it is a local setting in your browser.

Should I be okay to jump all the way from 7.0.0 to this latest 7.2.3? I've never jumped so many releases at once before. Are there any specific precautions I should take?

1 minute ago, SPOautos said:

Should I be okay to jump all the way from 7.0.0 to this latest 7.2.3?

Yes, create a flash drive backup before updating, and I recommend reading the release notes for 7.1.0 and 7.2.0

8 minutes ago, SPOautos said:

Are there any specific precautions I should take?

Make sure all your plugins are updated.

1 hour ago, JorgeB said:

Yes, create a flash drive backup before updating, and I recommend reading the release notes for 7.1.0 and 7.2.0

54 minutes ago, trurl said:

Make sure all your plugins are updated.

@JorgeB @trurl Thank You both, did the update, its been up and running for several minutes now and everything seems to be working fine! I always get nervous about updates because I'm not knowledgeable enough to fix real issues hahaha

Thanks team - Upgraded my 2gb usb stick to a Swissbit 16GB stick easily & then updated to 7.2.3
Smooth like butter on pancakes. 🥞🍻

Edited January 12Jan 12 by dopeytree

I just updated from 7.1.2 to 7.2.3 and for some reason the Docker page no longer appears tabbed. Other pages dont seem to have changed.

Edited January 12Jan 12 by primeval_god

56 minutes ago, primeval_god said:

Docker page no longer appears tabbed

I've never seen tabs on the Docker Containers page, and don't know why you would want them. I only use the Black or the White theme on my servers though, which you apparently aren't. Are you sure there isn't some plugin involved?

35 minutes ago, trurl said:

I've never seen tabs on the Docker Containers page, and don't know why you would want them. I only use the Black or the White theme on my server though, which you apparently aren't. Are you sure there isn't some plugin involved?

Yes the tabs are there when the compose plugin is installed (of which i am the maintainer). The layout however has never changed across updates before, and doesnt seem to have effected any other tabbed page on the system. Its also as far as i am aware not specific to the theme but a function of the "Page view" settings (Tabbed vs Non-tabbed).