It seems that Firefox does not display the error if it autocompletes the url with http://. For some reason yesterday it went via https://. If you use https:// explicitly the failure is still there. Does apache allow for custom domain? Then it would be simply a matter of pointing the DNS record to apache server and use nuttx.org as the main URL. Also, it is good practice to make HTTP be redirected to HTTPS, if GoDaddy allows for that.
On Sun, Aug 30, 2020, at 12:46, Brennan Ashton wrote: > On Sun, Aug 30, 2020, 8:34 AM Gregory Nutt <spudan...@gmail.com> wrote: > > > > > > I'm getting the following error on firefox: > > > > > > Websites prove their identity via certificates. Firefox does not trust > > this site because it uses a certificate that is not valid for nuttx.org. > > The certificate is only valid for the following names: > > shortener.secureserver.net, www.shortener.secureserver.net > > > > > > Error code: SSL_ERROR_BAD_CERT_DOMAIN > > > > > > Note that this does not happen for nuttx.apache.org. > > > > This has happened before. I don't see the problem this morning (also > > using Firefox). > > > > securesever.net is GoDaddy. nuttx.org is not a website. The URL is > > parked at GoDaddy and currently just re-directs to nuttx.apache.org. > > This is probably with GoDaddy itself, so I don't think there is > > anything that can be done except wait for them to fix their certificate > > (which apparently they have) > > > > > Greg, I think something is configured wrong. This is the same thing I saw > when I mentioned it a while back and I have never seen it work since. > > https://www.ssllabs.com/ssltest/analyze.html?d=nuttx.org&hideResults=on > > Are we sure GoDaddy supports SSL on parked domains? My offer still stands > to sort the DNS bit out. > > --Brennan >
