Leaderboard

If no updates are offered then its the latest (for now). I work hard on the new one, compatible with Unraid 6.12. beta soon

Update is now available for Docker Folder. Note that this only fixes the issues on the docker tab and the VMs tab. Folders are not currently available on the dashboard. (ie: Interim compatibility fix for 6.12)

I've got it now working on the docker tab in 6.12. Trying to figure out what's going on with the dashboard hacks. VMs I don't see being an issue. Should have an update for this early next week

I just stumbled across something called RetroNAS recently. It's an open source project to allow people to have an easier means of streaming their game backups from a centralized server to various game consoles & retro systems with network capability. I personally love this idea since I think it is a better alternative to buying a larger storage media for each individual console or system. Keeping storage at the console level also generally means having no parity protection which is a bummer. I think the key selling point of RetroNAS is to simplify the setup of the various tools and protocols required to facilitate the communication between server and the various game consoles/systems however many of these protocols are older and insecure. In this instance I think that keeping something like RetroNAS containerized would be preferable. At the moment there is a lot of interest in getting this packaged up as a docker container for use on systems such as Unraid, QNAP, Synology however the developer for RetroNAS does not have personal experience with such systems. Does anyone know how feasible it would be to make this as a container for Unraid? For reference here is a link to the project on github along with a video introduction by RetroRGB: Github: https://github.com/danmons/retronas Youtube Video:

Ja, tatsächlich. Hab ich gemacht: https://github.com/netdata/netdata/issues/14760

Nutzt du den netdata Container? Der soll diese Meldungen verursachen: https://forums.unraid.net/topic/123981-anyone-know-where-these-errors-are-coming-from/ Warum das "normal" sein soll, erschließt sich mir aber nicht. Da muss doch irgendein Bug im Container sein. Sonst würde der dich die ganzen Fehler nicht verursachen. Vielleicht mal in GitHub melden.

I decided to forego mounting the docker socket to the LXC and ended up opening up the TCP port to the docker daemon and am connecting to it through ip/port to get all of my containers. Thank you for the help anyway.

@h0schi Danke für die Info

I've been having to restart the API every couple of days to resolve this. Restarting it fixes the issue immediately but it eventually returns. It started for me the same day OP posted this thread. I'm on 6.11.5.

Yes. May I first ask why you want to do that? Do you want to use Docker from the host for developing container? If yes, I would rather recommend that you install Docker inside the LXC container, that would be the preferred way to go (I do this also in a LXC container with Docker installed in the container to build my container locally and upload them to Docker Hub and GHCR). I really don't recommend mounting the docker.sock from the host and this is also a huge security concern and isn't recommended by the devs or me... Installing Docker is easy as: #!/bin/bash #Install Docker cd /tmp curl -fsSL https://get.docker.com -o get-docker.sh chmod +x /tmp/get-docker.sh /tmp/get-docker.sh rm /tmp/get-docker.sh (please note that the above steps should be executed as root, you maybe have to add "sudo" to the line /tmp/get-docker.sh depending on the distribution that you are using)

Thanks so much for the quick reply. I am glad to hear that if using the device mapping it does not matter what port my coordinators are plugged into. That puts that concern to rest! On the question of "Did you set them to auto connect in the mappings at VM start", I am pretty sure I did but when tinkering at the time I was first setting this up maybe I made a mistake? I will see how it goes for now and let you know if I see any additional issues. Probably user error..... BTW, this is an Awesome Plugin. Before I found it I was really struggling with how I was gonna make this work for my three Home Assistant coordinators so this was a gold find for me. Thanks!

alturismo thank you for your help 👍

If you need any further information or testing i would be happy to assist.

Ahhh, ok....da muss man genau hinschauen...jene, die Du gekauft hast, ist wohl nicht geeignet. Die scheint für "Mining Rigs" zu sein. Schick die zurück und nimm die "echte" Pico, aber eine mit mind. 120W, schau hier: https://geizhals.de/?cat=gehps&xf=4174_Wandlerplatine ...und auf die 12V-Buchse achten. Tja, wenn Du das Gehäuse selbst druckst, fehlen diese "Kleinteile", die sonst im Gehäuse mit drin sind. Schau mal hier: https://www.amazon.de/Ytian-Stücke-Schalter-Power-Reset-Schalterkabel/dp/B07BT3ZZ8X/ref=sr_1_2?__mk_de_DE=ÅMÅŽÕÑ&crid=PGRTWA1CZJV8&keywords=mainboard+reset+power+set&qid=1679140920&sprefix=mainboard+reset+power+set%2Caps%2C92&sr=8-2 Edit: oder sowas, da isst dann auch ein kleiner Summer dabei, falls es mal vom MB her "piepst", hörst Du das: https://www.amazon.de/InLine-59910-Mainboard-Testset-5-teilig/dp/B000PELTVA/ref=pd_bxgy_sccl_1/259-5900375-4585650?pd_rd_w=Mrtgc&content-id=amzn1.sym.6885cacb-c49f-4303-9dbe-86c115720418&pf_rd_p=6885cacb-c49f-4303-9dbe-86c115720418&pf_rd_r=EGVGR2GMWB74Z5H9VMHV&pd_rd_wg=XEUGC&pd_rd_r=9b6dd18b-ab54-40d5-b369-88abe65f5f95&pd_rd_i=B000PELTVA&psc=1

[arco@arco-qnap ~]$ lsmod Module Size Used by btrfs 2015232 0 blake2b_generic 20480 0 xor 24576 1 btrfs raid6_pq 122880 1 btrfs ufs 102400 0 hfsplus 172032 0 hfs 98304 0 cdrom 86016 2 hfsplus,hfs minix 61440 0 vfat 24576 0 msdos 20480 0 fat 102400 2 msdos,vfat jfs 258048 0 xfs 2588672 0 libcrc32c 16384 2 btrfs,xfs snd_seq_dummy 16384 0 snd_seq 110592 1 snd_seq_dummy snd_seq_device 16384 1 snd_seq bnep 36864 2 joydev 28672 0 mousedev 24576 0 usbhid 81920 0 intel_rapl_msr 20480 0 snd_hda_codec_hdmi 94208 1 intel_rapl_common 36864 1 intel_rapl_msr intel_powerclamp 20480 0 snd_hda_codec_realtek 196608 1 snd_hda_codec_generic 110592 1 snd_hda_codec_realtek ledtrig_audio 16384 1 snd_hda_codec_generic coretemp 20480 0 kvm_intel 446464 0 snd_hda_intel 65536 2 snd_intel_dspcfg 36864 1 snd_hda_intel kvm 1323008 1 kvm_intel snd_intel_sdw_acpi 20480 1 snd_intel_dspcfg i915 3784704 20 snd_hda_codec 217088 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_core 139264 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek irqbypass 16384 1 kvm igb 331776 0 snd_hwdep 20480 1 snd_hda_codec snd_pcm 200704 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core crct10dif_pclmul 16384 1 snd_timer 53248 2 snd_seq,snd_pcm crc32_pclmul 16384 0 dca 20480 1 igb drm_buddy 20480 1 i915 snd 151552 14 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm polyval_generic 16384 0 soundcore 16384 1 snd ttm 102400 1 i915 gf128mul 16384 1 polyval_generic drm_display_helper 208896 1 i915 mei_hdcp 28672 0 mei_pxp 20480 0 ghash_clmulni_intel 16384 0 sha512_ssse3 57344 0 cec 86016 2 drm_display_helper,i915 spi_nor 135168 0 mei_txe 40960 2 at24 28672 0 intel_gtt 28672 1 i915 mei 192512 5 mei_hdcp,mei_pxp,mei_txe aesni_intel 401408 0 hci_uart 188416 0 i2c_i801 45056 0 mtd 110592 1 spi_nor crypto_simd 16384 1 aesni_intel intel_xhci_usb_role_switch 16384 0 roles 20480 1 intel_xhci_usb_role_switch iTCO_wdt 16384 0 btqca 28672 1 hci_uart spi_intel_platform 16384 0 intel_pmc_bxt 16384 1 iTCO_wdt spi_intel 36864 1 spi_intel_platform iTCO_vendor_support 16384 1 iTCO_wdt btrtl 28672 1 hci_uart lpc_ich 28672 0 i2c_smbus 20480 1 i2c_i801 btbcm 24576 1 hci_uart cryptd 32768 2 crypto_simd,ghash_clmulni_intel intel_cstate 24576 0 btintel 53248 1 hci_uart atomisp_lm3554 24576 0 intel_chtwc_int33fe 16384 0 bluetooth 1077248 12 btrtl,btqca,btintel,hci_uart,btbcm,bnep ir_rc6_decoder 20480 0 atomisp_gmin_platform 40960 1 atomisp_lm3554 video 73728 1 i915 videodev 352256 1 atomisp_lm3554 mac_hid 16384 0 rc_rc6_mce 16384 0 ecdh_generic 16384 1 bluetooth wmi 45056 1 video rfkill_gpio 16384 0 mc 81920 2 videodev,atomisp_lm3554 rfkill 40960 4 rfkill_gpio,bluetooth i2c_hid_acpi 16384 0 ite_cir 36864 0 pwm_lpss_platform 16384 0 i2c_hid 40960 1 i2c_hid_acpi intel_int0002_vgpio 16384 1 pwm_lpss 16384 1 pwm_lpss_platform crypto_user 20480 0 dm_mod 225280 0 loop 36864 0 fuse 204800 5 bpf_preload 24576 0 ip_tables 40960 0 x_tables 61440 1 ip_tables ext4 1163264 1 crc32c_generic 16384 0 crc16 16384 2 bluetooth,ext4 mbcache 16384 1 ext4 jbd2 217088 1 ext4 sdhci_pci 94208 0 xhci_pci 24576 0 crc32c_intel 24576 3 xhci_pci_renesas 24576 1 xhci_pci cqhci 45056 1 sdhci_pci sdhci_acpi 32768 0 sdhci 98304 2 sdhci_acpi,sdhci_pci mmc_core 266240 4 sdhci,cqhci,sdhci_acpi,sdhci_pci Also: [arco@arco-qnap ~]$ sudo stty -F /dev/ttyS1 1200 [arco@arco-qnap ~]$ sudo echo -e "M^\x0" > /dev/ttyS1 bash: /dev/ttyS1: Permission denied [arco@arco-qnap ~]$ sudo stty -F /dev/tty1 1200 stty: /dev/tty1: unable to perform all requested operations

Single M.2 NVMe to PCIe adapters are transparent to the OS, any will work.

Yes, using the same controller (if it's a RAID controller).

in the end, simple as @ich777 pointed out, as i want it to be failsafe and closer to finishing state i made a 2 step way. 1/ touch a file which changes the mod time after the last job is done 2/ wrote myself a small check script #!/bin/bash donefile="/mnt/cache/appdata/luckybackup/check" ### file created/redone by luckybackup after complete waittime="10800" ### time in seconds to check age dockname="luckybackup" ### case sensitive name for docker to restart if [ "$(( $(date +"%s") - $(stat -c "%Y" $donefile) ))" -gt $waittime ]; then echo $donefile is too old else docker restart $dockname echo $dockname restarted fi 3/ schedule it to fit my personal setup so, my backup starts at 3.45 am, needs ... some time, depending now ... so i check 1st time at 4.55 am if the job is done and restart the docker, if its not done then, it will check at 7.55 am ... and finally at 10.55 am ... (thats why the 10800 seconds timer, 3 hours lookup) then definately all jobs are done and the docker will restart and GUI is updated.

Just restart the container on a daily basis with a user script through Unraid so that it doesn‘t interferes with the schedule in the container. docker container restart CONTAINERNAME (of corse replace CONTAINERNAME with the container name - case sensitive!)

Hab jetzt mal testweise einen ASM1166 6 Port Controller eingebaut. Package State geht auf C7 und ich bin im Spindown bei 21 Watt. Der LSi hat also den C7 verhindert. Mit den 21 Watt bin ich bei der Anzahl Festplatten schon sehr zufrieden.

You just connect the disks to another computer, Unraid is mostly hardware agnostic, this might be a problem though: If it's really a RAID controller disks might not work correctly on a different one, one of the reasons RAID controllers are not recommended.

ich glaube dafür ist es zu spät ich würde auch erst wieder normal mit Image starten und dann evtl. umstellen wenn der Fehler gefunden wurde, aber egal ...

It means the drive is past its predicted life, based on the total writes, it doesn't mean it's failing, they can sometimes reach 200% or more, I have a few way past 100% life and still going strong, just make sure you have backups of anything important, like you always should.

exactly, its a lack in the webgui app itself. may as note, this is normally a desktop app, i guess the author of the app (not the docker) is just checking while opening the app and not watching the cronjob results while the app is open ... which is the case in a docker may just check your backup targetif it ran properly or not ... personally i made a workaround for me and posted it also here in this thread.

Before you go too far, try resetting only the network and see if you can re-do the setup the way you would like. delete network.cfg and network-rules.cfg under config folder on your flash drive and reboot It doesn't look like you really want to start fresh, but rather just start fresh on certain things while keeping most of your setup. Someone can better advise on what to do if you post diagnostics

Figured that out..... It is now populating.

Hello guys just wanted to update the thread as of the date of this comment i have found and fixed my issue, it was “RDT-CLIENT” docker ignoring PUID and PGID, more info on their github so my fix was to add both PUID and a PGID variables to the template and set those to the same IDs as my arr containers.

Will Do. Actually Got some transcoding stuff thats buggin me. Maybe i'll see you in that thread lol. Thanks for all your help in on the forums

First thing to do is go to the Plugins tab and make sure you are running the latest version of the plugin. Currently that is 2023.03.09.1140 Then check https://status.unraid.net/ and confirm we are not having back-end issues. If we are, then I apologize and ask you to please wait until those are cleared. If there are no issues reported on our end, try restarting the Unraid API via `unraid-api restart`. Wait at least 30 seconds, then reload the webgui. If restarting the api solves the issue then we still have more work to do on our reconnection logic. The API should be able to detect that it was disconnected and automatically reconnect. If restarting the api doesn't solve the issue then you need to check your network for a firewall or pihole or adguard that might be blocking the connection.

So 7-days later past the reformat of my cache drives all is stable and right in the world! Thanks for the assistance.

Cannot see any thing jumping out in the logs. But will keep looking.

Tremendous. Thanks. Worked perfect.

das ist zwar soweit korrekt, ich würde nur trotzdem mal schauen was Stand ist da er sich sonst das Docker Verzeichnis "voll" schreibt ... und je nach Regel der Quatsch mit Cache prefer greift und was auch immer dann moved wird usw usw ...

@rsbuc I just uploaded a version of the plugin that should now run the temperature detection code correctly again. Took me ages to track down what turned out to be a simple typo that had crept into the code somehow (had '&' when it needed to be '&&').

One of the issues with this style of selling is the lack of concrete delivery dates. They hope they can just stall the shipments until the prices people paid become normal market prices because tech tends to get cheaper as newer higher capacity items come on the market. I see this as the best case scenario, where you do actually receive the products eventually, but by the time they ship, you could purchase them on the open market for cheaper. Worst case, they are outright frauds, and intend to close up shop shortly after shipping enough units to satisfy the influencers that were gullible enough to hype them. The kickstarter model has so little accountability, any money you send now before products are available for resale on the open market should be considered gifts to the campaign, and you just hope that they are good people that are honest enough to not skidaddle with millions of free dollars. This particular campaign has just the right mix of authenticity to bring in huge amounts of cash, I hope they really do have the knowledge and honesty to deliver, but it doesn't smell that way right now.

Done it. Updated unraid then removed zfs plugin (that’s probably better other way around). Nothing was detected so did a zpool import -a then I was able to stop and start docker. one disk is apparently unavailable but otherwise it’s working as far as I can tell. Will let it settle before trying anything further. For those wondering zfs version is 2.1.9-1.

Thanks @steini84, it is strangely exciting to be able to remove my usb drives from my setup. Just a note that you may not be out of the woods yet because according to the release notes only certain zfs features are supported. I am not sure how those are being limited but I have more than one pool, cache and special vdev, way more than 4 drives, dedup and probably other things. I would have thought zfs was just zfs or maybe the limitations are just in a new gui? Hoping I can just upgrade and that’s that. Slightly scared to do it! 😮

Looking forward to this plugin being updated for 6.12. Docker list looks ugly

Hi, da ich mich auch mit diesem Thema befasse und am Anfang mich zu sehr an meine "klassische" Ablage orientiert habe, kann ich empfehlen dieses nicht 1:1 zu übernehmen. Hintergrund ist, dass viele Elemente dadurch keinen Sinn machen, z.B. Rechnungen 2023 - hierfür gibt es Typ "Rechnung" und eine Filterung "Ausgestellt am" --> nach 2023. Was das Anlernen angeht, genauer das Zuweisungsalgorithmus Auto, ja es braucht einige Dokumente und vor allem von jeder Zuordnung eine entsprechende Menge - wie viel kann ich nicht sagen. Was ich gelesen habe, ca. 50 unterschiedliche Dokumente. Hier mein Auszug, was den Workflow und die restlichen Daten angeht. Mein Workflow: 1) Alles Neue wird mit dem Tag "INBOX" versehen 2) prüfen, ob die Zuordnung richtig ist (habe fast alles auf Auto stehen, bis auf paar Ausnahmen) 2.1) richtig kategorisieren 3) Tag "INBOX" entfernen. Meine Korrespondenten: - 0_Ärzte - 0_Behörde - 0_Versicherung usw. - Deutsche Rentenversicherung - FIRMENNAMEN (Arbeitgeber, regelmäßige Korrespondenten) ----> Allgemeine sind mit "0_" versehen, für alles andere lege ich eigenen Korrespondenten an bzw. ziehe diese um, wenn ich häufiger was von denen habe. Tags - wie erwähnt, die meisten sind bei mir auf Auto: - Auto XYZ - Beleg Steuererklärung 202X - INBOX - Wohnen - Objekt (<-- Eigentum) - zz_Garten - P-XXXXXX (<--- P für Person die es betrifft/Empfänger, da dieses aktuell Paperless aktuell nicht kann) Dokumenttypen (Einzahl geschrieben): - Angebot - Bescheinigung - Gutschrift - Information - Kontoauszug - Rechnung Speicherpfade nutze ich aktuell nicht. Zusätzlich habe ich folgende Variable aktiv: - PAPERLESS_TRASH_DIR - Papierkorb - PAPERLESS_IGNORE_DATES - da sind die Geburtstage von uns - PAPERLESS_OCR_LANGUAGE=deu - PAPERLESS_FILENAME_FORMAT={correspondent}/{created_year}-{created_month}-{created_day} {document_type} {correspondent} {title} - {tag_list} (ist meine Exit-Strategie, aber auch, wenn im Notfall eine dritte Person an die Daten oder auch das System nicht mehr funktioniert, dass jemand mit den Daten was anfangen kann) ergibt folgenden Pfad und Dateibenennung: /media/documents/archive/KORRESPONDENT/2023-01-04 Bestellbestätigung KORRESPONDENT TITEL - KOMPLETTE TAG-LISTE.pdf sind mehrere Tags zugeordnet, werden alle Tags ausgegeben, z.B. Wohnen, P-XY Auf folgenden Seite (teilweise auf NG-Version bezogen, aber der fachliche Teil ist entscheident) habe ich paar Tipps und Hinweise mitnehmen können: https://paperless.codeberg.page/paperless/2021-05/paperlessng/ Auf der Webseite sind mehrere Einträge zu dem Thema vorhanden, am besten mit dem ältesten anfangen.

Running `unraid-api restart` fixed it for me.

space invader one has answered your prayers https://github.com/SpaceinvaderOne/RetroNASinabox on Ca as RetroNAS_inabox

Hi, After Weeks setting up my home network, I finally finished it and it works properly as I belived, I just want to make sure that I build it right. Can you let me know if my topology seems right please . I am not that familiar with network but I tried my best.

@binhex Any plans to update this docker now when ruTorrent 4.0.1 is released? Seems like a very nice update from them.

Uncast Episode XIV: Return of the Uncast with Bob from RetroRGB Season 2 of the Uncast pod is back and better than ever, with new host Ed Rawlings, aka @SpaceInvaderOne 👾 On this episode, Bob from RetroRGB joins the Uncast to talk about all things retro gaming, his discovery and use cases for Unraid, a deep dive into RetroNAS, and much more! Check out the show links below to connect with Bob or learn more about specific projects discussed. Show Topics with ~Timestamps: Intro from Ed, aka Spaceinvader One 👾 ~1:20: Listener participation on the pod with speakpipe.com/uncast. Speakpipe will allow you to ask questions to Ed about Unraid, ask questions directly to guests, and more. ~2:50: Upcoming Guests ~3:30: Bob from RetroRGB joins to talk about Unraid vs. prebuilt NAS solutions, use cases, and RetroNAS VMs. ~6:30: Unraid on a laptop? ~9:30: Array Protection, data recovery, New Configs, new hardware and client swapping. ~11:50: Discovering Unraid, VMs, capture cards, user error. ~17:30: VMs, Thunderbolt passthrough issues, Thunderbolt controllers, Intel vs. AMD, motherboard hardware, and BIOS issues/tips. ~21:30: All about Bob and RetroRGB. ~23:00: Retro games on modern TVs and hardware and platforms. ~24:34: MiSTerFPGA Project ~27:15: RetroNAS ~30:30: RetroNAS security: Creating VLANs, best practices, and networking tips. ~37:15: Using Virtiofs with RetroNAS on Unraid, VMs vs. Docker, and streamlining the RetroNAS install process. ~43:13: Everdrive Console Cartridges and optical drive emulators. ~46:50: Realistic expectations and advice to new retro gaming enthusiasts. ~51:05: MiSTer setup how to's and retro gaming community demographics. ~55:45: Retro gaming, CRTs, emulation scaling, wheeled retro gaming setups, and how to test components and avoid hardware scams. ~1:05: Console switches, scalers, and other setup equipment. In the end, it all comes down to personal choice. Show Links: Connect and support Bob: https://retrorgb.link/bob Send in your Uncast questions, comments, and good vibes: https://www.speakpipe.com/uncast Spaceinvader One interview on RetroRGB MiSTer FPGA Hardware https://www.retrorgb.com/mister.html RetroNAS info: https://www.retrorgb.com/introducing-retronas.html Other Ways to Support and Connect with the Uncast Subscribe/Support Spaceinvader One Youtube https://www.youtube.com/@uncastpod

I have not found a solution other than disabling cache on the pool in order to get the storage stable and usable in Proxmox host (not specific VMs or LXCs) - just adding it as storage.

Karte ist gebaut. C-State C7 kann erreicht werden, @cuddles

Known issues & planned features Known issues If container autoupdate is enabled, the container gets started and producing a "Already started" info Currently being accepted as ok - produces some debug info inside the log but does not treat it as error 02.2023: Some users facing "tar verify failed!" issues although all dockers are stopped. Currently searching possible root causes. Planned features Complete overhaul of the code including PHP8 compatibility ✔️Files/Folder config per container ✔️Maybe extra sources apart from containers? ✔️Option (separate) to disable encoutered errors (containers, tar backup, tar verify) ✔️Multicore backup (zstdmt) ✔️PreRun/PreBackup/PostBackup/PostRun custom scripts ✔️Restore single container data ❌Treesize view of all source data? ✔️Include the docker templates in backups ✔️Some easy diag functions Share diag docker infos and the config ❌Some anonymous statistic collection Opt-In ❌ Not now / Never / Not planned ✔️ Done ⏳ In progress Notes Multiple appdata volume sources possible Save to single archive removed The backup will always create seperate files now Flash backup is back! It uses unraids native way for doing it VMs backup also included Basic operation. More to come - maybe

Thanks for that. However, it seems that I don't have permission to access that topic. This confirms my view that plugin documentation is a real mess, with snippets of information scattered all around!

Just an addendum - you can load the drivers during the network setup process if you like. Hit SHIFT + F10 to get a command line open Switch to the location of the virtio iso (in my case, E:) and change to the NetKVM\w11\amd64 directory cd e:\NetKVM\w11\amd64 Install the driver pnputil -i -a netkvm.inf Network should now be detected. Close the command prompt and continue.

As I stated before I simply do not care for the cloud account nor the UPC options. Simply put I care too much for my security and my privacy. I feel that is being forced on us without any options or consideration for best practice security principles. I don't want to see it in my webGIU and I don't care to use it. Can you please have a switch to toggle it off the webGUI so we don't have to deal with it every time we look at our dashboard? "UPC and My Servers Plugin - [rc2] reworded The most visible new feature is located in the upper right of the webGUI header. We call this the User Profile Component, or UPC. The UPC allows a user to associate their server(s) and license key(s) with their Unraid Community forum account, also known as an Unraid.net account. Starting with this release, it will be necessary for a new user to either sign-in with existing forum credentials or sign-up, creating a new account via the UPC in order to download a Trial key. All key purchases and upgrades are also handled exclusively via the UPC. Signing-in provides these benefits: My Servers Dashboard - when logged into the forum a new My Servers menu item appears. Clicking this brings up a Dashboard which displays a set of tiles representing servers associated with this account. Each tile includes a link to bring up the servers webGUI on your LAN. Install the My Servers plugin to provide real-time status and other advanced features (see below). Notification of critical security-related updates. In the event a serious security vulnerability has been discovered and patched, we will send out a notification to all email addresses associated with registered servers. Posting privilege in a new set of My Servers forum boards. No more reliance on email and having to copy/paste key file URLs in order to install a license key - keys are delivered and installed automatically to your server.?: