I decide to post in a new topic since this is abit old.
I am having the same problem in all of my FreePBX installations (fresh or upgraded). If I use the the certificate that is generated during installation (with CA on localhost.localdomain) it works ok. If I generate a new one with hostname the IP of the FreePBX DIstro it does not work in Chrome (Firefox is ok).
I get the following error:
Attackers might be trying to steal your information from 192.168.8.40 (for example, passwords, messages, or credit cards). NET::ERR_CERT_INVALID
192.168.8.40 normally uses encryption to protect your information. When Google Chrome tried to connect to 192.168.8.40 this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be 192.168.8.40, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.
You cannot visit 192.168.8.40 right now because the website sent scrambled credentials that Google Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later. Learn more.
As I said, if I leave the certificate that is generated during installing it works (I get the option to proceed), but if I generate my own it does not work.
Anyone can shed some light why this happens? I remember one of the developers saying that we should use localhost.localdomain due to a bug (??) in chrome but I am not 100% sure (maybe related to FREEPBX-12407 )
Using FreePBX Distro 10.13.66-17 and certificate manager 13.0.34.8
Regads,
esarant