Cameron

You are getting the warning because you are accessing the website by ip address (whereas your certificate was issued to <some long hex>.unraid.net). When you try to access unRaid's webGUI from HTTP it will redirect you to <some long hex>.unraid.net where the certificate matches the domain. It looks like you are accessing unRaid's webGUI via HTTPS, so you're never redirected to the unraid domain and as such the certificate doesn't match.

Thanks for the great explanations! During my research, I read that CAs are not allowed to issue certificates to internal names or reserved ip addresses (source). So when I ping '<some random hex characters>.unraid.net' I didn't expect to see my internal ip of 192.168.x.x. I thought this wasn't allowed, or am I missing something? From my understanding, when you access `http://192.168.1.199` the web browser automatically goes to port 80 and your unraid server basically tells the browser that it doesn't do insecure connections so it redirects it to the unraid subdomain. If you manually specify the port with `https://192.168.1.199:443` the unraid server will accept the connection, however you are not redirected to the unraid subdomain so the SSL certificate provided by letsencypt (which is assigned to your specific unraid subdomain) does not look valid.