Hello @megabits
PayPal Payments does not require SSL. This cURL error is usually a server-related issue and not created by a plugin/theme/WordPress core in most cases. If you search around on Google, you’ll notice it’s quite a widespread problem, and there are a couple of solutions for this.
I recommend reaching out to your hosting provider about this. Beyond that, check if you use Cloudflare, firewall rules, or any caching. Beyond this, I’m not sure that this is related to the fatal error.
Could you check if the fatal error occurs frequently? Or after you enabling the plugin?
Let us know what you find.
Kind Regards,
Krystian
The error that your Google search indicates refers to a CURL error 28 and we are getting a CURL error 35 as reflected in the logs sent.
Thank you.
Hello @megabits
You are right; my mistake. I also didn’t notice one of your log files at first – I was under the impression that we only received the fatal error. I now see that there is also a log file from our plugin.
However, what I mentioned earlier still applies. The issue is most likely caused by a connection problem between your web server and our API server. I recommend starting by checking with your hosting provider, as the plugin is simply reporting a connection issue, but the root cause is likely on the server side. In theory, you could try logging in again within the plugin to see if that has any effect, as it would refresh the webhook connection. However, this process is nowadays mostly automated. The plugin is just detecting the issue, but the source of the problem is with your hosting environment.
Let me know if you need further assistance.
Kind Regards,
Krystian
Hello @megabits
Since we have not received any further communication from you, we are assuming that your issue has been resolved.
Therefore, we mark this thread as resolved. If you still have any questions or if a new problem arises, don’t hesitate to open a new thread.
Kind regards,
Krystian