HTTPS Certificate Renewal

When I logged in as Admin to my club's (# 1861331) site today I have a message saying FreeToastHost was "unable to renew a HTTPS certificate for the custom domain of my website". The three possible causes are given as:

• DNS records are set up incorrectly
• custom domain has expired
• custom domain listed in the Admin console is no longer being used

I doubt it's #1. The site has been setup since 2011. No technical changes were made since then & definitely not in the last 12 months
I suspect it's #2. However, a check with who.is reveals the domain name expired on 12/22/2014.
It's definitely not #3. We've been using the same custom domain name for the past six years

What do I need to do to have the certificate renewed? Why would this message appear three years after the expiration date but not sooner?

Domain name please?

www.francophonebilingualtoastmasters.com

You domain is using domain forwarding and we do not support.

This is not our server IP
francophonebilingualtoastmasters.com. 599 IN A 184.168.221.27

Please set up the domain following these directions
support.toastmastersclubs.org/doc/item/dns-settings-overview

FBTM wrote: What do I need to do to have the certificate renewed? Why would this message appear three years after the expiration date but not sooner?

Because we only implemented https support and automated *free* SSL cert handling last spring. You could not access any FTH websites w/ https prior to then.

However, when it comes to custom domains, we have been saying for a long time that domain forwarding is not supported. Just because you got it to work does not mean you should expect it to work in all cases... The lack of https support is one such case. Also, using domain forwarding prevents many of the FTH email features from working correctly.

Thank you for the link to the DNS settings instructions, Brian.

The registrar had an incorrect IP for the A setting & a typo for the MX setting. Was 184.168.221.27 ever FTH's server for support? I don't understand why I received the warning about the unsuccessful certificate renewal only on Thursday (Jan 11, 2018) after having had the site up for six years now.

Also, something happened between 12-20-17 & 1-14-18 that prevented the changing of the floater messages. When the correct IP was entered in the registrar, the changing of the floater messages was possible. [iWhat could have happened?][/i]

I ask these questions to make sure a HTTPS certificate can be created.