Well, this is driving me insane. I have a FreePBX box with a self signed cert. I was able to access the box fine from my Macbook with both Safari and Chrome. With Chrome, I just your standard "your connection is not private, and then the option to proceed anyway. However, a co-worker of mine needed to connect via his Windows 10 box, and he cant. from my Windows VM, neither can I. Chrome gives a "NET::ERR_CERT_INVALID" error and "You cannot visit pbx.domain.com right now because the website sent scrambled credentials that Google Chrome cannot process." with no option to proceed. That's issue number 1 that I'd like to get working.
As an alternative, FreePBX now has Let's Encrypt functionality build right into the cert manager. So, I gave that a shot. For the host name, I put in the proper DNS name of my PBX box (pbx.domain.com) An A record was already created at my registrar for this DNS name/IP. I get the error "There was an error updating the certificate: Token did not match"
Any suggestions for either problem?
Thanks!