mans_

root@Marcus:~# cat /tmp/gpudata0000\:00\:02.0 {"period":{"duration":1014.881557,"unit":"ms"},"frequency":{"requested":0,"actual":0,"unit":"MHz"},"interrupts":{"count":0.985337,"unit":"irq\/s"},"rc6":{"value":100,"unit":"%"},"power":{"GPU":0,"Package":11.831377,"unit":"W"},"engines":{"Render\/3D":{"busy":0,"sema":0,"wait":0,"unit":"%"},"Blitter":{"busy":0,"sema":0,"wait":0,"unit":"%"},"Video":{"busy":0,"sema":0,"wait":0,"unit":"%"},"VideoEnhance":{"busy":0,"sema":0,"wait":0,"unit":"%"}},"clients":[]}root@Marcus:~#

+1

Why Unraid Should Support Passkeys for GUI LoginUnraid has grown far beyond a hobby NAS—it’s now used for home labs, small businesses, and mission-critical self-hosting. The login experience should reflect that maturity. Adding passkey (WebAuthn/FIDO2) support to the Unraid web GUI—similar to Tailscale’s username@passkey flow—would be a major step forward. Here are reasons this feature deserves priority: 1. Massive Security Upgrade (Phishing-Resistant by Design)Passkeys eliminate shared secrets entirely: No passwords to steal, reuse, brute-force, or phish Resistant to credential replay and MITM attacks Immune to weak or reused admin passwords For a system that often runs root-level services, this is a meaningful security improvement—not just convenience. 2. Removes the Weakest Link: PasswordsEven strong passwords are: Hard to manage Often reused Frequently stored insecurely in browsers or notes Passkeys leverage: Hardware security keys TPM / Secure Enclave Biometric unlock (Face ID, Touch ID, Windows Hello) This aligns Unraid with modern authentication best practices. 3. Faster, Cleaner Login ExperienceA passkey login is: One click / biometric prompt No typing (great for mobile and tablets) No password managers required For admins who log into Unraid frequently, this saves time every day. 4. Perfect Fit for Local & Remote Admin AccessUnraid GUIs are often accessed: Over LAN Via VPN (Tailscale, WireGuard) Through reverse proxies Passkeys work seamlessly across all of these scenarios and bind authentication to the real origin, preventing fake login pages. 5. Matches the Modern Stack Unraid Users Already UseUnraid users already rely on: Tailscale Cloudflare GitHub Google / Apple ecosystems All of these platforms already support passkeys. Unraid adopting the same standard would feel natural and expected. 6. No Cloud Dependency RequiredThis can be implemented using: Standard WebAuthn APIs Local credential storage Optional fallback to password login No requirement for Unraid accounts, external identity providers, or always-online validation. 7. Backward Compatible & OptionalPasskeys don’t need to replace passwords: Enable per user Allow mixed authentication (password + passkey) Ideal for gradual adoption Admins who want passwords can keep them. Power users can upgrade. 8. Positions Unraid as a Forward-Looking PlatformAdding passkeys would: Signal strong security leadership Differentiate Unraid from other NAS solutions Reduce support issues related to compromised credentials This is the kind of feature users brag about. Suggested UX Conceptunraid_admin@passkey → Browser / OS prompts for biometric or security key → Instant login Simple. Secure. Modern. Bottom line: Passkey support isn’t just a nice-to-have—it’s the future of authentication. Implementing it in the Unraid GUI would significantly improve security, usability, and user trust while keeping Unraid competitive with modern infrastructure tools like Tailscale. This is a feature worth building.

@SimonF Please let me know if you need more info !

The power draw bar was perfectly working on 7.1.4. Now it is all white again on 7.2.3. I had the same bios for both the versions. Clearly this is not my bios, can you please look into it and fix it when you get time? Thank you for your work !

I updated from 7.1.4 to 7.2.3 and the plugin "check for update" gives the error Checking connectivity ... No response, aborting! I do have controld.com DoH (ads+malware) filter which worked perfectly for unraid versions 6.xx.x to 7.1.4 where the plugin update will give no error like above. Now only if I turn off this DoH resolver, my updates work in 7.2.3. "Check for updates" doesn't work on the docker tab too. I am trying to understand what changes were made in 7.2.3 and fix them? marcus-diagnostics-20251223-1414.zip

Hi ! I looked throughout the internet and wasn't able to find anyone having a same idea as me to use 2xhdd on the PSU side. Can you please tell me what you used to mount one top of the other?

@binhex doesnt connect to VNC on unraid 7.1.2. what is the fix?

@SimonF I have a 14900K and the black bar for power draw is not seen, it is just white. All options enabled on the plugin settings and on the latest plugin version. Unraid version is 6.12.15. Active apps icon is also missing. Its actually jellyfin. Prior to the update, it was working properly.

Then where only will we use the ipv4 of the jellyfin container? My docker containers dont have ipv6 which is the issue here. I use bridge network and it doesn't work. It still goes to the unraid webui this was your initial advice

@JorgeB Hi, I saw you commented on another post related to ipv6. Can you please help my containers get ipv6 via dhcpv6 or any other viable method for me? I am not sure, but this post here says to use macvlan for dhcp. Please support, thank you!

I can connect to my unraid login page via jellyfin.domain_name.com, but not jellyfin itself. My caddy config is as follows: jellyfin.domain.xyz, www.jellyfin.domain.xyz { reverse_proxy http://172.17.0.12:8096 } 172.17.0.12:8096 is internal jellyfin ip which is running on docker bridge network

Can you please tell me how? I can follow instructions well. I have a domain and setup nginx. Please, thank you!

Hi unraid team! I have tried and searched for several days and I am unable to figure out how to do the mentioned in the title. I have even reached out on the discord and was told the user base is very small and asked me to move to the forums. REASON: Tailscale does not stream jellyfin because I am under CGNAT. I am forced to use tailscale DERP severs. I have tried several times, and it doesn't work like it does for others in other parts of the world. According to https://tailscale.com/kb/1232/derp-servers, "Tailscale runs DERP relay servers distributed around the world to link your Tailscale nodes peer-to-peer as a side channel during NAT traversal, and as a fallback in case NAT traversal fails and a direct connection cannot be established." So ipv6 is my only option and reverse proxy on it. SETUP DETAILS: I can confirm I am able to connect to the unraid gui via http ipv6 remotely after setting ipv4+ipv6 in unraid gui and some settings in my OpenWrt router. I followed this guide and changed to macvlan -- unraid guide link When I inspect docker custom network bond0 it has no ipv6 enabled by default. I have no idea why this will be the case? I believe because of this bond0 setting when assigned to a container, is not getting ipv6 via dhcp. And for bridge it is enabled but it is not macvlan driver. root@Marcus:~# docker inspect network bridge [ { "Name": "bridge", "Id": "67da0ca0768313c1d78b6fcc9a2e0155dd2637ff448633d36d94f3895865ac42", "Created": "2025-04-06T15:31:37.995198845+05:30", "Scope": "local", "Driver": "bridge", "EnableIPv6": true, "IPAM": { "Driver": "default", "Options": null, "Config": [ { "Subnet": "172.17.0.0/16", "Gateway": "172.17.0.1" }, { "Subnet": "fd17::/64", "Gateway": "fd17::1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { #redacted rest of the result root@Marcus:~# docker inspect network bond0 [ { "Name": "bond0", "Id": "12d68ab11cc0c49db92450d6c1643ee0619eb7e65598992782278c6dc65a2f79", "Created": "2025-04-06T15:31:38.99571313+05:30", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.86.0/24", "Gateway": "192.168.86.1", "AuxiliaryAddresses": { "server": "192.168.86.52" } } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": { "parent": "vhost0" }, "Labels": {} } ] Error: No such object: network root@Marcus:~# EXPECTED RESULT: I have dhcpv6 setup on my openwrt and want each docker container to receive ipv6 via dhcpv6. From there, I can allow firewall rule to access it. As I confirmed previously, I am able to connect to unraid gui via ipv6. I wish to get the same result for each docker container, and I believe macvlan will help me achieve this. Kindly, please provide me with the steps involved in doing this. Thank you!

So intel will support 12th gen alder lake but not 13th & 14th gen raptor lake? Or will 13th & 14th be supported because they essentially have the same iGPU?