Why is my server configuration inconsistent?

Posted July 28, 2019 4.2k views

I got a domain in GoDaddy and I am using DigitalOcean (DO) to deploy my webapp. I created a ssl certificate using letsencrypt and aparently everything is fine. When I run the ssl-test from it appears to be a problem with the server configuration (Warning: Inconsistent server configuration)

Why is my godaddy ip address not certified as my DO ip?


These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
4 answers


Do you see two domains listed in the result in Can you confirm if both www and the non www DNS records are pointed to the same IP address?

Looking forward to your reply.


Yes, I have two domains listed in the result in One is the IP address of DigitalOcean with A+ Grade, and the other address is the one in Godaddy with no grade. An additional message says “Certificate not valid for domain name”..

I am not sure about the pointing. What I have done is in godaddy create a new A record to root and the DO ip address…

I have also tried changing the nameservers but same result.

I suppose, I am doing the IP pointing wrong. Is the only thing I can think of.


Thanks for replying back.

The DNS should be pointed correctly, usually you just need to point the A record of the domain name to the DigitalOcean IP address.

Two things to check:

  1. Make sure the SSL was issued for both www and non www version of your domain name.
  2. If you’re using nginx, make sure to check the config file and see if the domain is configured properly, because it should include both domains:


  • Thanks for the fast response.

    Well, actually the certificate was issued in both cases only for

    So, I am planning to do is adding to the configuration files, and generate a new certificate, but

    What would happend to the old certificate? Do I have to delete it manually?


Yes, you can also delete the certificate in the acme-tiny directory and then issue another SSL certificate.

Let me know how it goes.


  • Hi there,

    well, I have executed all your recommendations and I still have the same result.Both root and www are pointed but the result is ssllabs is still the same

    • If everything is working fine for you and you’re unable to track any issues with your site you can use some alternative sites to check the SSL: DigiCert and SSL Checker

      I’ve seen a lot of people complaining about the same error. There should be something which SSLlabs don’t like here, but this does not necessary mean that something is broken or not working.