• 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 Error in cURL request:

wolle

New Pleskian
Server operating system version
Ubuntu 24.04.4
Plesk version and microupdate number
Plesk Obsidian Web Pro Edition Version 18.0.77 Update Nr. 1
Every hour I get this error.

Error in cURL request: Failed to connect to check-updates.plesk.com port 443 after 60002 ms: Timeout was reached:
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":"11711336","uid":"552814b8-bbe4-4d09-9bda-a669cfe4a844","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 'Plesk Roller', string '{"keyNumberId":"11711336","uid":"552814b8-bbe4-4d09-9bda-a669cfe4a844","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
 
@wolle

@Raul A. is right.

I think that you should first check your Fail2Ban and Firewall for the 18.203.120.118 and 52.30.104.252 IPs (and other IPs associated with Plesk updates).

If one of the IPs is blocked somehow, just unblock them : remove them from the Firewall and/or move to "trusted IPs" in Fail2Ban.

Nevertheless, the above does not mean that your problem is solved ....... since the Plesk update IPs should be unblocked by default, there is another root cause of the problem that should be resolved.

Kind regards....
 
Back
Top