Stable Releases

The bottom of preclear status report has a typo of genereated rather then generated   #################################################################################################### # Unraid Server Preclear of disk ZXA12345 # # Cycle 1 of 1, partition start on sector 64. # # # .... #

It is not possible to login when booting Unraid via GUI mode, if you have a password longer than 49 characters.   Steps to reproduce:   1. Set a password via WebGUI longer than 49 characters (for example 60). 2. Reboot Unraid and select Unraid GUI 3. Enter username 4. Enter password 5. Incorrect login details (user/password) message   If you carefully count and type in more than 49 characters into the password field (for example 60 as above), you

Wrong Pool State virtcache - missing devices when trying to upgrade 7.1.4. the Unraid will not come on line. dolphin-diagnostics-20250711_1640.zip

Not sure if this is an unraid or Community apps bug but it seems tied to Unraid as CA was updated automatically and worked before the Unraid update Updated to 7.1.4, everything seemed to work fine. I hadn't updated from 6.x for a long time, just don't manage server often. Noticed Plex wasn't running and doesn't show up in docker. Apps tab gives timeout. CA version 2025.06.04a . Followed troubleshooting in forum post (DNS, etc). Can reach github/aws/etc from inside network. Followed recent

Since this morning, when i go to the app tab, action center show me this "bug" Did you allready have this issue ?

brand new system 714 only used for smb ran windows 10 for 2 months no problem now unraid freezes and i cant get a screen to display if frozen i7 4770 , 32 gb ram thanks if i need to downgrade the option is not available snas-diagnostics-20250709-1001.zip snas-diagnostics-20250708-2330.zip

Since Upgrading to 7.1.x I have serious issues whenever I try to update a docker container. After pulling the files, the container cannot stop before updating and therefore docker crashes. I can't even reboot the server, I have to pull the plug. I uploaded the screenshot from the installation window and the syslog. I can also dump the entire syslog here if neccessary.   I've had this problem before when I updated from 7.0 to 7.1. I even reverted the update to 7.0 and everything was wor

Suddenly the "edit" button is missing for some applications in the drop-down list in the Docker tab, in this case for Plex Media Server: If I manually open: http://192.168.1.110/Docker/UpdateContainer?xmlTemplate=edit:/boot/config/plugins/dockerMan/templates-userPlex-Media-Server.xmlthen the template looks like this. It is missing a lot of stuff... If I check /boot/config/plugins/dockerMan/templates-user for templates I can see that the template for Plex is missing, but I have no idea why

I upgraded again to the latest and it crashes my Unraid server when restarting the VM via Windows desktop. I confirmed this doesn't happen in 7.0.1 because I revert to that version, once I upgraded to 7.1.3 or 7.1.4 the problem is still there Specs: I5-13500 Intel CPU RTX 5070ti Nvidia GPU 64GB Ram Windows 11 VM Steps that I made but still crashing unraid 7.1.4: Remove RTX 5070ti and using VNC only Change cores and install the latest virtio drivers 0.1.271 Attached my syslog: syslog T

Hi All, I noticed an issue ever since going to either 7.1.0 or 7.1.1 where the UPS Load number will freeze and not change no matter what i do. Going into UPS Settings and changing the "Start APC UPS daemon:" From YES to NO and back to YES does not resolve the issue. So far only way to resolve this is to disconnect and reconnect USB Cable to UPS. I thought maybe the last 2 updates might address this but still happening. Not a big issue but just wondering is anyone else has noticed this. Sam

It is impossible to have multiple export rules for NFS shares currently. NFS exports are separated by spaces which Unraid web UI is currently removing when hitting the apply button. You can work around this by manually editing /etc/exports and then running exportfs -arv.

I experience the same issues upgrading from v7.0.1 no matter what version i try (i.e. v7.1.0 or v7.1.2)   I have created 2 threads about the issues here and here. After many attempts i was about to collect some diagnostic logs while they were still v7.1.2. I had to revert both machines to v7.0.1 because of the instability issues. Please see my posts for detailed info.   UPDATE 1: Some hours later on the same day T02 server reported the USB was corrupt or unmounted. Since this USB drive was used

When toggling autostart options at docker page, changes are saved to /var/lib/docker/unraid-autostart. However, if multiple switches are toggled at the same time, for example toggling the autostart switch of a folder created by folderview plugin, the unraid-autostart file appears to be edited at the same time, leaving it in a somewhat broken state. For example I have a unraid-autostart file like this in the first place: (I think it's already kind of broken, nginx-proxy-manager only has a "mana

After upgrading from 7.1.3 to 7.1.4, my unraid system starts getting laggy after a while, some docker containers stop working. Stopping the docker service brings the responsiveness back. After restarting the docker service, it takes 30 to 60 minutes until the system gets laggy again and docker containers start failing. Downgrading to 7.1.3 resolves the issue. unraid-test-diagnostics-20250624_1655.zip

When calling the API, it returns an internal server error that the free memory can't be expressed in a signed 32-bit int. Also affects total memory. {"errors":[{"message":"Int cannot represent non 32-bit signed integer value: 2433900544","locations":[{"line":58,"column":7}],"path":["info","memory","free"],"extensions":{"code":"INTERNAL_SERVER_ERROR"}}],"data":null} ETA: Found GitHub issue reporting the same thing: https://github.com/unraid/api/issues/1375

When using the Unraid USB Creator tool to restore from a zip backup, I was required to re-enter network information (IP address, netmask, etc.). Upon inspecting the resulting network.cfg on the new USB key, I found that the values I entered were appended to the existing values from the backup rather than replacing them. This caused invalid network configuration such as: IPADDR="192.168.1.3""192.168.1.3" NETMASK="255.255.255.0""255.255.255.0"and DNS_SERVER1="192.168.1.1" DNS_SERVER1="192.168.1.1

The WebUI element to add ssh keys to the management user has a bug that it is too restrictive and does not support advanced ssh keys. Please modify the regex or validation function to account for the additional valid options present in an authorized_key file. from="192.168.1.0/24,host.example.com"Restrict login to keys coming from specific IPs or hostnames. You can specify multiple sources and CIDR ranges. command="/home/user/system/exec_check.sh"Force a command to be run on login, ignoring an

Hello, the mover are not moving empty Directorys on ZFS Cache to array. In the Mover Plugin is this fixed. Maybe its a good idea to implemented the Mover/Parity Tuning Plugin/Features to Unraid himself. Than we have more Options to modify this and must not using a separate Plugin that are maybe not fully compatible with the actually OS and his Features. Maybe a progessbar for the Mover Process to and for his GUI Feature to empty a disk and move his to another disk. Many Thanks! Many Greeting

This is a frustrating problem I cannot quite pinpoint, but will try to explain.   I updated from 7.1.2 to 7.1.4 a few days ago.  I started having issues with Cloudflare tunnel docker.  The tunnel kept degrading, then coming back, then degrading, then coming back, then degrading, then coming back, etc. I initially thought it was a network cable issue, then an issue with one of my dockers using the tunnel, until I finally zeroed in  (after a day) on cloudflare tunnel docker. I then went about cr

Since updating to 7.1.3 I have been having some strange issues with my Unraid server. I observed the issue after my dashboard application Homarr started showing red status for containers hosted on NUC PC. Homarr uses pings behind the scenes to show status. Here's my network setup: I have a AI Mesh setup. a primary (master) router and 2 mesh nodes (1 connected via cable, 1 over WiFi 5). My Unraid server is connected to the WiFi node along with 2 other devices (1 NUC PC which runs my PiHole Ad B

Losing access to Unraid Web UI after a while. The same happened for me when I tried 7.1.2, and had to downgrade to 7.0.1. On 7.0.1 it has continued to work flawlessly for more than a week again after the downgrade. All dockers still work, and can still ping and ssh into the Unraid server when this happens, but the WebUI never responds. Not sure if this is the same thing other people are reporting, but adding it here. tower-diagnostics-20250614_0004.zip

Hi! I'm using 7.1.4, but the issue has been happening since a few versions prior. After some time, the services start to become unavailable, such as SSH, nginx, and others. It doesn't seem to affect Docker containers. It seems to be related to the services being reloaded and hitting Address already in use any tips or solution to avoid this issue? thank you logs.txt full_syslog.txt tower-diagnostics-20250626-1237.zip

Lorsque je veux ouvrir le terminal, une fenetre s'ouvre demandant l'identifiant et mot de passe. La page suivante s'ouvre sur le tableau d'unraid. Plus d'accès au terminal. unraid-diagnostics-20250625_0852.zip

Unraid Version: Unraid 7.0.0 Summary of the Issue: The Outgoing Proxy Manager setting appears to have no actual effect on Docker's network behavior. Even when disabled, Docker could pull images previously. After rebooting, enabling the proxy causes timeouts, and subsequent tests show that the setting neither enables nor disables proxy usage reliably. Steps to Reproduce: Unraid system previously operated with Outgoing Proxy Manager disabled, yet Docker could successfully pull images from Docker H

As the summary says: Using 7.1.4. Unraid is properly configured to use static IPv4 and IPv6 addressing, and networking functionality is there. Using a docker 'sftpgo' with host networking. The unraid UI shows only the IPv4 container IP, even though full IPv6 functionality is there (on the appropriate ports). nas-diagnostics-20250625-1454.zip