Hi everyone,
I have a few domains on my mailinabox, some going to custom domains and other using the aliases feature to route just email.
With the new Lets Encrypt feature I provisions a list of four alias, one which later was routed to a custom domain.
Now in the past I have been able to successfully add a custom domain on the box to point to an external IP by A record to point to the IP for the www.mydomain.com and another record using CNAME for mydomain.com
I have now done so again for an additional custom domain, only difference on this occasion I had provision that TLS record on the box prior to pointing to my custom domain using Lets Encrypt.
Having waited now for DNS to propogate, i can browse to my new A recordcorrectly as www.mydomain2.com which goes to my external IP whereas mydomain2.com thinks its seeing the mailinabox IP and throws security errors in the browser
Your connection is not secure
The owner of [mydomain2.com] has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.
This site uses HTTP Strict Transport Security (HSTS) to specify that Firefox only connect to it securely. As a result, it is not possible to add an exception for this certificate.
In the advance shows
mydomain2.com uses an invalid security certificate. The certificate is only valid for the following names: mymailinabox.com
Has anyone come across this issue?
How do i remove this TLS/SSL certificate within my mailinabox as i think its being confused by my original provision.
Any guidance would be appreciated. Thanks
Tony
Learn more…