I recently launched a site for a client who wishes to use the Smush app for lazy-load and image optimization – the lazy-load works fine but we are hitting an issue with the API not being accessible. Here is the error we see when trying to optimize an image:

(Error posting to API: cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to smushpro.wpmudev.org:443)

I have done some digging and it seems that in the past this has either been an issue serverside from Smush directly, or an issue with permissions on the site-side with the host not allowing access. I believe our usecase is the latter as this clients hosting solution is rather outdated. Their IT/Infra departments have agreed to whitelist whatever IP is needed to allow the API connection if I can be provided the following:

• The IP address(es) to be whitelisted
• Any documentation that is publicly available for the API

Would someone from the plugin dev team be able to provide this information to me so we can whitelist and verify whether this is the issue or not? I searched previous forum entries and could not find this information (please feel free link to it if you have it in another thread somewhere!)

Thanks in advance!

The page / post editor stopped working, so now I can’t edit any page of my website. Whenever I try to edit a page or a post, I see a blank screen. I checked the Site Health and it turned out that the Rest API doesn’t work. (
I use a free SSL certificate from Cloudflare.)

I would really appreciate if you could help me resolve the issue. Here are the details:

1 critical issue
The REST API encountered an error

“The REST API is one way WordPress, and other applications, communicate with the server. One example is the block editor screen, which relies on this to display, and save, your posts and pages.

The REST API request failed due to an error.
Error: cURL error 35: SSL received a record that exceeded the maximum permissible length. (http_request_failed)”

I have been having issues connecting with Send in Blue – it was working fine up until today.

When I send a test, I get this error:

https://prnt.sc/10ufjv7

Does anyone know the fix for this, please?

Thank you

this error if i use mode : Transitional

The server holds multiple domains which do not have the same problems – i.e. they have a clean health check, so these issues are installation specific and not server issues (Ubuntu 18.04.)

ERROR: [] cURL error 35: error:1408F10B:SSL routines:ssl3_get_record:wrong version number applies to both:
* The REST API request failed due to an error.
* The loopback request to your site failed, this means features relying on them are not currently working as expected.

Other issues include:
* The scheduled event, wp_privacy_delete_old_export_files, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

File permissions are correctly set and .htaccess and site.conf files match for properly operating WordPress sites.

Why should these fail on a vanila install and how to I fix the problem?

Thanks

“WordPress error: cURL error 35: SSL connect error”

Also, we have 5 forms set up on Formstack and my WordPress Formstack back end shows:
Available Forms: 0
PHP Version: 7.1.11

I also tried “Refresh Formstack form cache” with no luck and the Authenticate With Formstack API constantly displays even after I successfully authenticate on the Formstack page.

Please advise.
Bruce

My provider hosts 2 sites. In one of them WordPress scans OK, but on the other one scan fails with error message in a yellow panel :
SCAN FAILED
The scan has failed because we are unable to contact the Wordfence servers. Some sites mays need adjustments to run scans reliably.
Under this panel there is another error message :
“[SEP 26 07:56:49] Scan terminated with error. There was an error connecting to the Wordfence scanning servers:cURL error 35:unknown SSL protocol error in connection to noc1.wordfence.com:443”

By searching this forum, I found many posts with fairly the same subject, but I am not sure what tests I should run in my case or what I should ask to my provider. Any suggestion would be welcome.

gabier

Fetching https://www.getpositions.com/ to prime cache: FAILED

Errors: : cURL error 35: gnutls_handshake() failed: A TLS fatal alert has been received.
Fetching first copy of https://www.getpositions.com/: FAILED

Errors: : cURL error 35: gnutls_handshake() failed: A TLS fatal alert has been received.
Fetching second copy of https://www.getpositions.com/: FAILED

Errors: : cURL error 35: gnutls_handshake() failed: A TLS fatal alert has been received.
The pages do not match! Timestamps differ or were not found!

I tried to backup in WP 4.7.4, but failed with this error message:

WP Http Error: cURL error 35: gnutls_handshake() failed: A TLS fatal alert has been received.

Then I upgraded to 4.8, and the error message stays. what’s the issue? How could I resolve it?

Many thanks~~