unRAID Server Pro 7.0.1

If you want to edit inside Unraid you can do it for example by clicking on terminal window and then "nano /boot/config/go". Or ssh into shell and edit from there or connect usb stick to windows machine and use your preferred editor.

Second smaller thing that I noticed is that latest unraider does not use UNRAID_GUID env variable anymore, so you can remove it if wanted (as it reads guid from filesystem if UNRAID_UUID is not defined).

So if you want to use custom GUID then rename: UNRAID_GUID -> UNRAID_UUID

I noticed that because I'm running a script that generates fake GUID for the usb device (so you can use your valid pro.key in unlimited number of usb devices). Most people can ignore that (since generated key matches in normal cases).

Whait a minut, what are you saying that its possible for example if we have legit Pro.key file for one flash drive guid/uuid, that by moving that Pro.key to another flash drive with different guid/uuid and by editing go file and replacing UNRAID_GUID to UNRAID_UUID (and change guid/uuid to that of new flash drive) run unraid without patch any of original files just edit go file

Newest unraider needs currently always to patch the emhttpd-file, without UNRAID_UUID it reads the guid from the usb stick and generates the key with that.

So my post was about another unreleased way where you can use legit Pro.key and then fake the GUID that Unraid sees to match the legit keys GUID (that approach does not need any patching of emhttpd so you can run stock version).

So if weare to find Pro.key and know guid/uuid with what this key file is created. Then in theory by editing this one line in go file and put uuid of ORIGINAL key, unraid will be activate no mater what "real" guid/uuid is, since in this case it reads uuid from file and not from physical drive, and all files can be stock so no need to patch anything just edit go file

Unraid will show the missmatch GUID on the screen when you have valid key, so figuring out GUID part is easy if you find a valid Pro.key. But the method to fake GUID is not done inside go-file but somewhere else (but yes, that somewhere else place can be changed to read wanted GUID from go-file).

That method is nice if you have one valid key that you want to use on multiple places, or have small circle of friends who don't leak the key. If the key is distributed widely so it would end up to developers eyes, then it might end up in blacklist and you would need to patch blacklist part on the binary again on future releases.

unRAID Server Pro 6.12.8 has been in normal use for several months. Today it suddenly shut down automatically. When checking the log, it keeps reporting this error.



Mar 14 12:59:58 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 12:59:59 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:00 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:01 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:02 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:03 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:04 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:05 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:07 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:08 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:09 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:10 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:11 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:12 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:13 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:14 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:15 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:16 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:17 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:18 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:19 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:20 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:21 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)
Mar 14 13:00:22 Tower emhttpd: error: get_key_info, 618: Invalid argument (22): get_message: /boot/config/Trial.key (-3)

Solved, the error no longer appears

Try deleting the old trial.key and rebooting, it's no longer needed.

Всем привет!
Как обновить версию unRAID без переустановки всех плагинов и приложений?

1. Made a Flash backup in UNRAID
2. Copied from the new installation all files and folders with replacement except for the config folder
3. As indicated in the instructions for the new version of Unraid, I replaced the unraider file from the unRAID Server Pro 6.12.8_SoftoRooM\unraid_crack\unraider-for-update folder in the config folder on the flash drive.

This is a bug fix release, resolving a nice collection of problems reported by the community, details below.
We highly recommend that all users upgrade to this release.