It’s very bizarre, the issue I’m having. And btw, just for others that find this post, there is a very stupid and silly way to get around this in Chrome. Basically, Chrome’s latest releases, removed the old WARNING, click this link to proceed link. But, if you click anywhere in the page (i.e. basically bring focus to the page), and then type in your keyboard “thisisunsafe”, without the quotes, the page will magically refresh and proceed.
I didn’t believe it when I saw it on another website, when the person said that’s how you get around it, but yeah, it works.
okay, back to the issue. So, what’s weird is that the let’s encrypt certificate is properly loading if I just go to the website URL of my new hestiaCP server. It loads the “We’re working on it” page. And if I check the certificate, it’s signed by R3 and Lets Encrypt. So it’s working from that perspective.
But when I try to connect to the same URL but with port 8083, it then tells me the certificate is not trusted and gives the message I put in my first post. When I check the certificate, it says its signed by HestiaCP control panel and that it’s invalid. Why is it serving up two different certificates for the same domain under the admin user. I don’t get this.