If it does, the problem might be in your local server configuration. Sometimes outdated PHP or openSSL versions can also cause cURL errors.

Everything ok but DNS CAA a no.

I contacted my hosts with https://really-simple-ssl.com/knowledge-base/curl-errors/

Their response:
“It isn’t a shared certificate, they are correct with regards to it being the most common for localhost development environments, however this isn’t. The SSL is one for your domain rather than the server, the errors are being caused because the plugin is trying to access the root certificate, which it won’t have the permissions to access”

Any thoughts?

can you check with your hosting provider if cURL is updated to the latest version and what PHP version they are using? Usually updating cURL/PHP can resolve cURL errors.

Just checked with hosters, cURL is up to date but they note:

• “The reason the messages appear is because of how we install the SSL certificates onto our platform.
  The WordPress software is expecting to see see the SSL installed onto the same platform as where the website is. However, on our system, we install the SSL onto a different server called a Load Balancer.

  It’s nothing to worry about. We would define this as a “False Positive”.”

PHP: 7.3

missing block is not related to Really Simple SSL, you could try to re-install WordPress via the Updates screen to check if that resolves your issue.

Mark

Would the false positive be affecting Site Health troubleshooting mode if the REST API and loopback didn’t function?

the site health can indicate that these functions won’t work, but that shouldn’t affect your site. Your site should continue to work fine.

Mark