Prefixing "www." now triggers security warning

Hi. If I recall correctly, we could previously prefix "www." to our FTH site address and it would work fine, but now this produces a "Privacy error" warning:
Your connection is not private
Attackers might be trying to steal your information from www.christian.toastmastersclubs.org (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID

URL visited:
www.christian.toastmastersclubs.org/
or the same with http or without "https://", which are redirected to the above.

Browser: Chrome 66.0.3359.139 on Mac. (Similar error in Firefox).

Thanks

It is not really supported or correct as the prefix in front of your website alias used as a custom domain simply because we do not have a good way to set that up with all the subdomains to point to the server.

However, at one point I had basically a "hack" in place that would strip off the www. to make it work correctly. (sort of like a redirect) It did not always work right, so I ditched it.

So, depending on who you ask here, you may get that it is not correct and not supported, or that it is just not working right now.

I may put the "hack" back, but keep in mind that it would just be fixing what you essentially entered incorrectly.