bonienl

I made a fix in uploading binary files using Dynamix File Manager, please update.

I made a fix for the upload of binary files using the Dynamix File Manager, please update.

When you enable "Host access to custom network" a routing trick with more specific routes for the same IP subnet (br0) is introduced to fool Docker and make access possible, something which Docker does not allow for security reasons. The first question to ask: do I really need host access? In general this is NOT required, but there are some specific cases which need it. Have you tried and tested to run your containers without host access enabled? Because br0 and shim-br0 is actually one and the same machine (your Unraid box) but announced twice, it can be that certain network equipment, e.g. certain firewalls, do not like this situation and prohibit communication. In such a case you'll need to look into that device configuration and see if exception rules can be set.

newperms only operates on user content in /mnt, it doesn't touch internals.

emhttp is the application used by Unraid to manage and control the functionality of the system. For the user this runs transparently in the background and doesn't need any interaction. The GUI and other related content/scripts is stored under the path /usr/local/emhttp, this you can not view from the FIle Manager, which only gives access to user created content under /mnt. Unraid.net has no relation and works together with the My Servers plugin.

Under Tools -> File Integrity you have the option to view the "hash files". There should be export files for each disk.

Host access works for ipv4 only, the ipv6 part was removed because it caused interference with other ipv6 related activities, which could break the communication.

This is related to the text editor ACE. I recently updated ACE to the latest available version, if you have not updated the File Manager yet, I recommend you install the latest version. The file "mod-log.js" is indeed not existing in the ACE package, I don't know if this an error or not. What kind of file (extension) are you opening when this error message occurs? Ps. I can reproduce this error when I open a *.log file. The syntax file is not present and its content is displayed as regular text. I keep an eye on ACE to see if it gets corrected / included. You can simply ignore the error, it has no impact.

I temporary removed the plugin, investigating an issue at the moment.

I created a new plugin Dynamix Encryption Key, which is inspired by the excellent unraid-newenckey script of @doron When disk encryption is used then under Disk Settings a new section is added, which allows the user to change the existing key to a new passphrase or new keyfile. The plugin is available in CA.

You can use wg-quick up wg0 To bring tunnel 0 up (use ‘down’ to put tunnel down). This should also work from the GUI unless there is an error. Caution: Unraid 6.10 you need to use the GUI to bring the tunnel up or down, because it executes additional commands.

Like to say Thank You to both @JorgeB and @ich777 for your dedication and support in this forum, much appreciated 🎺

I included more translations. Thanks.

This is due to the built-in "intelligence", which assumes you want to copy/move to the same folder on a different target. You can manually remove the folder part before doing the actual copy or move operation.

May 31 11:18:43 PonTower kernel: e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock Normally at this point the ethernet interface is assigned, but here it fails. I don't know if this is a driver issue, I am not using the e1000e driver. Can you try without using the bond interface and use eth0 as a single interface only?

Have you changed the number of "slots" to make all selections available? Can you post a screenshot?

Yes, configuration is always opened in basic mode.

Any files written to your array (shares) have never execution rights enabled. The File manager follows this policy. You can always ssh into your system and make exceptions, not recommended though.

You should run a custom script thru 'bash' or the appropriate language command, don't run them natively.

Security, there should be no reason to have executables running on your storage devices. This is the design of the GUI, can't be changed.

Yes, it is fixed in 6.10.2

Did you read the 6.10.2 release notes?

FYI Unraid 6.10.2 will have a fix for this.

I can reproduce the issue that udev creates interfaces with duplicated MAC addresses, it is under investigation whether this is particular to the udev version used, or kernel version or network driver.

This is by design, in the background rsync is used to do the copy or move operation.