Fix TLS error for https://www.agilesix.com (not www.agile6.com)

[ElijahLynn]

Getting cert error on https://www.agilesix.com when it tries to redirect

dig www.agilesix.com

www.agilesix.com. 3504 IN CNAME agilesix.com.
agilesix.com. 504 IN A 184.168.131.241

ip2location.com > 184.168.131.241 > godaddy.com

[ElijahLynn]

Just hangs at connecting now.

[ElijahLynn]

This is also happening at https://agilesix.net/.

[ElijahLynn]

I think what needs to be done is that we update the Lets Encrypt certificate with 2 Subject Alternative Names (SAN) and somehow attach that to the shortener.secureserver.net redirects. I don't know if the shortener.secureserver.net are in GoDaddy or where that is?

[ElijahLynn]

It appears that securesever.net is in fact GoDaddy. And now that I think about it, the main site is on Netlify and probably has integration with Lets Encrypt, so the SAN idea won't be easy with that. I suggest we update DNS to point at Netlify instead of GoDaddy's redirect service (secureserver) for agilesix.com/net and use the interface in Netlify to regenerate the TLS certificate with the two additional SANs.

[ElijahLynn]

K, I added the domain aliases in Netlify:

Now we just need to update the DNS in GoDaddy. For the below domains in GoDaddy we need to add the following DNS records, make sure to include the trailing period, .:

• agilesix.net

  • agilesix.net ALIAS agile6.netlify.app.
  • www CNAME agile6.netlify.app.

• agilesix.com

  • agilesix.com ALIAS agile6.netlify.app.
  • www CNAME agile6.netlify.app.

Then, we need to go into our Netlify and "Renew Certificate" and the SANs should be added to the Lets Encrypt certificate.