Stable Releases

I disabled docker on the docker settings page. I then enabled VLANs under the network settings, and created a VLAN and set it to static. set the ip range to 192.168.x.0 - x being the vlan number. I gave it a gateway of x.1.  Now back over on the docker settings page, i check the box to include the vlan as a container selection. Enable docker and try to edit a docker to be set to the vlan I just created and it does not show up.    FULL TRANSPARENCY - This may not be a bug, it may b

Hey all,   I just completed a parity swap and when the copy process finished, an email was sent out to notify me. It's the content of the email that confused me because when I went to the UI>Main page, I didn't see what I had expected to see.   The subject line alludes to the rebuild process as already running. This would tell me the array is up and disk 8 is being rebuilt from the array and parity data. But that's not the case.   When I logged into the UI

Hey all,   I spent all of yesterday, 9/12, manually trying to figure this out with unfortunately no luck. I received several blue screens yesterday morning on my VM, each typically with a different error code and eventually ended up hard clean-reinstalling windows and wiping my main C drive, a 1 tb nvme drive passedthrough to the VM. I was hoping for this to be the fix, as the blue screens pointed to something being fundamentally wrong with the windows operating system. It is important

As reported by deusxanime under the Wireguard thread.  I am having this exact same issue.   I noticed a possible bug/issue with WireGuard on unRAID. I have a docker container that runs on a custom network and I needed it to talk to a container on bridge so I went into docker settings and enabled "Host access to custom networks". After doing so (and all the required stop/start/reboot), the containers could talk on the network and I thought all was well.   Later that week I tri

I started a parity swap procedure last night around 11pm. I've been watching it for a while now and that's when I noticed the UI bug.   The "Current Operation Started" date and the running time displayed are out of whack.   I started the operation at 12/12/23 11:41 pm. The current date today is 12/13/2023 8:36 am. The system feels that this process started "twenty-eight days ago"   I suspect this is purely UI and I doubt this has any effect on anything serious, but

There is something about this pre-existing zpool that makes unriad unable to create new shares on it from the GUI. I am easily able to create new datasets from the command line and then unraid creates a share (it improperly assigns the dataset generated share primary storage to the array) with the dataset name. Previously in another bug report a user mentioned that behavior (wrong storage assignment) when manually creating datasets from CLI - so that behavior is expected since that isn't the rec

Hoping I could get some help resolving this issue tower-diagnostics-20231204-1843.zip

I was trying to copy some data to my cache drive and noticed that I was unable to write. It is a cache pool of two 500GB WD Black NVMEs in a mirrored pool Looked in the logs and saw that cache was trying to write but was getting errors   Dec 9 20:41:15 Tower kernel: BTRFS error (device nvme0n1p1: state EA): parent transid verify failed on logical 1399619584 mirror 1 wanted 2502028 found 2502026   Decided to do a clean reboot, but saw in the logs that the server was waiting

On the Dashboard, under the Array section, a critical error is displayed stating "Array has N failed device" if the parity is invalid (where N is the number of parity disks), regardless of the device's actual health. On an initial parity sync of a new array, the error message should be that the parity is invalid, not that a device has failed. A failed device insinuates a drive has failed.   Steps to recreate the issue: 1. Configure a new Unraid installation as default. This partic

I'm trying to automate the creation of Traefik labels for my containers using the `xdotool` When the `Add another Path, Port, Variable, Label or Device` is opened and the keyboard arrow down is used to select the Config Type: Label it breaks the Key and Value fields where they only accepts numbers but not any other letters: The issue is present in both Chrome and Firefox.

I updated to the newest version a week or so ago. I rebooted today, and when it came back up my docker image was deleted or missing. The docker config was looking for it in /mnt/user/system/docker/docker.img, and the entire docker folder was missing out of system. i can't seem to find the docker.img file anywhere. 

Additional cache pools read speed not being reported to main gui area. From what I can tell this is also affecting telegraf diskio input as well. copying files from a share that is directly associated to  the cache pools does not show any read speed, it does however show write speed. Nothing in logs and or diagnostics as I have spent a good deal of time going through diagnostics but if you have any pointers id be happy to attempt finding any info  you need besides uploading full d

as this is open since many releases, just more or less as reminder   when using the --net=container function ...   expected behaviour either keep the IP / Ports field blank (as before) or insert the same entries from the "Host Docker" --net=conatiner:<DOCKERNAME>   currently its 1st blank (expected), but after some dockers is updating ... it will take the entrys from the latest installed/updated docker   sample here, oscam is --net=network:

I recently upgraded to 6.12.5 from 6.10.3. I'm now experiencing the server becoming unresponsive or crashing (GUI unresponsive, cannot access folders in Windows Explorer, Plex cannot connect to server) after several hours. Syslog attached which covers two crashes (hard reset occurred Dec 5 17:38 and Dec 6 07:25. Thanks! tower-diagnostics-20231206-0817.zip syslog.log

So I tried upgrading to 6.12.6 recently from 6.11.5 and had call traces on boot and GPU Statistics could not read anything from the iGPU after boot, it would detect the AlderLake iGPU but thats it. Calling modprobe i915 in the konsole would freeze the task, same with powertop --auto-tune or when you manually would try to change the BAD/GOOD state of the iGPU in powertop itself. System also freezes on reboot, not sure where but probably also something iGPU related.   Call trace here:

I am getting constant hard freezes and/or crashes on my new Unraid server, averaging daily, requiring a hard shutdown. This has prevented me from building my parity disks as well as the server keeps crashing before they finish. The quickest crash has been ~6hrs of uptime and the longest the server has lasted without a crash has been ~28hrs. The webui and the server itself both go complexly unresponsive.   The OS version has been 6.12.5 and 6.12.6. The crashing has been happening on bot

Is the 'Docker' page supposed to correctly display containers\stacks created by a Docker Compose file?  I've encountered several issues in this case. They appear as shown in the screenshot below:     The required custom Docker networks were created using the code: docker network create revers-proxy docker network create homeassistant   Below are some basic network settings that might be helpful: Settings -> Network Settings -> Enable bridging: No Se

Hello,   I've been trying for a while to mount a NFS drive on another server using NFS v4.2. And every time, it fallback to v4.0. This is really strange since the NFS server configured by Unraid has no issue talking in the v4.2 protocol.   Example of mount command: root@Tower:~# mount -vvvv dolma:/Backs-Movies /tmp/test/ mount.nfs: timeout set for Tue Sep 12 21:01:32 2023 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.42.12,clientaddr=192.168.42.57' mount.nf

An incorrect naming occurred in the installation file, causing the system to not boot properly   EFI   "-"

After upgrade from 6.12.4  noticed  my backup NAS  NFS connect not working  getting following error NFS: nfs4_discover_server_trunking unhandled error -22. Exiting with error EIO   Diagnostics attached nas-diagnostics-20231201-1951.zip

I suspect this may be a related issue to the recent fix 'silence EDID "block all zeros" and "has corrupt header" notices'   The following errors started showing up in the syslog about 6 hours after upgrading to 6.11.1 and continue to show up about every 15 minutes.   Oct 7 03:33:08 titan kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 01 Oct 7 03:47:00 titan kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 07 Oct 7 03:49

When I upgrade my server to 6.12.6, I lost the connection with Unraid connect (connect.myunraid.net). When I click the confirm buttom, the following error appeared:" {"message":"Request failed with status code 403","data":"Oh noes! something doesn't seem right here"}". I have checked the networks and found that the Unraid TTYD cannot ping internet, hower vms, dockers, plugins and the app market are good. I don't know whether it is correlated to Unraid connect issue. The diagnostics was atta

It was normal before the language pack was updated. After updating the language pack in CA, it became like the screenshot. What should I do?

I 1st observed this while moving some data around on one of my disks. - 4 disk array (1x parity, 3x data). I observe this behaviour on the drive with zfs file system. Running the following command I moved multiple copies of a Windows10.iso file one folder up. I can see that RAM is filling up: Unraid GUI only shows read activity on the disk3 and NO writes. Unitl I get this: The moved files are lost! 3 out of 5 files were moved and nothing can

Hello,   I have activated WireGuard via the VPN Manager. I use the default settings:   Unraid IP: 192.168.1.199 Tunnel Local tunnel network pool: 10.253.0.0 Local tunnel address: 10.253.0.1 Local server uses NAT: Yes Peer 1 Remote access to LAN 10.253.0.2   Now I connected via Smartphone (Android) and WireGuard App.   Scenario A: Array is stopped (off) => This is fine I can access Unraid but not th