Independence_Day

Hello Brandon,

“Why make it simple when you can make it complicated”: this is what is said in France when an “improvement” complicates the task of the users.

But then, I finally understood. It’s for the good cause: for safety reasons.

Successive changes to the code have had enormous repercussions for some of your users. We are at least 3 …

The last solution seems to me the right one.

The Wordfence Security plugin uses the same principle to “customize” the name of certain sensitive files. The “hash” at the end of the name!

And after no change! Promised?

Best regards,

Patrick

Hello,

I agree with you, Daniel. My web host should solve the problem. In ten days. By updates of cURL and cURL SSL. Finally, I hope…

But several remarks.

BackWPup works fine with my HTTPS websites for months.
Since Monday of this week, it is no longer true.
I do not see the connection with the complete wordpress cron.
I did a test with UpdraftPlus – Backup / Restore.
UpdraftPlus detects the same error BackWPup during this test : “HTTP Get: https://domain-name.fr Fetch (Curl)”.
I get the “error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure”.
Despite this error, UpdraftPlus done the job. Backups are made and they are complete, I checked (FTP and Dropbox).

But I don’t want to work with UpdraftPlus. I prefer BackWPup.

Patrick

Hello,

I answer my own message.

I also contacted the author of Go Pricing. The problem is specific to version 3.2. A fix will be included in the next version.

So the problem does not come from Wordfence.

Patrick