Thanks wfphil,
that’s also what I thought. But the error is gone (on both sites), when Wordfence is deactivated and the hoster also told me that were no changes made in cURL library recently.
Since the error first appeared after the latest Wordfence update, I assume that this might be the cause.
-
This reply was modified 3 years, 9 months ago by elcompe.
