SSL is not working (commonly after a site move)

Edited

Overview


SSL issues often occur when a site is migrated to a new server, when DNS is not correctly updated, or when old/extra A-records conflict with the correct IP configuration.

Note: This isn't a BionicWP hosting issue.



Common Causes

  • Website recently moved to a new hosting/server

  • Incorrect or outdated A-records pointing to an old IP

  • Propagation delay after DNS update

  • Domain does not point to the server where SSL is installed


How to Resolve

  1. Check A-Records

  2.  Ensure only the correct A-record(s) exist.

    • Remove any additional or old A-records pointing to previous servers.

    • Keep only the main one that matches your hosting/server IP.

  3. Confirm DNS Propagation

  4.  SSL will not work until the domain is fully pointed to the correct IP

  5. Check “www” and non-www Versions are correctly updated. Both should point to the correct A-record or use CNAME appropriately.

  6. Wait for DNS Updates

  7.  Changes may take 15 minutes to a few hours depending on TTL.


When to Contact Support


If the DNS is correct but SSL still shows errors, share the domain with support to verify the certificate installation.