Can anyone help please as I am yet to hear from Support? I connected a subdomain to funnelish. When we try to access the page
We get this standard privacy error: ‘Your connection is not private. Attackers might be trying to steal your information from **
** (for example, passwords, messages or credit cards). NET::ERR_CERT_COMMON_NAME_INVALID’
This server could not prove that it is ???.com ; security certificate is from ***.funnelish.com. This may be caused by a misconfiguration or an attacker intercepting your connection.
And if you try to push through to the site, you get this: ‘Requested host does not match any Subject Alternative Names (SANs) on TLS certificate’.
If anyone has seen this - for an extended period - or has any idea how we can solve this ourselves, please share.
Hi there! We got back on our conversation in Support! This is a copy of our response:
After looking into your case with the team, we believe that the CAA RECORDS from your HOSTINGER domain provider are indeed interfering with the generation SSL.
To resolve, follow the steps below:
Please remove all CAA RECORDS
Then please come back to Funnelish > FUNNEL SETTINGS > DOMAIN, remove and re-add your subdomain from here, just as it was before: secure.voueeskin.com and click verify
This should force our platform to re-generate the SSL.
Please allow it 5 to 10 minutes firstly, SSl can take this time to generate.
If after 10 minutes it did not propagate at all (even when checking in an incognito window), then try to also:
Add the new CAA
Record name: @
Record Value: certainly.com Record Tag: Issue/ Or Issuewild.
