• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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.
 
Back
Top