Unraid 7.3.2 is a security and bugfix release with an updated Linux kernel, a critical WebGUI security fix, Docker VLAN networking improvements, and 70+ updated base packages.

This update is recommended for all users.

Release Docs

Bug Reports here please!

My server is updated... it's working great! 👌

Visiting Settings -> Management Access -> Unraid API Status show:

API Service Status

Status: Not Running (but it is) and log say "Jul 9 01:17:40 Server webGUI: error: /plugins/dynamix.my.servers/include/unraid-api.php - wrong csrf_token"

Pressing "Refresh Status", it shows up as running but revisiting that page gives not running with the wrong csrf_token error.
I really don't want red errors in the logs. I could ignore the wrong csrf_token but why does it happen?

Edited July 10Jul 10 by Niklas

updated from 7.3.1 without any issues.

Updated my Terra-Master 425 Plus from 7.3.1, went fine, Docker apps and plug-ins/apps appear to be working great.

The kernel change section seems incomplete/lacking formatting.

i.e.

From/To versions

Why is the usb auto suspend bit there on the same line,

Hello, The upgrade went well but had issues with the license. It was suddenly blocked and i can't activate anymore. after rollback to 7.3.1 it went good again.

Updated from 7.3.1. to 7.3.2. without issues.

Only one minor point that I have seen just now: a custom icon png file is not displayed anymore for a docker container, which worked before the update.

The file is still present.

I updated without a hitch. Great job!

Everything has been performing well. 🙂

THANK YOU!

Update but with a litte scare.. after the reboot the system hung. After pressing enter to reboot the system rebooted only to bios. Had to switch the usb to a different port to get the boot working again.

1 hour ago, ARGO666 said:

Update but with a litte scare.. after the reboot the system hung. After pressing enter to reboot the system rebooted only to bios. Had to switch the usb to a different port to get the boot working again.

Same issue here! had to change the usb port to boot again

After the update.... going to the ip:port as I normally do to access the dashboard gives me the old "This site can’t be reached" error... BUT I can connect via the servername:port with no problem

I upgraded and then could no longer load my gui on the firefox that I used to update it. Everything was running fine otherwise. I was able to ping my server from the terminal thou. I changed browsers and it worked fine. I restarted firefox and it wouldn't work until I cleared cookies now all seems good.

Upgrade from 7.3.1 initially went fine, was back online for a few hours. Suddenly I noticed the GUI was unreachable, wouldn't respond to pings, and there was no output when hooking up a monitor and keyboard directly to the PC.

Ended up saying screw it and cycled power. Now the the console was accessible and it responded to pings, but was refusing an SSH connection and still no GUI. I didn't try and login from the console because my password is absurdly long.

Took the USB out and reflashed the 7.3.1 backup I took right before using Unraid's USB creator and everything went back to working. Going to run a non-correcting parity check now and see....

First time I've had an issue with upgrading.

Edited July 10Jul 10 by boaconic

The upgrade seemingly ate my Pool Devices' device assignments (a dual BTRFS SSD cache pool, a four HDD RaidZ, and a HDD for music streaming). Reverting to 7.3.1 didn't help. Luckily everything was intact and just assigning them back sufficed. Most scary for a non-poweruser (I had to recourse to ChatGPT, which is something I hate if I don't know enough to catch any glaringly bad advice).

I keep backups of the boot USB drive and appdata. I'll try to see what could have happened: I don't have anything out of the ordinary, apps and plugins-wise, but maybe there was some weird interaction there.

9 minutes ago, MetricTonto said:

The upgrade seemingly ate my Pool Devices' device assignments (a dual BTRFS SSD cache pool, a four HDD RaidZ, and a HDD for music streaming). Reverting to 7.3.1 didn't help.

That suggests it wasn't the upgrade, possibly a boot device issue. If you saved the diagnostics after the first boot, please create a new thread in the general support forum.

1 hour ago, JorgeB said:

That suggests it wasn't the upgrade, possibly a boot device issue. If you saved the diagnostics after the first boot, please create a new thread in the general support forum.

Thank you: I've started the thread here: https://forums.unraid.net/topic/199814-loss-of-pool-devices-device-assignments-after-update-to-732-if-possibly-unrelated/

14 hours ago, Coop said:

After the update.... going to the ip:port as I normally do to access the dashboard gives me the old "This site can’t be reached" error... BUT I can connect via the servername:port with no problem

Same situation for me. Even after deleting cookies no access using http://IP:port (also from outside using Proxy Manager)

Solution:
Ok, i've found the point...
In the config of 'Management Access' in 'Settings' there is one field "Local TLD" showing 'local'. After deleting this i can use http://IP:port again for GUI Access.

Edited July 10Jul 10 by bluebean

Got luck when updating from 7.3.1. For me the update didn't generate any problems on my TS-253d with ten dockers and 3 Linux VM's.

On 7/10/2026 at 12:14 PM, boaconic said:

Upgrade from 7.3.1 initially went fine, was back online for a few hours. Suddenly I noticed the GUI was unreachable, wouldn't respond to pings, and there was no output when hooking up a monitor and keyboard directly to the PC.

Ended up saying screw it and cycled power. Now the the console was accessible and it responded to pings, but was refusing an SSH connection and still no GUI. I didn't try and login from the console because my password is absurdly long.

Took the USB out and reflashed the 7.3.1 backup I took right before using Unraid's USB creator and everything went back to working. Going to run a non-correcting parity check now and see....

First time I've had an issue with upgrading.

Hey crew,
@boaconic , @limetech FYI

upgraded all 3x of my servers, so far running smoothly except for an issue on my oldest/original config.
I was having the same issue - couldn't connect via SSH, so jumped into the web based terminal.

Long story short after some troubleshooting, could see that SSHD was crashing on startup because the daemon was complaining about this option in my sshd_config file: GSSAPIAuthentication
Seems it is an old / deprecated option - even though in the config file it was set to disabled, the binary seems to choke on the fact that the entry is in the config file.

Fix was to edit /boot/config/ssh/sshd and comment out the offending line: (was line 76 for me but might be different for others)
#GSSAPIAuthentication no

Wasn't something I had to do with my newer machines - I'd set them up years after the first one.

In case it's useful for anyone else in future
/usr/sbin/sshd -t
from the web terminal to get a more detailed error than the SSH rc.sshd start-up script gives

HTH, thanks for all the great work over the years 🙏
Del

On 7/9/2026 at 1:19 AM, Niklas said:

Visiting Settings -> Management Access -> Unraid API Status show:

API Service Status

Status: Not Running (but it is) and log say "Jul 9 01:17:40 Server webGUI: error: /plugins/dynamix.my.servers/include/unraid-api.php - wrong csrf_token"

Pressing "Refresh Status", it shows up as running but revisiting that page gives not running with the wrong csrf_token error.
I really don't want red errors in the logs. I could ignore the wrong csrf_token but why does it happen?

I have exactly the same problem here, and I'm pretty sure it started with version 7.3.x.

Edited July 11Jul 11 by unRaiderX

EDIT:
I found that this issue only occurs when using Google Chrome, Brave, or Microsoft Edge.

When I use Firefox, the error does not appear, and the API Service Status shows Running.

7 hours ago, unRaiderX said:

EDIT:
I found that this issue only occurs when using Google Chrome, Brave, or Microsoft Edge.

When I use Firefox, the error does not appear, and the API Service Status shows Running.

Yes. It has been reported before to occur in mainly Chromium based browsers. I use Brave Origin with Shield disabled for Unraid.

Edited July 11Jul 11 by Niklas

Hi Unraid Support Team,

I am stuck in an endless update loop trying to upgrade from v7.3.1 to v7.3.2. I have already gone through the entire process 6 times, and it always behaves as follows:

1. The web GUI shows the update to v7.3.2 is available.

2. I trigger the update. It downloads, extracts, and validates all sha256 checks perfectly ("Update successful - PLEASE REBOOT YOUR SERVER").

3. I reboot the server.

4. After the reboot, the system is still on v7.3.1, but instead of just showing a pending reboot, the entire update process starts from scratch. The web GUI acts as if nothing happened and offers the v7.3.2 download all over again.

My system configuration:

• OS Boot: Running Unraid 7 with TPM enabled.

• Pools: Main system pools are ZFS Mirror SSD setup.

It seems like the changes made to the boot directory during the update process are completely lost or discarded upon reboot, preventing the system from ever applying the new version.

I have attached screenshots of the successful installation log and the dashboard status.

Best regards,

Guybrush Threepwood from Monkey Island :-)

Edited July 12Jul 12 by guybrush2012

2 hours ago, guybrush2012 said:

I am stuck in an endless update loop trying to upgrade from v7.3.1 to v7.3.2. I have already gone through the entire process 6 times, and it always behaves as follows:

Please start a new thread in the general support forum and post the diagnostics after upgrading and before rebooting.