limetech

Please update to 6.10 and if it's still broken then post diagnostics.zip.

Nice catch, thanks.

I added nfsv4 support in kernel starting with 6.10-rc2. nfsv3 still works and the v4 protocol is definitely enabled but I can't get a client (another Unraid server) to mount a share using v4 protocol. Spent a couple hours on it this morning but I have no time to spend more time on it now. If someone wants to test this and let me know what has to happen, then we can add to 6.10 release. But please post in Prerelease Board.

I was seeing similar messages in libvirtd.log and fixed the issue in next release; however, i wasn't seeing them continuously output filling the log. Please retest once new release is posted (soon).

Changed Status to Retest

If possible please reboot in 'safe mode' and see if issue persists. This to rule out an incompatible plugin.

Changed Status to Closed Changed Priority to Other

I'll add it back, don't want to get between anyone and their WINE

Ok. I didn't know why this was setting was there. Are there really 32-bit dockers out there?

The 'link' was there to support cases where SSL/TLS was set to 'No' or 'Yes' and then you Provisioned a Lets Encrypt certificate. The link is the URL to your server using https://<hash>.unraid.net and is useful to switch to using that URL or save as a bookmark. For next release, this was changed a little where 'link' is removed and the 'Certificate subject' is made into a link.

Just the kernel .config file from whichever one works for you. I want to see how hey defined acpm-related kernel config settings. Your syslog from diags report that ACPM is enabled...

Do you need the "pcie_aspm=force" kernel parameter? There is this warning: WARNING: Forcing ASPM on may cause system lockups. Also it would be helpful to post the kernel .config file of your Ubuntu install.

If you can't upgrade how do you know this?

This happens when 'bzmodules', which is a compressed file system image, cannot be mounted from the USB flash device. Probably the file is corrupted. I suggest restoring your flash backup via the USB Creator tool, which will also ensure the flash file system is not corrupted, boot and try the update again.

There's nothing obvious in the system log except Nerdpack is installing down-rev packages. Maybe remove that plugin or try running in 'safe mode'.

Modern browsers these days ignore the OS hosts file, at least on Windows.

With SSL:Yes it will generate and use a self-signed cert and respond on URL: https://<server-name>.<local-tld>/ If a certificate_bundle.pem file is present it will use that cert and also respond on URL: https://<subject>/ where <subject> is the Common Name in the certificate. In other words it will respond on two different URL's using two different certs. If you set SSL:Auto then it will only respond on URL: https://<subject>/ and these URL's all 302-redirect to https://<subject>/ http://<ip-address>/ https://<ip-address>/ http://<server-name> https://<server-name>/ https://<server-name>.<local-tld>/ Of course, if non-standard http and/or https ports are defined, those ports are included in those URL's. Note that with SSL:Auto if your DNS server cannot resolve <subject> then you can be locked out of the webGUI.

That should work. If this is a custom self-signed cert we have made a change in rc2 to recognize that.

Buggy bios is buggy.

Use "Auto" setting. This setting is slightly different in 6.10 than in previous releases. "Auto" means use the certificate defined in the file: /boot/config/ss/certs/certificate_bundle.pem The "Provision" button will download a LE cert to that file, but instead of doing that you can upload your own cert there. The code will then check that DNS Rebinding protection is not active on your LAN and that the Subject of the certificate resolves via your DNS server. If both those checks pass then you can select "Auto". Once selected, now the webGUI will only answer up to this URL prefix: https://<subject>/

Thank you @bonienl I updated the OP with this text.

If you move it past that include of smb-shares.conf then any settings will apply to the last share defined in smb-shares.conf not globally.

Sure we can make that change for rc2

Try clearing your browser cache.

No that's a bug in our release process. Fixed now, please try again.