• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Issue Zend_Http_Client_Exception: Error in cURL request:

Polli

Basic Pleskian
Server operating system version
Debian 12.9
Plesk version and microupdate number
18.0.67
I´ve now found out that this error exist since the last update of the nextcloud extension. This error appears every hour. Along with this update of the nextcloud extension, there was also an update of bind9.

Code:
Zend_Http_Client_Exception: Error in cURL request: Failed to connect to updates.nextcloud.com port 443 after 210 ms: Couldn't connect to server in /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Http/Client/Adapter/Curl.php:455
Stack trace:
#0 /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Http/Client.php(1088): Zend_Http_Client_Adapter_Curl->write('GET', Object(Zend_Uri_Http), '1.1', Array, '')
#1 /opt/psa/admin/plib/modules/nextcloud/library/NextcloudApi.php(98): Zend_Http_Client->request()
#2 /opt/psa/admin/plib/modules/nextcloud/library/Instances.php(455): PleskExt\Nextcloud\NextcloudApi::latestVersion(Object(PleskExt\Nextcloud\Instance))
#3 /opt/psa/admin/plib/modules/nextcloud/scripts/refresh-instances-fast.php(12): PleskExt\Nextcloud\Instances::updateLatestVersion(Object(PleskExt\Nextcloud\Instance))
#4 {main}

How can I solve this?
 
Seems like the server is having issues connecting to updates.nextcloud.com. Make sure you don't have anything that might block the outbound to that server, either that or nextcloud's servers is down but chances are something is blocking it.
 
Seems like the server is having issues connecting to updates.nextcloud.com. Make sure you don't have anything that might block the outbound to that server, either that or nextcloud's servers is down but chances are something is blocking it.
There is no connection issue. I can ping all necessary domains and ip´s with no issue. The error appears since the last update for the nextcloud extension and/or bind9 updates. This is just a few days ago.
 
The error still exists. I am now on a freshly installed server. This is currently the only error.

Code:
Zend_Http_Client_Exception: Error in cURL request: Failed to connect to updates.nextcloud.com port 443 after 30000 ms: Timeout was reached in /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Http/Client/Adapter/Curl.php:455
Stack trace:
#0 /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Http/Client.php(1088): Zend_Http_Client_Adapter_Curl->write('GET', Object(Zend_Uri_Http), '1.1', Array, '')
#1 /opt/psa/admin/plib/modules/nextcloud/library/NextcloudApi.php(98): Zend_Http_Client->request()
#2 /opt/psa/admin/plib/modules/nextcloud/library/Instances.php(455): PleskExt\Nextcloud\NextcloudApi::latestVersion(Object(PleskExt\Nextcloud\Instance))
#3 /opt/psa/admin/plib/modules/nextcloud/scripts/refresh-instances-fast.php(12): PleskExt\Nextcloud\Instances::updateLatestVersion(Object(PleskExt\Nextcloud\Instance))
#4 {main}

The Server is now on Debian 12.10 with Plesk Web Pro 18.0.68#2
 
Hello, @Polli I can see reports for similar issue before (on Nextcloud's end as well), which turned out to be due to connectivity failure. I personally do not think this is a bug resulting from the extension update. However, please do provide us with step-by-step instructions on how to reproduce the reported issue on our end so we can further review it.
 
This error is still persitent, even after a fresh install of my server and everything is on default settings (I´m now on Debian 13). So I have no idea why this still happens day after day. Sometimes the error looks like this.

Code:
Zend_Http_Client_Exception: Error in cURL request: Recv failure: Connection reset by peer in /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Http/Client/Adapter/Curl.php:455
Stack trace:
#0 /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Http/Client.php(1088): Zend_Http_Client_Adapter_Curl->write('GET', Object(Zend_Uri_Http), '1.1', Array, '')
#1 /opt/psa/admin/plib/modules/nextcloud/library/NextcloudApi.php(98): Zend_Http_Client->request()
#2 /opt/psa/admin/plib/modules/nextcloud/library/Instances.php(455): PleskExt\Nextcloud\NextcloudApi::latestVersion(Object(PleskExt\Nextcloud\Instance))
#3 /opt/psa/admin/plib/modules/nextcloud/scripts/refresh-instances-fast.php(12): PleskExt\Nextcloud\Instances::updateLatestVersion(Object(PleskExt\Nextcloud\Instance))
#4 {main}
 
@Polli , please check if there are any additional errors logged into /var/log/plesk/panel.log related to the Nextcloud extension [extension/nextcloud].
Yes. There are a lot. Maybe this one.

Code:
Zend_Http_Client_Exception: Error in cURL request: Failed to connect to updates.nextcloud.com port 443 after 4 ms: Could not connect to server in /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Http/Client/Adapter/Curl.php:455
Stack trace:
#0 /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Http/Client.php(1088): Zend_Http_Client_Adapter_Curl->write('GET', Object(Zend_Uri_Http), '1.1', Array, '')
#1 /opt/psa/admin/plib/modules/nextcloud/library/NextcloudApi.php(98): Zend_Http_Client->request()
#2 /opt/psa/admin/plib/modules/nextcloud/library/Instances.php(455): PleskExt\Nextcloud\NextcloudApi::latestVersion(Object(PleskExt\Nextcloud\Instance))
#3 /opt/psa/admin/plib/modules/nextcloud/scripts/refresh-instances-fast.php(12): PleskExt\Nextcloud\Instances::updateLatestVersion(Object(PleskExt\Nextcloud\Instance))
#4 {main}

My resolv.conf has no entrys by default.
 
Thank you. Could you please restart the sw-engine service:

Code:
service sw-engine restart

Then manually re-attempt the update from from Extensions > Nextcloud.
 
Thank you. Could you please restart the sw-engine service:

Code:
service sw-engine restart

Then manually re-attempt the update from from Extensions > Nextcloud.
I´ve done this several times. The issue still exist.

A similar issue is also with plesk-update:

Code:
Error in cURL request: Recv failure: Connection reset by peer:
0: /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Http/Client/Adapter/Curl.php:455
    Zend_Http_Client_Adapter_Curl->write(string 'POST', object of type Zend_Uri_Http, string '1.1', array, string '{"keyNumberId":"*********","uid":"6074a1e6-68b9-45d7-aeb9-***********","updateTicket":null}')
1: /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Http/Client.php:1088
    Zend_Http_Client->request()
2: /opt/psa/admin/plib/CommonPanel/Update/Roller.php:60
    Plesk\CommonPanel\Update\Roller->sendRequest(string 'https://check-updates.plesk.com', string '{"keyNumberId":"*********","uid":"6074a1e6-68b9-45d7-aeb9-***********","updateTicket":null}')
3: /opt/psa/admin/plib/CommonPanel/Update/Roller.php:26
    Plesk\CommonPanel\Update\Roller->checkUpdates()
4: /opt/psa/admin/plib/DailyMaintainance/Task/UpgradePanel.php:24
    Plesk\DailyMaintenance\Task\UpgradePanel->run(array)
5: /opt/psa/admin/plib/DailyMaintainance/Runner/Task.php:76
    DailyMaintainance_Runner_Task->runTask(object of type Plesk\DailyMaintenance\Task\UpgradePanel, array)
6: /opt/psa/admin/plib/DailyMaintainance/Runner/Task.php:51
    DailyMaintainance_Runner_Task->run()
7: /opt/psa/admin/plib/DailyMaintainance/task-script.php:17

or with sslit

Code:
Failed to load ssl config data: Could not get Mozilla tls config: cURL error 6: Could not resolve host: statics.tls.security.mozilla.org (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://statics.tls.security.mozilla.org/server-side-tls-conf-4.0.json

For my opinion it has to be done with the dns and/or curl. I´ve deactivated ipv6 because I can only run ipv4 on my server. It seems that ipv6 is still enabled, cause of these entrys in my log. The updates work when I manually retry them, but I have to do it twice sometimes. If I do nslookup or dig it always try to do it with ipv6, even I have it deactivated.

As I mentioned, my dns-settings are on default by Plesk. So it should be running without any issues. My server is running so far. but I´ve these errors every day in my log several times. The only bad issue is Spamassassin, wich often fails at detecting spam, cause of these curl issue maybe.

I´m running out of ideas.
 
Thank you for the confirmation. Unfortunately, I am also out of suggestions. I would suggest opening a ticket with Plesk support for further investigation on your server.
 
Back
Top