Secure https:// for custom domain

I am likely experiencing the same problem discussed in this thread, which is why I am replying to this instead of posting an entirely new question. Last night, I set up noratoastmasters.org as my club's site's custom domain name (using the FreeToastHost Administrative Console). I also followed the instructions given here ( support.toastmastersclubs.org/doc/item/dns-settings-overview ) for making the appropriate changes with the domain registrar. It worked, but the several browsers that I have used to access the site after I made that change have displayed (and continue to display) messages claiming that the site is unsafe. The certificate for our site does not appear to have been updated to reflect the change. I looked at the existing certificate, and it indicates that it is associated with *.toastmastersclubs.org, which I assume was supposed to change once the custom domain name had been established.

Since about a day has passed since the custom domain name was set, I do not know whether I, too, just need to remain patient and wait a few more days for the problem to resolve itself or whether this is a case where someone will need to take action. Maybe our site suffered from the same kind of hiccup that ewbrowning encountered.

I do not know how to look into it myself, though, so if any of those of you who are experts in this kind of thing would help me out with it, I would appreciate it. Thanks!

Karl, you should be fine now... I created the missing .conf file.

I need to figure out why that is not getting created.

Yes, it looks good! Thank you, and good luck with the investigation into the cause of the missing .conf files.

It is a permissions error on the server... We will have to sort that out.
Permissions issues cause me a lot of headaches. ;-(

I set up a crontab scheduling task to regularly force the permissions to what they should be so hopefully we will not see this issue again.