~~~~~~~~~~~~ IMPORTANT INFORMATION -- Please read! ~~~~~~~~~~~~

1. The "search..." box above searches the Docs & Forum Posts. The "Search" tab above just searches the Forum Posts. :side:
Please use these to search for your issue *before* creating a new message topic, as your issue may have been previously solved.
2. Please put your Club # and Club Web Address in your Forum Signature (best) OR in each post to get faster support from us.
Click here to edit your signature at the bottom of the Profile Information tab.
3. Our user and admin docs are available at: support.toastmastersclubs.org/doc "There's a doc for that!" ;)
4. There is an "Opt In" Feature for newly added members. The Opt In document explains the strikethrough member information. Click Here to View the Post
5. When posting a New Topic , please include all relevant details and be specific. When did your issue 1st occur? What operating system, browser, & browser version are you using? Did you refresh your browser cache? Are your cookies enabled? Lastly, a screen shot is often helpful.
6. Please abide by the Terms of Use . We are volunteers contributing our spare time. We are happy to assist you, so long as you are respectful and courteous.
7. We are always looking for new FreeToastHost Ambassadors to join our team and support fellow Toastmasters in their use of the FreeToastHost website system. If you are familiar with the system and have some interest, send a Send Us a Private Message.

HTTPS certificates expiring

More
5 years 8 months ago #77968 by davietoasthost
Thank you Brian.
The topic has been locked.
More
5 years 8 months ago - 5 years 8 months ago #77969 by SteveTheTechie
If your domain DNS records cannot be validated by our automated cert renewal code, your existing cert will be left to expire. Additionally, if the situation persists, the code will eventually remove your domain from our database since we require HTTPS usage with the system.

Therefore, once you have gotten the DNS stuff sorted out, you need to let us know so that we can intervene and make sure you have a cert and are back in the automated loop.

Brian: I don't think I have the renewal loop set up to keep trying over and over for cases like this (at some point it just ditches the domain name)... That is why we may need to initiate a manual cert gen/renewal from our system admin tools.
Last edit: 5 years 8 months ago by SteveTheTechie.
The topic has been locked.
More
5 years 8 months ago #77974 by davietoasthost
Okay, for what I understand the issue is website is set to use Google as a mailserver and that setup would not allow for the SSL cert to renew. So, in that case I just delete the Google setting for the purpose of the update and put it right back. Since it's working now there is no reason it shouldn't continue to after the ssl cert renewal. What do you think Steve? By the way Brian and Steve you are awesome!

remove
davietoastmasters.org. 3600 IN MX 30 ALT2.ASPMX.L.GOOGLE.COM.
davietoastmasters.org. 3600 IN MX 10 ASPMX.L.GOOGLE.COM.
davietoastmasters.org. 3600 IN MX 40 ASPMX2.GOOGLEMAIL.COM.
davietoastmasters.org. 3600 IN MX 50 ASPMX3.GOOGLEMAIL.COM.
davietoastmasters.org. 3600 IN MX 20 ALT1.ASPMX.L.GOOGLE.COM.
The topic has been locked.
More
5 years 8 months ago - 5 years 8 months ago #77975 by SteveTheTechie

davietoasthost wrote: Okay, for what I understand the issue is website is set to use Google as a mailserver and that setup would not allow for the SSL cert to renew. So, in that case I just delete the Google setting for the purpose of the update and put it right back. Since it's working now there is no reason it shouldn't continue to after the ssl cert renewal. What do you think Steve? By the way Brian and Steve you are awesome!

remove
davietoastmasters.org. 3600 IN MX 30 ALT2.ASPMX.L.GOOGLE.COM.
davietoastmasters.org. 3600 IN MX 10 ASPMX.L.GOOGLE.COM.
davietoastmasters.org. 3600 IN MX 40 ASPMX2.GOOGLEMAIL.COM.
davietoastmasters.org. 3600 IN MX 50 ASPMX3.GOOGLEMAIL.COM.
davietoastmasters.org. 3600 IN MX 20 ALT1.ASPMX.L.GOOGLE.COM.


We do not actually verify the MX records to ensure they are set for FTH email. We do not require you to use FTH email. In practice though, most clubs do want to use the FTH email, so we include setting the MX record in our guidance so that people get that set correctly for FTH email.

The only thing we really check is the A record to ensure it points to the FTH server. As long as you have an A record pointing to the FTH server you should be fine. We check this by running the Linux "dig +short" command for your custom domain and looking for the FTH server IP address in the result.
Last edit: 5 years 8 months ago by SteveTheTechie.
The topic has been locked.
More
5 years 8 months ago #77980 by davietoasthost
Thank you DTM Steve,

Since running the "dig +short" require we have our MX records set to FTH email and in our case we have our own 3rd party solution, other than migration our email from Google to FTH would my previous stated solution work or you have another way to bypass that check. How are other FTH users if any dealing with this issue. I understand we may be unique to have a website hosting, domain hosting and email hosting separate
The topic has been locked.
More
5 years 8 months ago #77984 by SteveTheTechie
You are not reading my reply correctly. You have this all wrong. :pinch:
The topic has been locked.
Time to create page: 0.112 seconds