fl0at

Creating a certificate_bundle.pem in /boot/config/ssl/certs and using a wildcard certificate will result in a Nginx configuration error in /etc/nginx/conf.d/emhttp-servers.conf It looks like that the common name of the cert is being used in the configuration, around like 40, in this section: # # Redirect http requests to https # listen *:80 default_server; listen [::]:80 default_server; return 302 https://*.example.com:443$request_uri; Changing this from https://*.example.com to https://subdomain.example.com and running nginx -s reload will fix the issue. The issue is that port 80 redirects result in a corrupted content error in FireFox. Have not tested other browers.

Reproduce: Management -> Settings -> SMB -> Enable: Yes (Active Directory) -> Apply Scroll to Active Directory Settings. Join domain. RDP to AD/DC Server. If using Windows Server, run Active Directory Users and Computers (dsa.msc), select Computers, refresh and see that Unraid server is in domain joined. Return to Unraid Management -> Settings -> SMB -> Active Directory Settings -> enter domain admin password and click Leave. Page will refresh showing still joined. Return to Windows -> Active Directory Users and Computers. Refresh. Notice Unraid server is no longer in the list. Unraid server is now not domain joined, but shows as joined, until system is rebooted. Upon reboot, will show as not joined, and can now join a domain. No dockers, plugins or anything installed.

To reproduce: Management UI -> Settings -> FTP Server Set FTP server: Disabled then Apply. Status in top right should show Status: Stopped Click Dashboard then Reboot icon. Proceed. Once back up, Settings -> FTP Server, Status: Running System: Just upgraded to 6.7.0 from 6.6.6. Still in trial (28 days remaining...), active directory joined, no dockers, plugins, and one user share created. That is as far as I've gotten, except to disable FTP and then reboot due to the ugprade...