DCCXVIII

This will be a long post. TL;DR, a newbies has issues with the Unraid (unsurprisingly). But also hopes to provide constructive criticism for the devs to improve Unraid. Apologies to the mods if this is being posted in the wrong forum. But there doesn't seem to be a feedback section and some of my points are easily classified as support issues anyway so I thought this place was the next best location to submit this back to the powers that be (if they read what's posted here). Disclaimer: As a newbie, I may be missing or misunderstanding something that could be causing my issues. If this is the case, I would love to be advised on what to do so that I can improve my understanding of how to correctly use Unraid. Obviously this is from from a newbies perspective and is not really aimed at professional users. This is more from the perspective of someone transitioning from turn-key solutions like Synology, Asustor etc, to a DIY solution like Unraid. I also understand that as a DIY solution, Unraid is never going to be as streamlined and easy as the aforementioned turn-key options. That being said, if it is the devs intention to help Unraid break into a wider market in the future where us turn-key users inhabit, then I think this feedback/criticisms/issues will actually be helpful to you. In no particular order: No auto-log out of the webgui after a period of inactivity. This is a basic security feature in all of the turnkey NAS OS's like DSM, ADM etc. I found it shocking that this has never been a feature of Unraid. No native ISCSI support. 3rd party app that implements this is severely out of date and buggy from the comments I read on its support thread. ISCSI is a core NAS function. How is this not a default feature of the base install? The CA store is confusing to newbies. There are so many variants of the same app. If a user searches for PostgreSQL for example, not only are there half a dozen specific PostgreSQL named results due to the many different versions, but some are variants tied to other apps that require PostgreSQL. In addition to that, some of those variants will only work with specific versions of those other apps. And in addition to all of that, the CA store will also output multiple pages of apps from your search that at first glace, have nothing to do with your search term. But it turns out these other apps have buried your search term in their description, rather than where it should be, either in their title or in a separate dedicated field that app developers should be forced to fill that includes all the 3rd party app requirements an app has, that is viewable at the top level of a search. I.e. without having to click on the app at all. No native SMB sub-folder share control at sub-folder level. This was even more surprising to me than the lack of ISCSI support. Again, Unraid relies on a 3rd party app to fulfill this basic NAS function. No ability to rename root username (Could just be a Linux limitation I'm guessing. But basic security tenants teach to you always rename the admin username account such as it is). Archaic file browser UI. Needs to be upgraded to a Windows File Browser or KDE Dolphin style file browser instead. No native backup feature (once again relying on a 3rd party apps). 1st party apps that are not part of the base install that are practically mandatory for any install (e.g. Unassigned Devices, Recycling Bin etc). What's the point of making them something the user has to download if they're so critically necessary and made by Lime tech anyway? No native auto-updater for apps (once again relying on a 3rd party app). "Unassigned Devices" leaves ghost SMB shares still visible on remote computers despite the associated drive long since physically disconnected from the Unraid machine. Not enough customisation of alternative themes. Once again relying on 3rd party apps like "ThemeUI" to pickup the slack. No built in hardware fan control (base install should come with suite of necessary drivers for popular brands. App store provides this, so it's not like they couldn't easily implement it by default). I understand the desire to not bloat the base install. But considering how extremely critical cooling is, I think some effort should be made here even if there's a million and one hardware combinations people could be using to build their NAS. At least throw in the ones from the big name brands like Asus, MSI, Gigabyte etc. USB installer still not updated to support ISO install straight to SSD. Users still must go through the additional hoop of installing to USB, then transferring to SSD via Internal Boot tool. Even worse is the fact that there is no warning of this additional step in any of the online advertising of this feature. So it can catch a lot of newbies off-guard. No explanation of who the "Nobody" owner is or why they end up owning so many of your folders. Extremely slow data transfer (around 60-70MBps) when trying to move data to the NAS from external USB 3.2 HDD's. Likely caused by the existence of the parity feature, so probably nothing can be done about it without yet more tweaking of settings that newbies will obviously not be aware of. Many of the Dynamix series of apps (which are apparently first party by Lime tech?), are out of date, buggy, and no longer function properly e.g. Dynamix Cache Directories. A quick glance at their support threads will illustrate this. Attempting to uninstall an app via Community applications with the "Actions" menu results in an indefinite pop-up box with 3 jiggling dots that never goes away or completes. The case of the missing share settings: I created a brand new share on a brand new install of 7.3.2. Needed to change/delete if later. Couldn't. Why? Because the entire share settings of that particular share of the Unraid GUI was missing. Only managed to get rid of it by deleting the folder itself from the file browser GUI. When I researched this issue, it turned out others have also encountered this problem. Although in their case, it was blamed on a failure/bug during an upgrade process when they upgraded their Unraid OS version. However, I have now proven that this issue can occur on brand new vanilla installs, nothing to do with upgrading the OS. Apps that rely on other apps. Let's look at something like Immich for example. On Synology, a user can just one-click install it and all its dependencies are automatically installed and configured in the background. The user can then immediately access the Immich webgui. Whereas on Unraid, you have to first figure out what it requires in the first place by hoping to come across a guide that actually works. Then you have to figure out the correct variant of Redis and PostgreSQL images are the correct ones in the CA store to install. Only then can you begin to setup Immich. Need the ability to create encrypted shares. As of now, Unraid can only encrypt entire drives (not folders). But the encryption of individual shared folders is a common feature to turn-key NAS OS's. It's a very handy feature that Unraid really should have. In order to gain SMB/NFS access to an externally connected USB HDD, the user must: 1. Download and install this plugin. 2. Figure out the way the plugin works. 3. Change the default settings of the plugin to allow appropriate user permissions. 4. Work out that you need to click the little gear icon next under the settings column that corresponds to your HDD volume. 5. Manually toggle the "share" setting to on. Now compare this to something like Synology where it's literally "plug and play". Suffice it to say, the way Unraid does it is extremely obtuse and difficult to figure out for a newbie. Now before all the pitchforks come out: Yes, I understand that Unraid is a different beast compared to the likes of DSM or ADM turnkey NAS OS's. So I get that some things will always be different by nature of what it is. But at the same time, I think it is important to highlight that if devs are at least vaguely interested in widening Unraid's appeal to the more "noob" mass market, then these are the kinds of criticisms that they should address. Anywho, thank you for making Unraid and freeing me from the ever increasing enshitifiction that the devs/management at Synology seem to be hell-bent on.

Share data is an implied array-only share, but files / folders exist on the cache Share dmz is an implied array-only share, but files / folders exist on the cache So these two shares that I did not create (some random apps did) are meant to be on the cache. They were setup to use the cache, not the array. And indeed their shares show they're set to be on the cache. Yet this plugin is saying that there's an error because the opposite is the case when that doesn't actually exist. ???

I..uh...don't know about any of that. So I ended up just forcibly moving the folder by taking ownership permissions of it via the internal Unraid file browser. Then I pointed the docker container to the new file path. Seems to work no problem.

One last thing I noticed regarding that last issue I had with the Unraid GUI. So as you said, manually changing the "WebUI" field in the advanced settings from http://[IP]:[PORT:8080] to http://[IP]:[PORT:4000] did indeed fix the Unraid GUI shortcut. But here's the thing. Once again, qbitttorrent is the only image that I've had to do this for. E.g. if I change SABnzbd's port, I can leave its "WebUI" field completley unchanged and the Unraid GUI will automatically send you to the newly changed port. But for whatever reason with qbittorrent, if you don't manually update it, the Unraid GUI won't know the new port. Just something weird that is inconsistent with all my other containers that I noticed. Why both the developers of qBittorent and SABnzbd decided to have a fight over who gets to have port 8080 when there's literally thousands of other ports to choose from, is beyond me. Maybe there's some personal beef between them that we don't know about lol.

Thank you again! That fixed the Unraid GUI. You're awesome! :D

Holy shatzba! That was it! THANK YOU! Damn that threw me for a loop. Never even noticed that the GUI refuses to change the port it sends you to and that you instead have to manually change the URL and edit the port number in the address bar. What the hell makes qbittorrent so damn unique that it doesn't behave like literally every other image on the app store??? So basically nobody can ever use Unraid's GUI to access qbits webui since it seems to be hard-coded to port 8080. Thanks again! <3

Hi, thanks for the quick response. Unfortunately those instructions didn't work for me. I followed them, but the webui still refuses to be accessed. I suspected its still hard-coded to only allow port 8080 despite me changing the port to 4000. So I tested it by starting my SABnzbd container which is sitting on 8080. Sure enough, attempting to access your qbittorrent container, resulted in it being redirected to SABnzbd's webui instead.

Hi, I don't want to use the default port of 8080 to access the webui. Can I not use port e.g. 4000? This one, hotio's, binhex etc. All suffer from the same issue. None allow me to change the webui port. When I do, I either get a blank page with the world "unauthorized" in the top left corner, or the page fails to load alltogether. I've tried changing the "WebUI" port. I've tried changing the "WEBUI_PORT" port. I tried changing the port in advanced view to http://[IP]:[PORT:4000]. I tried deleting the variable and the port fields, applying them, then recreating them again and applying them again. Nothing. Changing the port back to the default 8080 brings up the webui no problem. Help please.

Hi, I want to use qbittorrent, but I don't want to use the default 8080 port since it's in use by SABnzbd. The only problem is, no matter what I do, no qbittorrent image will allow the changing of port numbers (this one, linuxserver.io, hotio's etc. Attempting to do so results in either 1 of 2 errors when attempting to access the webui. Either white page with single world "unauthorized", or "unable to connect" error. Changing the port back to the default 8080 makes the image work no problem and you can successfully access the webui. Is there some sort of hard-coded thing preventing anyone from changing the port or what? Help please!

I really like the idea of this arr as I'm otherwise having to manually trim with mkvtoolnix. So I thought I'd test it out before unleashing it on my actual library. However, thus far I do not see it actually doing anything. I copied a file that has only French audio to a test folder, pointed Trimarr at it with instructions to only keep "eng" audio, set the schedule, enabled the run on start option, disabled the dry run option (as otherwise this arr will never do anything as far as I interpret that option), waited a few minutes and.....nothing. No changes were made to the file. As I understand it, Trimarr should have deleted the French audio track from my file, resulting in no audio at all. But this did not happen. Why? Or does Trimarr have internal logic to skip a file even if it has the incorrect audio if it is the only audio stream embedded in the file?

I'm new to Unraid but I can't seem to find this option anywhere. Like how Asustor, Synology, Qnap etc, they all log you out of the webUI after a certain period of time, for security. But thus far my instance of Unraid has never once asked me to log in unless I reboot it. Thanks.

Unfortunately none of this worked for me. I cannot change this containers port. This one, hotio's, binhex etc. All suffer from the same issue. None allow me to change the webui port. When I do, I either get a blank page with the world "unauthorized" in the top left corner, or the page fails to load alltogether. I've tried changing the "WebUI" port. I've tried changing the "WEBUI_PORT" port. I tried changing the port in advanced view to http://[IP]:[PORT:4000]. I tried deleting the variable and the port fields, applying them, then recreating them again and applying them again. Nothing. Nothing works. Changing the port back to the default 8080 brings up the webui no problem. But I want to use a different port. I can only surmise that all qbit images hard-coded to only allow use of port 8080 in a way that does not allow users to change it. Here is the log for when both above values were set to port 4000 that results in no page/webui loading at all: Connection to localhost (::1) 4000 port [tcp/*] succeeded! [migrations] started [migrations] no migrations found ─────────────────────────────────────── ██╗ ███████╗██╗ ██████╗ ██║ ██╔════╝██║██╔═══██╗ ██║ ███████╗██║██║ ██║ ██║ ╚════██║██║██║ ██║ ███████╗███████║██║╚██████╔╝ ╚══════╝╚══════╝╚═╝ ╚═════╝ Brought to you by linuxserver.io ─────────────────────────────────────── To support LSIO projects visit: https://www.linuxserver.io/donate/ ─────────────────────────────────────── GID/UID ─────────────────────────────────────── User UID: 99 User GID: 100 ─────────────────────────────────────── Linuxserver.io version: 5.2.3_v2.0.13-ls470 Build-date: 2026-08-09T07:43:28+00:00 ─────────────────────────────────────── [custom-init] No custom files found, skipping... WebUI will be started shortly after internal preparations. Please wait... ******** Information ******** To control qBittorrent, access the WebUI at: http://localhost:4000 The WebUI administrator username is: admin The WebUI administrator password was not set. A temporary password is provided for this session: 6BcGN8zsw You should set your own password in program preferences. [ls.io-init] done.

I'm a little confused with the "Tray Allocation" feature. I set 2 Layouts. One layout has 9 drives. The other has 3. Yet when I click on the drop down "Tray Allocation" under the "Tray" column, it shows me numbers 1 through 9 even if I have set the "Group" to the layout that only has 3 drives. Setting the Group should dictate how many drives the "Tray" column drop down displays. Yet for whatever reason, it seems to ignore it and just display whichever is largest?

Disabling the favourites setting in Display Setting does not remove the favourites button in the grey theme. Only the black theme seems to respect this setting.

Well IDK what it could be considering the fact that it never showed up once even from a fresh install. I guess I'll have to play around with it.

So does that mean there is no native way to access a USB connected drive to Unraid via a 3rd party machine like Windows?

Hi, I want to access an external USB drive that is connect to my Unraid machine via my Windows machine. I have the Unassigned Disk Devices plugin installed and I've configured its SMB sharing to Private and have enabled read/write access to my account in Unraid. I have also mounted the drive in Unraid. However I still cannot see it in Windows File Explorer. Not sure what else I need to do to expose the drive such that it is accessible via SMB in Windows. I've also noticed that the "Auto Mount USB Devices?" option in the Unassigned Disk Devices plugin doesn't actually do anything. I still have to manually press the "mount" button in order for the drive to become accessible to even Unraid itself.

Ah I see. I figured out a way around it. Turns out you can create a new network mount point in Windows (I guess you're limited to 2 (one is the IP and the other is the name)). So I just used the IP in addition to the name and used the other Unraid account credentials with the IP mount point to bypass the issue.

To the array directly. Is it because it's calculating parity at the same time?

Windows 10. Scenario: I am trying to SMB into a couple different shares. However one share is only accessible using a account A's Unraid user account and the other share is only accessible using account B's Unraid user account. Windows allows me to access the shares with account A. But does not allow me to access the shares only accessible by account B. This despite the fact that Windows does popup a login dialogue box for me to put in account B's account credentials correctly.

Does anyone know if it's possible to use a different folder other than /mnt/user/Photos/ when setting up the Immich container? Because when I tried to use /mnt/user/Photos/Immich (on a brand new install) for example, the webUI refuses to load. Thanks.

Anyone know what might be causing the speed from my external USB drive to be so much slower (down from 150+MBps on Synology to 60+MBps on Unraid) than what it was when using the exact same cables and hardware when transferring from my old Synology NAS? Is it because I installed the Unassigned Devices plugin instead of the Unassigned Devices Plus plugin (my drives are formatted in exFAT)? Thanks.

I assume I must have I guess. But I honestly don't know what because I made the exact same changes each time and sometimes they would result in the container going poof and sometimes they didn't. Thanks for the tip. I did that too. Although I was also using the appdata cleanup plus plugin to scan for orphaned entries as well. That being said, it didn't seem to pickup all the orphaned containers. Only the advanced view you mentioned did.

Hi, I'm new to Unraid so perhaps I'm missing something here. But I've noticed some extremely strange and frustrating behaviour. Its fairly easy to replicate. Just install a container like e.g. Sonarr, SABnzbd, EmbyServer etc (basically anything), then modify its parameters (e.g. delete some var variables or add some path variables etc) to customise the container to your requirements, then hit Apply and...poof! Your docker container evaporates into the nether, never to be seen again. It doesn't happen all the time. So sometimes you can change the dockers parameters and apply and it works (i.e. the container gets updated and reboots correctly). Other times though...poof! Gone. Then you have to re-install it again. This is on a brand new fresh install of 7.3.2 btw.

I was deleting them via SMB from my Windows machine. I was basically creating test folders and text files, then deleting them, then checking the .Recycle.Bin folder and noticing that none of those deleted folders or text documents would appear in the .Recycle.Bin folder. That being said, upon further testing, I figured out a very weird quirk of this plugin. It turns out that if you delete a folder or file of 0 bytes (like I was doing in order to test it), the deleted files are ignored by the plugin and completely bypass the .Recycle.Bin folder, thus resulting in no recoverability. However, if you added a e.g. single text character to a .txt file, saved it, then deleted it, THEN it would appear in the .Recycle.Bin folder. So whoever designed this plugin has chosen to set it up in such a was as to completely ignore empty folders or files. Kind of weird, but there you go.