Cause: SSL Peer Certificate or SSH Remote Key was not OK

The “SSL Peer Certificate or SSH Remote Key was not OK” error typically occurs when a domain is not pointing to the correct server where the SSL certificate is installed. This is most common after a site migration or when DNS records are outdated or misconfigured.

Note: This is not a BionicWP hosting issue.

• Website recently moved to a new server or hosting provider

• A-records still pointing to an old or incorrect IP address

• Multiple A-records causing conflicts

• DNS propagation still in progress after recent updates

• Domain not resolving to the server where the SSL certificate exists

• “www” and non-www records pointing to different locations

• Confirm the domain’s A-record points to the correct server IP in the platform

• Remove any old or extra A-records referencing previous servers

• Keep only the required A-record(s) provided in the platform.

• Ensure both versions resolve correctly:

  • Either both point to the same A-record, or

  • One uses a CNAME pointing to the other

• Avoid mixed configurations that send traffic to different IPs

• SSL certificates will not validate until DNS fully resolves to the correct server IP records shown in the platform

• Allow 15 minutes to several hours for DNS changes to propagate, depending on TTL

Contact support if:

• DNS records are correct but the SSL error persists

• You need confirmation that the SSL certificate is installed properly

• The site continues to show certificate-related warnings

Share the domain name so the team can verify DNS resolution and certificate status.