• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved 'ext.plesk.com' ssl expired

arsku

New Pleskian
hey, I discovered 'ext.plesk.com' ssl is not working in the china. so it will print 'Peer's Certificate has expired' when install plesk. I have tried to point the domain hosts to Japan's CDN, can solve this problem, but the speed is very slow, can you solve this problem?
 

Attachments

  • QQ截图20181102133912.png
    QQ截图20181102133912.png
    54.3 KB · Views: 14
  • QQ截图20181102134931.png
    QQ截图20181102134931.png
    83.3 KB · Views: 12
hey, I discovered 'ext.plesk.com' ssl is not working in the china. so it will print 'Peer's Certificate has expired' when install plesk. I have tried to point the domain hosts to Japan's CDN, can solve this problem, but the speed is very slow, can you solve this problem?

@arsku , could you show what IP ext.plesk.com is resolved to?
 
@korsar Here are some of the problems I encountered during the installation process


ERROR: Upgrade step 2017-06-26-09-21-10_InstallExtCatalog.php failed with code 1 and output:
ERROR: PleskUserException: Execution of /usr/local/psa/admin/plib/modules/catalog/scripts/post-install.php failed with exit code 1 and the output:
[2018-11-01 16:15:45.255] ERR [extension/catalog] Peer's Certificate has expired. (Package.php:583)
SUCCESS: Upgrade step 2017-07-17-15-42-03_ConfigureRDPSettings.php was successfully done.
[2018-11-01 16:15:50.195] ERR [panel] Peer's Certificate has expired.
SUCCESS: Upgrade step 2017-09-14-10-43-29_SearchIndex.php was successfully done.
SUCCESS: Upgrade step 2017-12-06-07-47-38_ApplyPleskRepairPermissions.php was successfully done.
SUCCESS: Upgrade step 2018-01-22-05-44-38_InstallExtRestApi.php was successfully done.
SUCCESS: Upgrade step 2018-02-14-18-14-01_UpgradeExtensions.php was successfully done.
[2018-11-01 16:15:52.523] ERR [panel] Peer's Certificate has expired.:
0: /usr/local/psa/admin/plib/Extension/Catalog.php:83
Plesk\Extension\Catalog->_request(string 'https://ext.plesk.com/api/v4/packages?platform=unix&with-hidden')
1: /usr/local/psa/admin/plib/Extension/Catalog.php:50
Plesk\Extension\Catalog->_getFeedContent(string 'https://ext.plesk.com/api/v4/packages?platform=unix&with-hidden', boolean false)
2: /usr/local/psa/admin/plib/Extension/Catalog.php:99
Plesk\Extension\Catalog->_getPackages(string 'https://ext.plesk.com/api/v4/packages?platform=unix&with-hidden', boolean false)
3: /usr/local/psa/admin/plib/Extension/Catalog.php:197
Plesk\Extension\Catalog->getUpgrades()
4: /usr/local/psa/admin/plib/Extension/Catalog.php:241
Plesk\Extension\Catalog->upgradeInstalledExtensions()
5: /usr/local/psa/admin/plib/Upgrade/Action/UpgradeExtensions.php:9
Plesk\Upgrade\Action_UpgradeExtensions->run()
6: /usr/local/psa/admin/plib/Upgrade/Deferred.php:31
Plesk\Upgrade\Deferred->run()
7: /usr/local/psa/admin/plib/Upgrade/Command/Upgrade.php:67
Plesk\Upgrade\Command_Upgrade->run(boolean false)
8: /usr/local/psa/admin/plib/Upgrade/upgrade.php:33
ERROR: PleskException: Peer's Certificate has expired. (Catalog.php:83)


WARNING!
Some problems are found during execute post install/upgrade actions(see log file: /var/log/plesk/install/plesk_17.8.11_installation.log)

Continue...

success
success
Stopping sw-cp-server (via systemctl): [ OK ]
Starting sw_engine service... done
Starting sw_cp_server service... done
Starting mysql service... already started
Starting named service... already started
Starting mailer service... done
Starting spamfilter service... not installed
Starting drweb service... not installed
Starting apache service... already started
Starting xinetd service... done

[2018-11-01 16:16:20.436628] Bootstrapper has finished action (exec time: 0 sec.): parent_name='PLESK_17_8_11', sequence='post', stage='execute', sequence_order='9998', operation='install', exec_cmd='test ! -x /usr/local/psa/admin/sbin/packagemng || /usr/local/psa/admin/sbin/packagemng --set-dirty-flag'', m_arch='', output: ~empty
[2018-11-01 16:16:20.719893] ===> Configuring ProFTPD server
Done!
Bootstrapper has finished action (exec time: 94 sec.): parent_name='PLESK_17_8_11', sequence='post', stage='execute', sequence_order='9999', operation='install', exec_cmd='/usr/local/psa/bootstrapper/pp17.8.11-bootstrapper/bootstrapper.sh perform-deferred-actions'', m_arch='', output: ~empty
[2018-11-01 16:17:54.901568] Bootstrapper has finished action (exec time: 0 sec.): parent_name='PLESK_17_8_11', sequence='post', stage='commit', sequence_order='1', operation='install', exec_cmd='rm -f /tmp/pp-bootstrapper-mode.flag; rm -f /var/lock/parallels-panel-maintenance-mode.flag; :'', m_arch='', output: ~empty
[2018-11-01 16:17:55.748855] Extension package ext-git 1.1.0-213 installation failed with code 1, stdout: ~empty
stderr: Error in cURL request: Peer's Certificate has expired.


[2018-11-01 16:17:55.749540] Execute command /usr/local/psa/admin/bin/send-error-report install --version 17.8.11
[2018-11-01 16:17:55.750732] Warning: Failed to attach to cgroup /sys/fs/cgroup/systemd/user/root/tasks, installer might be unexpectedly killed later by the system
[2018-11-01 16:17:55.769888] Error: 安装或升级扩展 'Git'(程序包:git)失败:Error in cURL request: Peer's Certificate has expired.


警告!未安装所有的程序包。
请检查您的系统服务是否可操作。
请先解决该问题然后再重试安装包。如果您自己无法解决该问题,请联系产品技术支持寻求帮助。
 
@arsku it seems that the issue with SSL certificate caused by some misconfiguration of the region CDN PoP. We are checking the issue with the CDN provider.
Will keep you informed.
 
Yep, seems yes. CDN team fixed this.
Thank you for letting us know about the issue.
Now we've configured monitoring to keep such issues under our control.
 
Back
Top