• Unraid OS version 6.10.0-rc8 available


    limetech

    This release includes some bug fixes and update of base packages.  Notable changes:

    • correct device status handling for single-slot pools
    • collapse multiple underscores within nvme /dev/disk/by-id symlinks to single underscore
    • WireGuard: fixed proper handling of ipv4 + ipv6 tunnels

    • A few security related base package updates
    • Added BPF support in the Linux kernel

     

    Please note: It would be extremely helpful to us to report issues by creating separate Reports here rather than creating a reply in this topic.

     


    6.10.0 Summary of Changes and New Features

     

    As always, prior to updating, create a backup of your USB flash device:  "Main/Flash/Flash Device Settings" - click "Flash Backup".

     

    [rc3] Plugin Authors:  We patched the upgradepkg script to prevent it from replacing an installed package with an earlier version of the same package, i.e., no downgrading.  If a plugin really needs to replace a package with a downgraded version it can include the '--reinstall' option.

     

    Also be sure to check out the Dynamix File Manager plugin available now through Community Apps!

     

    UPC and My Servers Plugin

    The most visible new feature is located in the upper right corner of the webGUI header.  We call this the User Profile Component, or UPC.  The UPC allows a user to better manage their registration keys and install the optional My Servers plugin.

     

    My Servers is what we call our set of cloud-based services and features that integrate with your Unraid server(s).  After installing the My Servers plugin, you will be prompted to sign-in your server with an existing Unraid.net account, or create a new Unraid.net account.  Once installed here are some of the features of My Servers:

    • Real-time Status - with the plugin installed each server tile on the My Servers Dashboard will display real-time status such as whether the server is online or offline, storage utilization and other information. 
    • Local Access link - this is a direct link the the server webGUI on your LAN.
    • Remote Access link - if enabled, a link is displayed on the My Servers Dashboard to bring up a server webGUI remotely and over the Internet.
    • Automatic Flash Backup - every registered server is provided with a private git repo initially populated with the contents of your USB flash boot device (except for certain files which contain private information such as passwords).  Thereafter, configuration changes are automatically committed.  A link is provided to download a custom zip file that can be fed as input to the USB Flash Creator tool to move your configuration to a new USB flash device.
    • 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.

     

    Signed-in servers maintain a websocket connection to a cloud-based Lime Technology proxy server for the purpose of relaying real-time status.  Refer to the Privacy section for more information.
     

    Security Changes

    • It is now mandatory to define a root password.  We also created a division in the Users page to distinguish root from other user names.  The root UserEdit page includes a text box for pasting SSH authorized keys.
    • For new configurations, the flash share default export setting is No.
    • For all new user shares, the default export setting is No.
    • For new configurations, SMBv1 is disabled by default.
    • For new configurations, telnet, ssh, and ftp are disabled by default.
    • We removed certain strings from Diagnostics such as passwords found in the 'go' file.
    • [rc6] Changing root user password will log out all webGUI browser sessions.

     

    Virtualization

    Both libvirt and qemu have been updated.  In addition, qemu has been compiled with OpenGL support, and [rc2] ARM emulation (experimental).

     

    [rc2] To support Windows 11 which requires TPM and Secure boot, we have added TPM emulation; and, added a "Windows 11" VM template which automatically selects TPM-aware OVMF bios.  Also, here are instructions for upgrading a Windows 10 VM to Windows 11.  Special thanks to @ich777 who researched and determined what changes and components were necessary to provide this functionality.

     

    The built-in Firefox browser available in GUI-mode boot is built as an AppImage and located in the bzfirmware compressed file system image.  This saves approximately 60MB of RAM.

     

    The Wireguard plugin has been integrated into webGUI, that is, no need for the plugin.  If you had the plugin installed previously, it will be uninstalled and moved to the "Plugins/Plugin File Install Errors" page. No action is needed unless you want to press the Delete button to remove it from that page. Your WireGuard tunnels and settings will be preserved.

     

    [rc5] Resident network guru @bonienl has added the capability to bind a Wireguard virtual network interface to a docker container.  One use of this feature is to configure a Wireguard-enabled VPN which may then be exclusively used by that container, while you main server makes use of the normal LAN network interface.  Please refer to this post for additional details.

     

    Simplified installation of the Community Apps plugin.  The webGUI automatically includes the Apps menu item, and if CA is not already installed, the page offers an Install button.  No need to hunt for the plugin link.

     

    [rc3] Moving to Let's Encrypt wildcard SSL certificates. 

    Starting with this release, we no longer issue new single-host SSL certificates (which we're calling legacy certificates).  Instead, all new Unraid.net SSL certificates are wildcard certificates (still provided by Let's Encrypt). 

     

    The URL used to access your server making use of a wildcard certificate has this form:

    • https://[lan-ip].[hash].myunraid.net

    where,

    • [lan-ip] is your severs LAN IP address with dots changed to dashes
    • [hash] is a 40-character hex string (160 bits) unique to this server (and different from similar [hash] in legacy certificates)

    example:

     

    We added a new DDNS server which listens at "myunraid.net".  This server extracts [lan-ip] from the domain name and returns the IP address where the dashes are changed back into dots.  There are several benefits to this approach for both our users and for us:

    • Eliminates DNS propagation delays when you first provision a certificate or when a server LAN IP address (or WAN IP address) changes.  Since the domain name includes the IP address, any IP address change also changes the domain name, hence will not be contained in any intermediate DNS cache.  We also changed the TTL from 1 hour to 7 days further reducing overhead and alleviating issues where someone's internet goes down for brief periods.
    • There is no longer a requirement for the server to actively update a DDNS server.
    • Improves privacy because your remote access WAN IP address can't be determined by simply prepending "www" to your local access URL.
    • Moves DNS functionality off the 'unraid.net' domain and isolates it on 'myunraid.net' domain.

     

    In previous releases code that provisions (allocates and downloads) an Unraid.net SSL certificate would first test if DNS Rebinding Protection was enforced on the user's LAN; and, if so, would not provision the certificate.  Since there are other uses for a LE certificate we changed the code so that provision would always proceed.  Next, we changed the logic behind the Auto selection of "Use SSL/TLS" setting on the Management Access page.  Now it is only possible to select Auto if both a LE certificate has been provisioned and DNS Rebinding Protection is not enforced.  This is a subtle change but permits certain My Servers features such as Remote Access.

     

    Upon upgrading, you will need to modify any server bookmarks with the new the URL.  Alternately, if you have installed the My Servers plugin, a local access link is included for each server on your Dashboard.  If you have not installed My Servers plugin, since there is no DDNS update daemon, we recommend setting up either a static DHCP lease, or assign a static IP address for your server.  Finally, we have set up nginx such that the URL's:

    • http://<server-name>.<local-tld>/

    or

    • https://<server-name>.<local-tld>/

    will redirect to https://[lan-ip].[hash].myunraid.net

     

    More information including use cases may be found in Documentation here.

     

    Linux Kernel

    Upgrade to [rc4] Linux 5.15.x kernel which includes so-called Sequoia and Dirty Pipe vulnerability mitigations.

     

    In-tree GPU drivers are now loaded by default if corresponding hardware is detected:

    • amdgpu
    • ast
    • i915
    • radeon

     

    These drivers are required mostly for motherboard on-board graphics used in GUI boot mode.  Loading of a driver can be prohibited by creating the appropriate file named after the driver:

    echo "blacklist i915" > /boot/config/modprobe.d/i915.conf

    Alternately, the device can be isolated from Linux entirely via the System Devices page.  Note that in Unraid OS 6.9 releases the in-tree GPU drivers are blacklisted by default and to enabling loading a driver you need to create an empty "conf" file.  After upgrading to Unraid OS 6.10 you may delete those files, or leave them as-is.  This change was made to greatly improve the Desktop GUI experience for new users.

     

    Added support for Intel GVT-g, which lets you split your Intel i915 iGPU into multiple virtual GPUs and pass them through to multiple VMs, using @ich777's Intel-GVT-g plugin.

     

    Added support for gnif/vendor-reset.  This simplifies @ich777's AMD Vendor Reset plugin which permits users to get their AMD video cards to reset properly.

     

    [rc2] Added so-called "add-relaxable-rmrr-5_8_and_up.patch" modified for our kernel
      https://github.com/kiler129/relax-intel-rmrr/blob/master/patches/add-relaxable-rmrr-5_8_and_up.patch

    Thanks to @ich777 for pointing this out.

     

    [rc2] Enabled additional ACPI kernel options
    [rc2] Enabled TPM kernel modules (not utilized yet) - note this is for Unraid host utilizing physical TPM, not emulated TPM support for virtual machnes.

    [rc4] Updated out-of-tree drivers

    [rc5] Support Realtek RTL8152/RTL8153 Based USB Ethernet Adapters

     

    Base Packages

    Virtually the entire base package set has been updated.

     

    [rc2] For SMB: Samba version 4.15 SMB3 multi-channel is no longer marked "experimental", however is disabled by default.  This may be enabled on the Settings/SMB Settings page.  Some users have reported issues with SMB3 multi-channel in conjunction with certain network bond configurations.

     

    [rc2] Per request we added the mcelog package.  With inclusion of this package, if you have an AMD processor you may see this error message in the system log:

    mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead.

    We're not sure what to make of this.  It appears mcelog is being deprecated in favor of rasdaemon.  This is something we need to research further.

     

    Other improvements available in 6.10, which are maybe not so obvious to spot from the release notes and some of these improvements are internal and not really visible:

     

    Event driven model to obtain server information and update the webGUI in real-time

    • The advantage of this model is its scalability. Multiple browsers can be opened simultaneously to the webGUI without much impact
    • In addition stale browser sessions won't create any CSRF errors anymore
    • People who keep their browser open 24/7 will find the webGUI stays responsive at all times
    • [rc3] Consistent state information is maintained across all browser instances open to a particular server

     

    Docker labels

    • Docker labels are added to allow people using Docker compose to make use of icons and GUI access
    • Look at a Docker 'run' command output to see exactly what labels are used

     

    Docker custom networks

    • A new setting for custom networks is available. Originally custom networks are created using the macvlan mode, and this mode is kept when upgrading to version 6.10
    • The new ipvlan mode is introduced to battle the crashes some people experience when using macvlan mode. If that is your case, change to ipvlan mode and test. Changing of mode does not require to reconfigure anything on Docker level, internally everything is being taken care off.

     

    Docker bridge network (docker0)

    • docker0 now supports IPv6. This is implemented by assigning docker0 a private IPv6 subnet (fd17::/64), similar to what is done for IPv4 and use network translation to communicate with the outside world
    • Containers connected to the bridge network now have both IPv4 and IPv6 connectivity (of course the system must have IPv6 configured in the network configuration)
    • In addition several enhancements are made in the IPv6 implementation to better deal with the use (or no-use) of IPv6

     

    Plugins page

    • The plugins page now loads information in two steps. First the list of plugins is created and next the more time consuming plugin status field is retrieved in the background. The result is a faster loading plugins page, especially when you have a lot of plugins installed

     

    Dashboard graphs

    • The dashboard has now two graphs available. The CPU graph is displayed by default, while the NETWORK graph is a new option under Interface (see the 'General Info' selection)
    • The CPU graph may be hidden as well in case it is not desired
    • Both graphs have a configurable time-line, which is by default 30 seconds and can be changed independently for each graph to see a longer or shorter history.
    • Graphs are updated in real-time and are useful to observe the behavior of the server under different circumstances

     

    Scheduler Improvements

    • [rc3] You can now split a parity check into smaller pieces and let it run over multiple days or weeks.  For example a check can be performed in a time frame of 01:00am to 06:00am for several days in a row until it is completed.  This way a long parity check won’t interfere with the normal day activities, like watching a movie.
    • [rc3] Added ability to schedule pool 'balance' and 'scrub' operations and calculate whether a full balance is recommended.

     

    Other Changes

    • We switched to a better-maintained version of the WSD server component called wsdd2 in an effort to eliminate instances where the wsd daemon would start consuming 100% of a CPU core.
    • Fixed issue where you couldn't create a docker image on a share name that contains a space.
    • Fixed issue where 'mover' would not move to a pool name that contains a space.
    • Fixed issue in User Share file system where permissions were not being honored.
    • We increased the font size in Terminal and [rc2] fixed issue with macOS Monterey.  Terminal font size is configurable via Settings/Display Settings page.
    • [rc2] Fixed jumbo frames not working.
    • [rc2] sysctl: handle net.netfilter.nf_conntrack_count max exceeded (increase setting to 131072) - hattip to Community Member @DieFalse

    • [rc2] Mover will create '.partial' file and then rename upon completion.

    • [rc2] Enabled NFSv4 support.

    • [rc2] Check bz file sha256sums at boot time.

    • [rc3] Fixed bug found by @thohell where md_sync_limit was not being honored to limit stripe_head cache usage when other I/O is active.  The effect of this fix is to drastically slow down parity operations if other I/O is happening (such as streaming a video).  Throttling of parity sync operations can be adjusted by changing the 'Settings/Disk Settings/Tunable (md_sync_limit)' value.

    • [rc3] Fixed btrfs pool device replace corner cases.  Important note: if you 'unassign' a device from a btrfs multiple-device pool, and that device is still physically present, upon array Start we will erase the LUKS header on the device if present, and delete the partition structure, thereby effectively erasing all the data contained on the device.  This is necessary in order to convince btrfs to no longer use the device and to free it for assignment to another pool.

    • [rc3] For cookies managed by webGUI, changed sameSite cookie attribute from 'strict' to 'lax'.  This change was made to solve an issue with Terminal window not opening in Safari.

    • [rc5] Fixed a bug where replacing a device in a multiple-device btrfs pool would still tag the old device as missing.

    • [rc5] Fixed an issue where hot plugging a device in a server with spun-down SAS drive(s) could cause the SAS drive(s) to appear unassigned.

    • [rc5] Fixed an issue where the server would disappear from Windows Network after docker and/or VM startup.

    • [rc5] Fixed md/unraid driver regression which would confuse XFS, making it think an online shrink had occurred.

    • [rc5] Fixed: Prevent Unraid from hanging when the array is stopped, while VMs are in paused or suspended state.

    • [rc6] Added ServerChan and Pushplus notification agents, thanks to @ludoux

    • Numerous other small bug fixes and improvements.

     

    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

     


    Version 6.10.0-rc8 2022-05-10 (vs. 6.10.0-rc7)

    Base distro:

    • libxml2: version 2.9.14 (CVE-2022-29824)
    • openssl: version 1.1.1o (CVE-2022-1292)
    • openssl-solibs: version 1.1.1o

    Linux kernel:

    • Linux 5.15.38-Unraid
    • enable BPF kernel options (user request):
      • CONFIG_BPF_SYSCALL: Enable bpf() system call
      • CONFIG_BPF_JIT: Enable BPF Just In Time compiler
      • CONFIG_BPF_JIT_ALWAYS_ON: Permanently enable BPF JIT and remove BPF interpreter
      • CONFIG_NET_CLS_BPF: BPF-based classifier
      • CONFIG_NET_CLS_ACT: Actions
      • CONFIG_NET_ACT_BPF: BPF based action
      • CONFIG_IKHEADERS: Enable kernel headers through /sys/kernel/kheaders.tar.xz
      • CONFIG_NET_SCH_SFQ: Stochastic Fairness Queueing (SFQ)
      • CONFIG_NET_ACT_POLICE: Traffic Policing
      • CONFIG_NET_ACT_GACT: Generic actions
      • CONFIG_GACT_PROB: Probability support
      • CONFIG_NET_SCH_INGRESS: Ingress/classifier-action Qdisc
      • CONFIG_CGROUP_BPF: Support for eBPF programs attached to cgroups

    Management:

    • emhttpd: correct device status handling for single-slot pools
    • emhttpd: collapse multiple underscores within nvme /dev/disk/by-id symlinks to single underscore
    • webgui: WireGuard: fixed proper handling of ipv4 + ipv6 tunnels
    • webgui: Font files update
      1. clear-sans --> source sans pro
      2. bitstream --> source code pro
    • webgui: Remove deprecated font extensions: eot, svg, ttf
    • webgui: Cleanup styles folder
    • webgui: Update css files to use woff and woff2 formats only
    • webgui: Fixed balance/scrub schedule not saved when device name has "-" in it
    • webgui: Fix side bar of themes azure/gray in firefox
    • webgui: chore(upc): ENOKEYFILE2 message translation
    • Like 7
    • Thanks 1



    User Feedback

    Recommended Comments



    I just upgraded, and once again some of my containers were not starting (I reported a bug related to this container permission issue) and now also the NVIDIA driver plugin and the Dynamix wireguard plugin are showing errors:

    image.thumb.png.82281d74cedcfc74044b01591473c740.png

    Link to comment
    28 minutes ago, bonienl said:

    Please read the release notes about obsolete plugins.

    THat explains Wireguard, howabout NVIDIA?

    Link to comment
    Just now, huntastikus said:

    THat explains Wireguard, howabout NVIDIA?

    The nvidia plugin needs to be updated because of the newer kernel version in rc8, this should be an automated process when the OS update is initiated. Did you see any notifications about plugin updates, and especially notifications telling the updates are completed?
     

    • Thanks 1
    Link to comment
    1 minute ago, bonienl said:

    The nvidia plugin needs to be updated because of the newer kernel version in rc8, this should be an automated process when the OS update is initiated. Did you see any notifications about plugin updates, and especially notifications telling the updates are completed?
     

    I will watch out for it during the next RC upgrade.

    Link to comment

    I spy with my little eye ... a little typo in there since a couple of RCs 😉

    2022-05-10 21_08_18-Greenshot.png

    • Thanks 1
    • Haha 1
    Link to comment

    I'm having issues with Wireguard. (im using Remote Tunneled Access) When docker is off I am able to access my home network and the internet. When I enable Docker I lose access to navigate to internet websites, however, I can still access my internal network. Not a huge issue but definitely a regression.

    Link to comment

    Did you make changes to the tunnel or is this happening with the original tunnel config?

     

    Please make a seperate report, so we can track this.


     

    Link to comment
    17 hours ago, huntastikus said:

    I will watch out for it during the next RC upgrade.

    The build process is automated as @bonienl pointed out but you have to give my server some time to actually build the updated drivers for the new Kernel version.

    Anyways you should get messages that a update is in progress and to wait with the reboot until everything is done, if you get a error message that usually indicates that the plugins aren't built yet.

    The messages should look something like this:

    image.png.de912436f8b74deef2407b2383e2ea0f.png

    In this case there was an error with ZFS, this indicates that the plugins aren't built yet or create a post in the appropriate plugin support thread.

    If there was no error you will get green notifications that the plugin download succeeded.

     

    The build itself takes about 40 minutes (Nvidia, DVB, OpenRGB,...) where it can take about 20 minutes that my server picks up the new Unraid version, so to speak I would recommend to wait at least for about an hour if not better two hours so that everything is built.

    Link to comment
    7 hours ago, bonienl said:

    Did you make changes to the tunnel or is this happening with the original tunnel config?

     

    Please make a seperate report, so we can track this.


     


    I didn’t make any changes to the tunnel after upgrading. I also noticed a little weirdness on 6.10-rc7 the only major change I made was switching to using the ipvlan instead of macvlan because I was experiencing a lot of hard crashing issues on 6.9.2. I would be happy to create a separate issue and troubleshoot.  @bonienl can you remind me again where I make the report? Thanks!

    Link to comment

    You can open a new topic here in this section, bug reports - prereleases.

    Can you include your diagnostics and WG config file (remove the private and public key values).

    Thx

     

    Link to comment

    Updated from RC7. No issue so far with VPN (wireguard) or any of the docker except:

     

    Upon update the reboot wasn't successful, the system was hanging (I don't have any error/info as no monitor is attached). After 552 secs, I did a normal power down (pressing the power button and the system immediately shut down, like when no boot device found) and restart, one of the btrfs disk cache was missing (again as I did have the same issue upon reboot on the rc4/5).

    I shut down, changed sata port on the card and reboot. Same issue so I removed the device as the cache was raid 1 anyway so no data loss but I am not sure if the problem is my disk or the update as, as stated before, I had the issue before.

    The disk shows correctly under unassigned devices now that it has been removed from the cache pool. The only SMART error I have on the drive is the UltraDMA CRC that occurred after I removed the drive.

     

    I don't have diagnostics as I did 2 reboot after the changes and forgot to save what happened, however no info/issue in the system log as far as I remember.

    Hopefully the explanation makes sense. If not please let me know and I try to rephrase it.

    Link to comment

    I looked for documentation about the about the scrub and balance schedulers that were recently introduced for btrfs volumes. What kind of scrub is done on a schedule? Is it a correcting one or a read-only one, given that there's a choice when a scrub is run manually? What kind of balance is done on a schedule? Is it a full one or one based on partially filled extents? Does the presence of the Block group usage parameter imply that it's the latter?

     

    1170632483_ScreenShot2022-05-11at19_03_13.png.bb919ce915751bddf6389b2cb28fbfd1.png

    Link to comment
    SavellM

    Posted (edited)

    I updated to RC8 today and my NVIDIA Quadro P2000 is no longer showing in the NVIDIA app.

    Tried to restart a few times and no change.

     

    image.thumb.png.5e11edf4eb7217697466950b9d21ed21.png

    I see its still shown but NVIDIA app no longer shows it:

     

     

    Is there something that needs to be done/reset for it to show back?

    image.thumb.png.5a7f21720a16198f7be9fceaaaadc51d.png

     

    Roll back to RC7 and its back and I can see my Installed GPU

     

    *EDIT* Did another upgrade and this time was successful... weird 

    Edited by SavellM
    • Like 1
    Link to comment
    uncle

    Posted (edited)

    After updating, i am having the problem that i get "404 Not Found nginx" error when i want to get on the Unraid Server GUI but with the new "local.IP".hash.myunraid.net it works (only local).

    tower.local ; local ip etc. are not working => MyServers Plugin is up to date

     

    I cant reach it outside my local network and already deactivated docker to check if ports are crossing.

    Swag still works and is reachable from the outside with my docker containers.

     

    Does anyone got that problem too or knows a solution? Otherwise i am going to restore my backup.

     

    Diagnostics will be shortly uploaded.

     

    EDIT: diagnostics uploaded

    uncle-diagnostics-20220512-0220.zip

    Edited by uncle
    Link to comment
    9 hours ago, SavellM said:

    I updated to RC8 today and my NVIDIA Quadro P2000 is no longer showing in the NVIDIA app.

    Please create a post in the support thread from the plugin itself if you got issues with it and attach your Diagnostics.

     

    Do you got any messages like described here while upgrading:

     

    Link to comment
    On 5/11/2022 at 7:31 PM, John_M said:

    What kind of scrub is done on a schedule? Is it a correcting one or a read-only one, given that there's a choice when a scrub is run manually?

    Read-only, though arguably it should be correcting by default.

     

    On 5/11/2022 at 7:31 PM, John_M said:

    What kind of balance is done on a schedule? Is it a full one or one based on partially filled extents? Does the presence of the Block group usage parameter imply that it's the latter?

    The latter, block group usage is the value used in -dusage, it means that it will only balance data blocks groups with usage under the set percentage, metadata is not balanced as it's usually not needed, or even recommended unless there's a specific reason to do it.

     

    A few more observations:

     

    50% should be a good default for most use cases, pools that have many extents per block group with frequent changes/deletes to some might need a higher value to keep a good data usage ratio, for most cases anything above 75% should be fine, it's this value:

     

    imagem.png.e01fad072af352d61bdccbf541a7a50f.png

     

    So check that value after the scheduled balance runs, once at month should be enough for most cases, and if the usage ratio drops below 75% you can increase the "block group usage" value a little, usually no need to go very high, the higher it's set the more data will be balance resulting in unnecessary wear for flash devices, with a value of 100 all data will be balanced, i.e. re-written, same as a full balance, except full balance also balances the metadata.

     

    Also note that the usage ratio by itself is not critical, it should be viewed in conjunction with the available unallocated space, as long and there's some it's not a problem, but it's good practice to keep it under control, if the pool is run close to full, or frequently filled up it might be good to aim for a higher data usage ratio.

     

     

    • Thanks 1
    Link to comment
    17 hours ago, uncle said:

    After updating, i am having the problem that i get "404 Not Found nginx" error when i want to get on the Unraid Server GUI but with the new "local.IP".hash.myunraid.net it works (only local).

    tower.local ; local ip etc. are not working 

     

    Thanks for the diagnostics! Although really this would have been better as its own post, now our conversation is at risk of being lost in the noise

     

    On Settings -> Management Access, your "Use SSL/TLS" setting is set to "auto". This is the most secure mode, where the system will only respond to https using the myunraid.net certificate. 

     

    These http urls will redirect to the secure https myunraid.net url:
      http://ipaddress 
      http://tower.local 

     

    If you want the system to respond to these:
      https://ipaddress 
      https://tower.local
    then you can change "Use SSL/TLS" to "yes" instead of "auto"

     

    The different options are described more here:

      https://wiki.unraid.net/Manual/Security#Securing_webGui_connections_.28SSL.29

    Although I'm thinking about adding a section that talks about redirects.

     

    17 hours ago, uncle said:

    I cant reach it outside my local network and already deactivated docker to check if ports are crossing.

     

    For privacy, Remote Access information is not in the diagnostics, so I can't tell how you are configured. Go to Settings -> Management Access -> My Servers and confirm Remote Access is enabled and on the expected port. Then press the Check button and let me know what it says.

     

    Then go to the My Servers dashboard from a computer that is not on your network and click the Remote Access url. It should pull up the login page. If there are issues please give me the error message.

     

    If there were issues with any of the above steps please open a web terminal and provide the output from:

    php /usr/local/emhttp/plugins/dynamix/include/UpdateDNS.php -v

    (it is anonymized)

    • Like 1
    Link to comment
    uncle

    Posted (edited)

    3 hours ago, ljm42 said:

    If you want the system to respond to these:

      https://ipaddress 
      https://tower.local
    then you can change "Use SSL/TLS" to "yes" instead of "auto"

     

    That helped a lot. Now it works!! Many thanks!!

     

    I have a port directing to the Unraid GUI with DDNS and setting it to "yes" was the solution.

     

    3 hours ago, ljm42 said:

    The different options are described more here:

      https://wiki.unraid.net/Manual/Security#Securing_webGui_connections_.28SSL.29

    Although I'm thinking about adding a section that talks about redirects.

     

    That would be nice.

    I wasnt aware that its a big diffarence between setting SSL to "auto" or "yes". It might help other people.

     

    3 hours ago, ljm42 said:

    If there were issues with any of the above steps please open a web terminal and provide the output from:

    php /usr/local/emhttp/plugins/dynamix/include/UpdateDNS.php -v

    (it is anonymized)

     

    In the output it says "192-168-178-43.hash.myunraid.net does not resolve to an IP address, it should resolve to 192.168.178.43" probably thats why i got the 404 error in the browser. I am not using myunraid.net so its not important for me to work. (output is in the spoiler)

     

    Spoiler

    (Output is anonymized, use '-vv' to see full details)
    Unraid OS 6.10.0-rc8 with My Servers plugin version 2022.05.10.1726
      Signed in to Unraid.net as uncle04
    Use SSL is yes
      Rebind protection is disabled for myunraid.net
    Local Access url: https://uncle.local
    ⚠️  192-168-178-43.hash.myunraid.net does not resolve to an IP address, it should resolve to 192.168.178.43
    Remote Access url: https://[redacted].hash.myunraid.net:[redacted]
      [redacted].hash.myunraid.net resolves to [redacted]

    Request:
    {
        "keyfile": "[redacted]",
        "plgversion": "2022.05.10.1726",
        "internalhostname": "uncle.local",
        "internalport": "443",
        "internalprotocol": "https",
        "remoteaccess": "yes",
        "servercomment": "uncle server",
        "servername": "uncle",
        "internalip": "192.168.178.43",
        "externalhostname": "*.hash.myunraid.net",
        "externalport": "[redacted]",
        "externalprotocol": "https"
    }
    Response (HTTP 200):
    []
    success

     

    Thanks for helping again!! :)

    Edited by uncle
    Link to comment

    After updating from 6.10.0-rc5 Plex HW transcoding stopped working on 12th Alder Lake (i5-12400T - only P-cores)

     

    I did exact same steps as on rc5:

    1. Created /boot/config/modprobe.d/i915.conf and added blacklist i915

    2. Rebooted

    3. Installed Intel GPU TOP plugin
    4. Passed /dev/dri into Plex docker container

    I have no idea what was changed but after rollback to rc5 everything is working fine again. Any ideas?

    Edited by omygoodness
    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.