• 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!
  • 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.

Resolved Server not serving renewed letsencrypt

Stuart De Usoz

New Pleskian
Plesk Onyx Linux

One of my domains suddenly has browsers showing expired certificate. Yet LetsEncrypt seems to have renewed. So I manually renewed again, twice, both times successfully. But Plesk still serving an expired certificate.

Second time I checked the /var/www/vhosts/system/[mydomain]/conf/vhost_nginx conf

And the name changed as it should, the cert file exists where it says it should be, but server still showing old expiration date.

There's nothing pertinent in the /var/log/plesk/panel.log

I tried plesk repair web -sslcerts but did not resolve issue.

Now I tried going to Websites and Domains>hosting Settings>Security>certificate and selected "not selected" and browsers still show that it has a certificate with old expiration date.
 
Last edited:
I updated Plesk components now at latest Onyx.

Then tried plesk repair web (all)
- httpdmng failed: [2019-10-18 01:40:43.905] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/nginx_control' '--restart'] with exit code [1] Can not reload proxy server:

Then I tried nginx -t *(is ok)

then
plesk repair all -y -v |
still getting error:
- httpdmng failed: [2019-10-18 01:58:40.110] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/nginx_control' '--restart'] with exit code [1] Can not reload proxy server:

ALSO
- httpdmng failed: Execution failed. Command: httpdmng Arguments: Array ( [0] => --reconfigure-domains [1] => [list of domains including many that were removed] )

Went to Tools and Services > manage and tried to manually restart nginx proxy there and at top of page error:

Unable to start service: Unable to manage service by nginxmng: ('start', 'nginx'). Error: [2019-10-18 02:04:05.614] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/nginx_control' '--start'] with exit code [1] Can not start proxy server:

THEN
[root@u17483829 plesk]# service nginx restart ERROR: ports 80/443 are still not free. [FAILED] Starting nginx: [ OK ]

SO there's an issue with ports... checking
 
Last edited:
OK getting somewhere, I just restarted server and ran plesk repair all -y -v again and now proxy server is running, Cert now showing expired in 2015 so it's not the one that expired last week at least. Will try reinstalling letsencrypt now... I didn't have to do that, I had deselected it for testing... Reselected and we're all good now. Thanks for providing this space where I could vent to myself LOL JK you guys are great and I know you just didn't get around to me yet.
 
Back
Top