ljm42

The upgrade script failed when extracting the downloaded zip file onto the flash drive. The flash drive could be out of space (although the script does try to detect that). It is likely that the flash drive is failing, I'd suggest making a backup and consider replacing the flash drive:
https://docs.unraid.net/unraid-os/system-administration/maintain-and-update/changing-the-flash-device/

Woah, some of your plugins are from 2020 (!!)  It is important to keep plugins up to date, it is likely that old code is messing with the display

Oh I see, you have the mover tuning plugin. It has already modified the mover script so when this installs it throws an error message about that one file.   The rest of the patches installed fine, it is safe to ignore this.
 
Need to see if there is a better way of handling issues from files that were modified by plugins

You have a very complex go script, and it looks like it messes with nginx/php config:
cp /boot/config/www.conf /etc/php-fpm.d/ I'd recommend commenting all of your go script mods and re-implementing them one at a time in Unraid 7

Docker containers are not proxied through Unraid, so Unraid's certificate has no bearing on a container's certificate. You'd want to ask for help setting up that container in the forum thread for that container.
 
 
The local TLD is used for URLS, such as:
  http://server.local
  https://server.local
The https url will use a self-signed certificate which causes browser warnings. But other than that it is fine.
 
If you had your own domain you could enter "mydomain.com" in that field and then the urls would be:
  http://server.mydomain
  https://server.mydomain
This also requires you to have DNS and provide your own certificate. More details in the docs provided earlier
 
Separate from that, once you provision a myunraid certificate you can access the server via a unique myunraid.net url using a valid certificate that we provide. 

I'd recommend following the instructions here:
  https://wiki.unraid.net/Connect#Remote_Access_.28optional.29
if you get stuck, let me know what step you are on. i.e. describe what you have done so far and what isn't working.
 
Note that some routers don't let you use different WAN and LAN ports for a port forward. In that case I'd recommend using a high random port for both.

Oooh that's exciting  
 
Tools -> PHP Settings -> PHP Info confirms that max_input_vars is at 1000

 
Edit /etc/php.ini and add a new line at the end:
max_input_vars = 1500  
And then reload PHP:
/etc/rc.d/rc.php-fpm reload  
Refresh Tools -> PHP Settings -> PHP Info to confirm max_input_vars has a new value, then try submitting the form. If PHP log still complains, try a higher number.
 
FYI, the changes to php.ini will be lost the next time you reboot
 

Aaaaand we're back: https://forums.unraid.net/topic/138392-unraid-connect-plugin-announcements/#comment-1427183

Jumbo frames are evil. Well, they cause a lot of problems anyway. Fix Common Problems will warn against them:
https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/#comment-1167702
 
To manually remove them, on the flash drive, edit config/network.cfg. Find any MTU[x] entries and change them to "1500", i.e.:
MTU[0]="1500" MTU[1]="1500" When you reboot you will be back to stock MTUs.

To be safe, make a backup of your flash drive first. Main -> Boot -> Flash -> Flash Device Settings -> Flash Backup
 
The files are stored on the flash drive in the config/wireguard directory. Delete everything in that directory (but leave the directory itself) to start over with WireGuard.
 
To do this from the web terminal type:
rm -r /boot/config/wireguard/* ( Be extremely careful typing that command! A space in the wrong place will wreak havoc. )

Flash backup runs whenever it detects a change on the flash drive, so something is updating a file on your flash drive every 15 minutes.
 
To see what it is, open a web terminal and type:
cd /boot then
git log --stat You can up/down arrow through the list, press Q to quit
 
You will probably see the same file being mentioned multiple times, please copy/paste what you see back here.

This is the problem, DNS Rebind Protection needs to be disabled.
 
Diagnostics shows that DNS requests for 192-168-4-100.hash.myunraid.net do not resolve.  It needs to resolve to 192.168.4.100 in order for the url to work.
 
Isn't there a message about this on the Settings -> Management Access page?

This is correct.  The certificate_bundle.pem cert is ONLY valid for *.myunraid.net urls. There is zero benefit to using it with other urls.  If you access the server by IP address or by name then it will use a self-signed cert.
 
 
It is fully setup. To use it, click the url starting with https://192-168... that you blanked out of the screenshot.
 
For more information, see https://docs.unraid.net/unraid-os/manual/security/secure-webgui-ssl/

Unraid 6.12.8 does not have proper support for Lifetime keys. Please upgrade to Unraid 6.12.10

Excellent. I'd suggest turning that other piece of hardware off and then see if Unraid can boot and get an IP.  If so, you'll want to dig into the config of that other system and figure out why it is claiming 10.1.10.81 when you have it set to use 10.1.10.82

Navigate to Settings -> Identification and remove any single or double quote marks from the description and model fields. This will be resolved in the next release.

Regarding the Docker security advisory, Unraid 6.12.7-rc2 is now available with Docker 24.0.9 and runc 1.1.12:
 
 

It looks like there might be some partial config files causing problems. On your flash drive, open the config/wireguard folder and delete any files/folders you find there, then refresh the page.

You are having issues with SSL and DNS.
 
After disabling SSL like JorgeB recommended you should be able to access the server via:
  http://10.10.10.10
(note: http not https)
 
Then follow the instructions here:
  https://docs.unraid.net/unraid-os/manual/security/secure-webgui-ssl/
to enable SSL with a custom certificate. Note that servername + localTLD has to be listed in the custom SSL cert. And the network has to provide a DNS entry that resolves to the server's IP.

Delete config/wireguard/wg1.* from the flash drive and then refresh the page

Ah, looks like you have a statically assigned IPv6 address. We just tracked down an issue with that, it will be fixed in the next release:
https://forums.unraid.net/bug-reports/prereleases/bugs-with-ipv6-in-6125-rc1-r2742/?tab=comments#comment-26714
 

This is really odd... Digital Ocean (our CDN) is sending the wrong file when the plugin installer tries to download it. The good news is that the SHA256 mismatch detects the wrong file and refuses to install it.
 
We are investigating, in the meantime you can manually download the file by opening a web terminal and running these commands one at a time:
mkdir -p /boot/config/plugins/dynamix.my.servers wget -O /boot/config/plugins/dynamix.my.servers/unraid-api.tgz https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/unraid-api/unraid-api-3.2.3.tgz Once that is done, you will be able to install the current Connect plugin (dated 2023.09.08.0637)

When you enable/disable SSL there is a warning in the webgui:

 
Basically, your browser is remembering that it used to use SSL for this url and it wants to keep using it. If you run into this, you need to close any other browser tabs that are pointed to the server and then clear your browser's cache. That should convince your browser to let you log in using the newly configured url.

Oh I see the issue. Edit config/ident.cfg on the flash drive. Find this line:
PORTSSL="88443" 88443 is too big, change that to a number between 1000 and 64000
 
Then run
/etc/rc.d/rc.nginx start  

It looks like DNS Rebinding is enabled for your network, so the myunraid.net url will not work.
 
Using SSH, Telnet, or a local keyboard/monitor, type:
use_ssl no  
Then you should be able to access the webgui using:
  http://192.168.50.254