ConnerVT

Does the server have a simple network setup? Such as a single NIC vs multiple NICs/VLAN/etc? If a simple setup, you can take your flash drive to another machine, then rename the network.cfg file to network.old (file is in flash > config folder). When you boot up the Unraid server the first time, it will create a new network.cfg file with default settings, including using DHCP.

You could contact @hotio and ask him to fix the image link (it is 404). Or you can update your docker template (in Advance View) to use this icon link: https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sonarr-icon.png

USB-C is a style of connector. USB 2.0, USB 3.0 are data transfer protocols. That said, typically all USC-C connectors are used for USB 3.x data transfers. So no different than running USB 3.0 with a USB-A (the common skinny rectangular connector).

It is 2025. Nobody should be booting a computer with legacy BIOS. Developers pretty much expect the features of UEFI to be available for them to use in their code. If someone is using 20 year old hardware, they need to realize that it needs to be kept sealed in a frozen in time state, and expect issues whenever something modern (hardware or software) is introduced to the equation.

Glad you got this sorted. There are currently 3 Nginx Proxy Manager containers in CA, and who knows how many out in the wilds of the Internet. The ones in CA each have a different spin on how they are configured, so your question was definitely one to ask in the container's support thread.

You will likely get a better/faster response if you post in the appropriate support thread in the Applications Support > Docker Containers sub-forum.

Just tried it. Started the container, then launched the GUI. Both started in seconds.

It is selected to do Parity Checks every day:

If you are using default configurations (and if you weren't, you would already know where these files are) - The Docker application code is in the docker.img file, default location is in the system share (system/docker/docker.img) The Docker appdata is wherever you specified in the Docker template when you created the docker container (usually in the appdata share) Docker templates are stored on your flash drive. Most people put their system and appdata shares on a pool, ideally a NVMe or SSD for faster access speed. Now that Unraid allows multiple pools, there are less reasons to have permanent storage (storage that will not be removed from the system) on an Unassigned Device. It is still useful for drives that will be added/removed. I use it for a pair of USB enclosures used for off-site backup and a "SneakerNet" flash drive to physically copy files to/from my server. UD is also useful for connecting remote shares.

It is usually best if you post in the support thread for the particular container you are using. Especially in this case, as your troubleshooting is pointing to a disconnect somewhere inside the container. You didn't indicate which of the many Plex containers you are using, so I can't direct you where to go for answers. I do know with Plex there are several times where something gets broken when they add something new to the application. You may want to try going back a version or two and see if this resolves your issue. Or even try a different container. I use the Linixserverio. Binhex has many people using his container as well. I am not 100% sure (as I don't own a nice GPU like you) but I believe you need to use the open source version of the Nvidia Driver for RTX3xxx GPU.

I'm right about 5 years since building my first Unraid server. Today, it is much like the Ship of Theseus, except for the case, the flash drive and perhaps a few cables, none of the server's original parts remain. A second server was built about 2 years ago to keep this first one company. Many here have the same problem. I suggested starting a support group in the thread I have in my siggy, but it probably wouldn't work out. We would all just spend our time recommending new Docker containers to try... 😮 OSD - I Need Help - Lounge - Unraid

This is pretty harsh. Many of the enhancements available for Unraid come from users who develop and support these with no compensation for their time or effort. If you wish for a better plugin, you are free to develop it yourself, and then either share it or keep it to use on only your system. Your choice. I've used this plugin for several years without issue. Plex is set up with the most basic, standard configuration: linuxserver container, Host Network Type, and only the standard 32400 port forwarded from WAN on my firewall. Pop in the Plex token and select the local server address (mine displays both the local and remote server addresses as choices). It just works.

Better way is to replace one disk at a time. Remove current disk and replace with new, bigger disk. Let Unraid rebuild the data onto the new disk. Doing it this way, if any issue arises, all of your data is backed up on the disk you removed. https://docs.unraid.net/unraid-os/manual/storage-management/#replacing-a-disk-to-increase-capacity

Is the EFI folder on your flash drive "EFI" or "EFI-"? If it is EFI- remove the trailing dash. That is for booting non-UEFI/legacy BIOS.

Fully understand. Your support will be greatly missed. Thank you for all of the support you have provided toward this very important function.

Open your template in Advanced View. What is your WebUI set as? Mine is http:

Possibly a 3.3V issue?

You are tired of hearing people express opinions you do not agree with. You don't have sympathy for users who make such comments. I hope the people at Limetech do not feel the same as you. As Tiffany expressed during the latest Uncast show, it is about the community.

Sorry, but I'm getting pretty tired of seeing such comments. The unraid team isn't that big that they can't test a new build for every single thing that may surface during beta/rc releases. They and the rest of the community (us) are dependent on users testing the betas and rc releases for bugs. While testing betas and rc releases may not be in everyone's interest, and are waiting for the rest of the community to iron out the kinks. Bugs will slip through the cracks and appear in stable releases. This is and will always be the case, forever. Even Microsoft Windows, which is used by billions of users, has bugs slipping through the cracks in stable releases, despite having millions of testers in the Windows Insider program. Therefore, I don't have sympathy for users who make such comments. Sorry for the rant, but I just couldn't bite my tongue seeing at least a couple of similar comments in this thread. Sorry you are tired of Unraid users expressing their opinions and experiences on the Unraid Discussion forum. What are people thinking? Oh, never mind, we shouldn't say...

I hunted all over for that the other day. Never found it. Not very intuitive. If someone with over 1K posts (and that just on this forum) cant find it, how likely will someone fairly new to the forum locate it? 🙄

Believe it uses the RTL8125BG-CG - see: https://www.asus.com/us/displays-desktops/nucs/nuc-mini-pcs/asus-nuc-14-essential/techspec/

Frank1940 is right. I'll add one other thing about his last comment... Need to be doubly careful when backing up things such as other systems or drives. With many backup programs, the final file size is unknown until the backup is completed (for programs which write compressed image files). I use Macrium Reflect for backing up several Windows machines. I skip the cache entirely for the share I keep backups. After all, it is running daily in the background, so I don't need to sit and wait while it runs. Also, it saves writing the data twice - once to cache, then again to the array (via mover).

Note that you cannot execute the script file used by User Scripts itself, as it exists on the flash drive. You will needs to make a copy of it on a different drive with the proper permissions, including making it executable.

Sorry, but I'm getting pretty tired of seeing such comments. The unraid team isn't that big that they can't test a new build for every single thing that may surface during beta/rc releases. 7.1.4 is the 7th release since 7.0.0 was released on January 9, 2025. 164 days, which is a bug fix a month averaging every 27 days. Unraid is a server application, which for many people stability is a primary concern. It is impossible for many (myself included) to have any confidence in updating when watching the issues multiple users have experienced in release after release of Unraid 7. Yes, it was a big undertaking and has major changes. That Unraid is a small group is not an acceptable response for the needed fixes to the application. If it needed to take more time or deliver less enhancements/features, to match the resources the Unraid team has available, perhaps this would of been a better path to have taken.

There really isn't any one answer when it comes to UPS. It is much more nuanced, as a number of factors come in to play, and they tend to interact with each other. Model and size of the UPS Total power draw connected to the UPS Age/condition of the battery Frequency/length of power delivery to your home Time it takes for server shutdown You also need to consider that UPS batteries don't discharge in a linear manner. Many will lose almost 10% when kicking in for a short power sag (ie. your lights flicker/dim for a brief moment). It is also possible you have multiple power outages, such as the power goes out for only a moment, but this happens several times before the UPS recovers to 100%. Each time the line power is restored it rests the countdown to shutdown timer. If you are shutting down almost immediately when the UPS kicks in (such as 60 seconds to initiate shutdown), you can ignore the Battery Level and Runtime Left settings. But you can use these to shut down the server when you get repeated short outages, such that happen during a storm. I have my setting as I'll show below. I don't wish to see my battery level drop below 50%. That is my second catch if somehow multiple outages get past my 6 minute setting for Time On Battery. I have Runtime Left set to 12 minutes as a final safety net, though I hope that never is reached.