Leaderboard

I fixed it by running the New Permissions tool on the affected folders You can also add this script to user scripts and run it to be more specific on folders instead of shares/disks. Remember to add the path to your folder #!/bin/sh for dir in "/mnt/user/!!you folder path here!!" do echo $dir chmod -R ug+rw,ug+X,o-rwx $dir chown -R nobody:users $dir done

Hi, also, lag bzw. liegt tatsächlich an der PCIe Karte von Dell.... Hab diese kurzerhand wieder auf das Asus Board gesteckt und dort funktioniert diese wunderbar.. Egal, wollte hier nur bescheid geben, falls jemand anders das Problem auch mal hat. ✌️

AFAIK it's only the Microserver Gen8, many people running a Xeon with VT-d enable, including multiple models myself without issues, pretty sure I've also seen other users with different model HP servers running it without problems, of course can't guarantee there's won't be other models affected but seems unlikely, can also add that the issues start immediately after updating, since at least -rc4, so anyone affected would notice after a couple of hours or so, and if it was a more general issue we would have seen a lot of forum posts about it.

I would recommend anyone running a HP MicroServer Gen8 to not update for now, there have been multiple cases of filesystem corruption after updating, with both XFS and btrfs, looks like the hardware doesn't get along with the new kernel, not clear if it's all models in general or just some specific BIOS/CPU combos, so if anyone updated without issues please post here. Edit to add: The ones I found so far were all using Xeon CPUs with Intel VT-D (IOMMU) enable, I have a suspicion the problem is related to this, it's causing some kind of kernel memory corruption so if you're running one of these with a Pentium or I3 CPU (or a Xeon with VT-D disable) you might be OK. See here for latest update on this: https://forums.unraid.net/topic/123620-unraid-os-version-6100-available/?do=findComment&comment=1129501

This docker template was created based on an already available official docker image Website: https://www.tinymediamanager.org/ GitLab: https://gitlab.com/tinyMediaManager/tinyMediaManager DockerHub: https://hub.docker.com/r/tinymediamanager/tinymediamanager Documentation: https://www.tinymediamanager.org/docs/ My Repository: https://github.com/SmartPhoneLover/unraid-docker-templates DESCRIPTION tinyMediaManager is a full featured media manager to organize and clean up your media library. It is designed to allow you to create/view/edit the metadata, artwork and file structure for your media files used by Kodi (formerly XBMC), Plex, MediaPortal, Emby, Jellyfin and other compatible media center software. Features: - Automatic updates - GUI and command line interfaces - Metadata scrapers for IMDb, TheMovieDb, TVDb, OFDb, Moviemeter, Trakt and more - Artwork downloaders for TheMovieDb, TVDb and FanArt.tv - Trailer downloads from TheMovieDb and HD-Trailers.net - Subtitles downloaded from OpenSubtitles.org - Manually edit any metadata fields with ease - Automatic file renaming according to any user-defined format - Powerful search features with custom filters and sorting - Saves everything in .nfo files automatically recognized by Kodi and most other media centers - Technical metadata like codecs, duration and resolution extracted from each media file - Group movies into sets with special artwork common to all movies in it - Import TV show collections no matter the file organization style used VERSION 1.0 (2022-05-21) If you are going to report a bug or request something to be added/modified, please, take into consideration that I will only be able to apply changes for the work I own only. For example, if I create a docker template for an already existing docker image (not created by me), I won't be able to do more for that image than forward your report or request to the owner of the project.

Hi folks, after spending a fair bit of time hardening my SMB configuration I figured I'd write a quick guide on what I consider the best settings for the security of an SMB server running on Unraid 6.9.2. First, before we get into SMB settings, you may also want to consider hardening the data while it is at rest by specifying an encrypted file-system type for your array (although this isn't a share specific option). For SMB, first set the SMB settings available: I've settled on this as the following block is what I consider to be a hardened SMB configuration for a standalone server that is not domain joined or using Kerberos authentication: server min protocol = SMB3_11 client ipc min protocol = SMB3_11 client signing = mandatory server signing = mandatory client ipc signing = mandatory client NTLMv2 auth = yes smb encrypt = required restrict anonymous = 2 null passwords = No raw NTLMv2 auth = no This configuration block is to be entered into the SMB extras configuration section of the SMB settings page. These settings will break compatibility with legacy clients, but when I say legacy I'm talking like Windows Server 2003/XP. Windows 10+ clients should work without issue as they all support (but are not necessarily configured to REQUIRE) these security features. These settings force the following security options: All communications must occur via SMB v3.1.1 All communications force the use of signing for communications NTLMv2 authentication is required, LanMan authentication is implicitly disabled. All communications must be encrypted Anonymous access is disabled Null session access is disabled NTLMSSP is required for all NTLMv2 authentication attempts In addition, the following security settings are configured for each available share: Also ensure that you create a non-root user to access the shares with and that all accounts use strong passwords (Ideally 12+ complex characters). Finally, a couple of things to note: If you read the release notes for Unraid 6.9.2, you'll see that Unraid uses samba: version 4.12.14. This is extremely important. If you, like me, google SMB configuration settings you'll eventually come across the documentation for the current version of SMB. But! Unraid is not running the latest version, and that's extremely important. The correct documentation to follow is for the 4.12 branch of Samba and the configuration options are significantly different, enough that a valid config for 4.15 will not work for 4.12. With "null passwords = No" you must enable Secure or Private security modes on each exported Unraid share - guest access won't work. There is currently no way to add per-share custom smb.conf settings. So either the server gets hardened or it does not. Do not apply a [share_name] tag as it will not work. It is not possible to specify `client smb3 encryption algorithms` in version 4.12.x of Samba. Kerberos authentication and domain authentication may be preferable in other circumstances, in this instance, additional hardening options may be considered. If you, like me, use VLC media player on mobile devices, you may find that SMBv3 with encryption makes the host inaccessible on IOS devices. The VLC team is aware of this and there is a fix available if you have the bleeding edge/development version of the app, but not if you download the current store version (last I checked, the fix hadn't been released). Should work fine with Android/Windows VLC. If you have any suggestions for other options that I have not included here or that you think are a mistake. Please let me know and I'd be most happy to look into them and adjust. Some other quick hardening suggestions for unraid hardening in general. Disable whatever services you don't need. In my case, that means I: Disable NFS Disable FTP Disable 'Start APC UPS daemon' If you enable Syslog, also enable NTP and configure it. Disable Docker Quick note on docker, having the services enabled allows for 'ip forwarding' which could, in theory, be used to route traffic via the host to bypass firewall rules (depending on your network toplogy obviously) Hope that helps someone else out there. Cheers!

Refer to Summary of New Features for an overview of changes since version 6.9. To upgrade: First create a backup of your USB flash boot device: Main/Flash/Flash Backup If you are running any 6.4 or later release, click 'Check for Updates' on the Tools/Update OS page. If you are running a pre-6.4 release, click 'Check for Updates' on the Plugins page. If the above doesn't work, navigate to Plugins/Install Plugin, select/copy/paste this plugin URL and click Install: https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer.plg Bugs: If you discover a bug or other issue in this release, please open a Stable Releases Bug Report. Credits Special thanks to all our beta testers and especially: @bonienl for his continued refinement and updating of the Dynamix webGUI. @Squid for continued refinement of Community Apps and associated feed. @dlandon for continued refinement of Unassigned Devices plugin and patience as we change things under the hood. @ich777 for assistance and passing on knowledge of Linux kernel config changes to support third party drivers and other kernel-related functionality via plugins. @SimonF for refinements to System Devices page and other webGUI improvements. @thohell for an extra set of eyes looking at md/unraid driver and for work-in-progress of adding changes to support multiple Unraid arrays. @JorgeB for rigorous testing of storage subsystem

unRAID

Yes. i have always wondered why a dummy file that does nothing is not included as standard.

It might be worth mentioning that you can have a ‘stop’ file that is similar to the ‘go’ file that is run near the end of the shutdown process. Not very well documented.

@Vr2Lo Thanks again just tried it and it works correctly bios updated and when I give the command to turn off it turns off regularly

6.10.1 has a fix for this, internal testing now.

Bonjour et bienvenue sur le forum. De mémoire je n'avais eu aucun soucis quand j'ai fait ça y a deux ans. Mais il est possible que Limetech ait fait évoluer la plateforme de licence entre temps. C'est une chose qu'on ne fait que très occasionnellement, je doute qu'un utilisateur puisse te donner une réponse définitive. Est-ce que ton serveur a bien accès aux serveur de Limetech pour faire la transaction ? Dans le doute, j'appelle un ami. @SpencerJ the user has issues renewing the trial license, any recent change on your side ? Should he contact you directly at https://unraid.net/contact ?

Enable the FTP server, then check the log, that's all I did.

#!/bin/bash /usr/local/emhttp/plugins/dynamix/scripts/ftpusers '1' 'root'

Changed Status to Solved

Changed Status to Solved

Looks like the docker image ran out of space, the system share exists on both disk1 and cache, if the docker image is on disk1 the disk is completely full, if that's the case I would recommend deleting that one and recreating the image on cache.

ok i seem to found out the reason and a solution the reason for the sleep/wake/sleep is the conflict between acpi handler script and the elogind configuration. they both react to the key press and acpi handler wins it first then when it wakes up the elogind continues so the solution for power button sleep is to edit or remove the /etc/acpi/acpi_handler.sh or just remove the +x attribute of the file so that it does not execute on the power press and edit the /etc/elogind/logind.conf so that the HandlePowerKey=poweroff is changed to HandlePowerKey=suspend that is being done in /boot/config/go by adding these lines #change power button handling and restart elogind to reload the edited config /usr/bin/sed -i -e 's/#HandlePowerKey=poweroff/HandlePowerKey=suspend/g' /etc/elogind/logind.conf /usr/bin/sed -i -e 's/#AllowSuspend=yes/AllowSuspend=yes/g' /etc/elogind/logind.conf /usr/bin/sed -i -e 's/#SuspendState=mem standby freeze/SuspendState=mem/g' /etc/elogind/logind.conf /etc/rc.d/rc.elogind restart chmod -x /etc/acpi/acpi_handler.sh

To both things no... Seems like something messed up your config, but I don't think this was caused by an RC update or something like that.

This should be correct, but try it again, maybe the old name is cached somewhere, you can always go through the logs and see what name is in there.

I feel like an idiot.. I totally looked past that and never checked the docker for the server name.. thank you!

Please don‘t give advice that‘s not correct. What you are experiencing is that something seems wrong with your hair pin NAT, that‘s why you don‘t see the server on the Server List in game, but you should be able to connect to the game via Direct Connect and your local Unraid IP.

You have to change the server name in the Docker template because the start parameters (that’s how I use the server name parameter from the template) override the files.

You had it almost right in your last post. The port is wrong, should be 8118. So change the port and change the IP back to the 198.... IP

Thank you @JorgeB. The two affected drives are indeed both 8TB Ironwolf ST8000VN004, and are both connected to my LSI card, so it is likely caused by the issue you linked. Before I go modifiying the disk settings however, I decided to try moving the affected disks off the LSI and on to the motherboard SATA, which should confirm if that is the problem. I have a total of 12 disks (only three of which are ST8000VN004) and 8 SATA ports on the MB, so they do not need to be connected to the LSI. So far, the array disk is back online and the parity 2 rebuild is progressing normally.

tried linuxserver, binhex and official. all broken and moreso, after downgrading to 6.9.2 it's still broken. only works if you don't put nvidia and other variables in the setup but gpu support is disabled

Yes, just made the checks. Still working!

Shut down the array and swapped the drive as per documentation (WD Gold 8TB). Rebuild completed without issue. All is good. After 1.5 years on Unraid it was great to see how easy that was when a disk finally failed. Reminds me why I came to Unraid in the first place when I lost a disk in my old JBOD setup. Thanks all for the help.

OK great! Glad we're past that. Unraid 6.9.2 had a behavior/bug which allowed you to use https://whateveryouwant.com even though the SSL certificate did not match the url. Unraid 6.10.0 corrects that and will only respond when the url matches the certificate, otherwise it gives a 404. (actually there is one exception to that, if Use SSL is "yes" then it will also respond to https://ipaddress using a self-signed cert) So: 1) https://hanebijters2.duckdns.org:47438 will give a 404 unless you set the server name to hanebijters2 and the Local TLD to duckdns.org. Probably not what you want to do. 1a) However, the My Servers remote access url does work: https://www.hash.unraid.net:47438 Depending on how your router is configured, this will probably only work from outside your network. The best way to access this url is via the My Servers Dashboard ( https://forums.unraid.net/my-servers/ ) - if it detects you are on the same network as the server it will show the Local Access url, if it detects you are on a different network it will show you the Remote Access url. BTW once you get past this you might want to change the remote access port to something else, just to keep script kiddies away from your server now that it has been published here. 2) https://192.168.1.223:2443 will respond using a self-signed cert if you set Use SSL to Yes. It will not work if Use SSL is No or Auto. (Think of "auto" as "extremely strict" mode) 3) https://hash.unraid.net:2443 . The server is setup for this to work, but DNS Rebinding Protection is enabled on your network, so hash.unraid.net is unable to resolve to your internal IP. If you can disable DNS Rebinding Protection then this will work as well (try googling "nameOfYourRouter disable DNS rebinding protection") Until you resolve that, leave Use SSL on No or Yes, not Auto.

I think no one actually explained how to reproduce the context menu bug: 1. Create a folder and add containers to it 2. Enable preview advanced context menu: 3. Click on a container a menu will open without the dropdown options: Workaround which works for me that might hint where is the problem: 4. Expand the folder and start/stop any container on that folder and the dropdown menu is fixed until the page is refreshed: Hope that helps, I spent few hours debugging this with no luck (I am more of a backend developer, not frontend), I think the starting point should be https://github.com/GuildDarts/unraid-plugin-docker.folder/issues/11#issuecomment-1072792061

I added a script to enable FTP on boot, seems to be working so far. Enabled FTP Server under "Settings, FTP Server". Check the system log and read the line that Enabled the FTP Server, for mine it was "/usr/local/emhttp/plugins/dynamix/scripts/ftpusers '1' 'root'" Added a new script using the User Scripts plugin, and added that data, and set it to run at "At Startup of Array"

Had a very similar issue after 6.10 upgrade for Plex. Plex (official image) could no longer find most of library, whenever you selecetd a show you would get a "Not Available" message. All media was there it just could not play it. Fix for me was to force apply access to the shared folder and all its subdirectories and files. I accessd via console and "chmod 777 -R tv" (tv beign the share in mnt/user and all was restored. I suspect the access rights were wrong before, but docker in 6.10 maybe enforcing rules a bit better? Just a guess.

Trying to get you back up and running as quickly as possible, so just addressing this issue for now: Try http://192.168.1.223/login in your browser's private/incognito mode.

Unraid 6.10 is out, could you please update the hardening for samba 4.15? Thanks

I'm afraid that none of the suggestions here have helped me, so perhaps 'Solved' is a bit premature. After adding my machine to the 'hosts' file and using plain http I get relayed to the URL xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.unraid.net:2443 that AFAIK is something that was introduced with the 'My Server' plugin. That doesn't work in my setup. My guess is also that something is wrong because of the LetsEncrypt changes introduced, but I'm afraid that a lot more digging is necessary.

After upgrading to 6.10 I'm getting this error when trying to start: docker: Error response from daemon: error gathering device information while adding custom device "/dev/dri": no such file or directory. Does anyone have a solution?

The preclear disk plugin is deprecated. Go to CA and look for UD preclear plugin and install that. It is a direct replacement for preclear disk.

Have you had a chance to read this thread? *Something* is updating files on your flash drive repeatedly, causing the My Servers flash backup to back up the changes. You have the rclone plugin installed, that is the likely culprit. Unfortunately, while it is running it updates the /boot/config/plugins/rclone/.rclone.conf on the flash drive continuously. Open a web terminal and run the commands posted earlier in this thread: https://forums.unraid.net/topic/112745-stop-useless-backups/#comment-1032807 that will tell Flash Backup not to backup the .rclone.conf file Then you'll probably want to reboot to clear out your log file.

Man könnte in einem Webserver Docker einen Webmailer installieren, den man auch gut per Smartphone bedienen kann. Oder man leitet alle E-Mails um. Ist nur die Frage ob das erwünscht ist, weil man dann ja von fremden Adresse antwortet.

Attached is a file which fixes the logs not working on RC4+ (Tested RC5, RC5a) Copy this to /config/plugins/docker.folder (replace the existing .txz there) and reboot I do not use this plugin, so if there's any other issues with RC4+ I will attempt to fix if (and only if) you are extremely specific on how to set things up to get it to fail on RC4 where it worked on 6.9.2 I do see some issues on the dashboard when opening up the folder, and I'm probably not going to touch that as dashboard extensions are a hack upon the system docker.folder-2021.08.20-x86_64-1.txz

As the title says, I've just updated Unraid for the first time in a couple of years from 6.9.something to 6.10.0-rc4. As I was going through Unraid, I noticed that the Plex docker was not running. I tried manually starting it, but was getting a "execution error - bad parameter" message pop up. I saw there was an option to Force Update, even though it did say it was already up-to-date, so I tried that. The update failed and then completely removed Plex from my list of dockers. I'm not sure if this error was because I still had / have the Unraid Nvidia plugin installed which I know is not depreciated, however I didn't want to get rid of it until I figured out how to do it and how to make sure that Plex was still using the GPU. So now I'm panicking because I've completely lost Plex and have no idea what to do. I really hope that I will not have lost all of my settings and everything else I've spent the last few years getting just how I want it! Please can someone help, what can I do? Edit: So this thread seems to be very similar to the situation I have just had. I have downloaded and installed the new nvidia driver from Community Applications. I have removed the old Unraid Nvidia plugin. I think I now need to re-download and install a new Plex docker, but how can I go about that whilst also bringing back all of my old libraries, settings, etc? Also I see that there are TWO binhex Plex dockers, one with and one with "plexpass" in the title. I do have Plex Pass, but I'm not sure that my previous docker had Plex Pass in the title. Does that matter? Edit 2: I think I've fixed the problem... This one of the comments in this reddit thread suggested going to Apps > Previously Installed > Install Plex from there and it should bring back app the same mappings. It did! I then used instructions in the 2nd post of this thread on the Unraid forums to add "Key: 'NVIDIA_DRIVER_CAPABILITIES' and as Value: 'all':" before re-installing that Plex docker. I've checked that Hardware Transcoding is turned on in Plex. I've checked in Plex that it is successfully doing hardware transcoding, and I've also checked through "watch nvidia-smi". All seems to be working and exactly as it was! Plex Web interface does look a little weird and different to what I'm used to. It's now got ALOT more of a bluey background, and seems to have merged On Deck with Continue Watching? But I'm guessing that this is another new Plex layout and nothing to do with anything else, not that I'm particularly bothered as I use PMP on my PC & laptop. Still not sure whether I got the docker with or without "plexpass" in the title, but it doesn't seem to be causing any problems either way....

Use this syntax qemu-img resize --shrink vdisk1.img 60G

Nun ja, du könntest die Anleitung in meinem Link (s.o.) befolgen und benötigst nicht einmal eine Linux Maschine: geh per ssh auf den Unraid server (entweder von deinem PC via putty, oder über das Webterminal in Unraid) wechsle dort in das Verzeichnis in dem deine .ova liegt (cd /mnt/user/freigabe/verzeichnis) Entpacke die .ova Datei mit dem Befehl tar -xvf dateiname.ova Konvertiere die entpackte .vmdk Datei mit dem Befehl qemu-img convert dateiname.vmdk deinwunschname.qcow2 -O qcow2 Das war dann erst mal die Konvertierung. Bei der Erstellung der VM darfst du dann natürlich keine neue virtuelle Festplatte erstellen lassen, sondern verwendets die "deinwunschname.qcow2". Hierzu musst du Sie vorher noch in das Verzeichnis für diese VM verschieben (z.B. unter /mnt/user/domains/deineneueVM). Mach dich mal an die Konvertierung und dann sehen wir weiter, ok?

@binhex thank you for weighing in. I hadn't even considered that different servers OF COURSE need/require different versions of java. So, Crafty does it? Looks terrific, I'll give it a spin for my servers. Would you, or someone comment on all these different flavors of minecraft dockers? Three right from Binhex?: 1. Crafty (unRaid forum thread) 2. Minecraftserver (unRaid forum thread) 3. Mineos-node (unRaid forum thread) For me, I've been using Mineos node for the web user interface, and ability to run several servers at once on different ports. Took a bit of finagling to get Geyser working (friend on a Switch), but got it, and it's been aok. I don't like the built in backup system in Mineos-node, but solved that with another plugin drivebackupV2.

Docker containers are in essence tiny virtual machines, so the base distro that the app runs on can be different, the frequency and method of updating can be different, the supporting apps inside the container can be different. All of these differences are reflected in the type and frequency of questions on the support thread. If you want actual technical details you will have to examine the docker build lists for the different containers, or ask the container's authors for more info.

Hey, This is AnalogJ, the developer of Scrutiny. I've seen some confusion around the SCRUTINY_API_ENDPOINT. If you're using the "all-in-one" container, which runs both the API and the collector, you do not need to touch that variable. Set it to the default value (http://localhost:8080). Within the container, the API is listening on localhost:8080, even if you bind that port to something else on your host. It's primarily used by users who are deploying scrutiny in a hub/spoke model -- one API server & db with multiple collectors. Hopefully that fixes most of your issues, however if any of you are still running into problems, feel free to open an issue on Github: https://github.com/AnalogJ/scrutiny. I can also be found on the Self-Hosted podcast discord & the LinuxServer.io discord: AnalogJ#3506 If you find Scrutiny useful, and you'd like to support my work, here's a link to my Github Sponsors page: https://github.com/sponsors/AnalogJ Thanks for your interest & support!

Yeah I am seeing this on a couple drives as well, especially when in high utilization. I have changed the SATA breakout cables as well and it did not resolve it. Perhaps the drives are going...

StarTech.com 4 Port PCI Express (PCIe) SuperSpeed USB 3.0 Card Adapter w/ 2 Dedicated 5Gbps Channels Chipset: Renesas/NEC - µPD720202 Findings: Purchased this because it had 4 individual USB controllers on the board thinking the extra price would allow for more flexibility with my VMs. Requires SATA/Molex power, works fine when booting native to Windows 10. It is recognized in Unraid under Settings -> Hardware however when passing through the PCIE card to a VM, while the card is detected, it always has an error with Code=10. This is with the standard Windows drivers and also with the drivers from the manufacturer's website. There are other posts online with the same result (Code=10 error in Device Manager) but not promising workarounds. I suspect this is something at the Linux level as when I do not pass through the PCIE card and hook up USB devices directly to the card, they also are not recognized by Unraid. I give up on this card.

Check the cables first. For a basic server 430W is normally fine with more drives than you have provided it can handle the peak startup currents for all drives at once. I have had a few glitches over the years - it has always been power cables or SATA cables that were responsible.