SSL Renew Problem

Hi Guys Im having major SSL problems

This is an error message received in response to this command.

ee site ssl

Starting SSL verification.
Warning: Failed to verify SSL: cURL error 60: SSL certificate problem: certificate has expired (see
Warning: Check logs and retry ee site ssl once the issue is resolved.

Im also continually getting this
Error: Site already contains SSL.

Any guidance appreciated …causing downtime.

have the same issue too. latest v4 version, certificate has expired and can’t figure out a way to renew it

any help would be appreciated

Try this and see if it gives you the same error.

ee site ssl-renew --all

it does, i’ve tried every command suggested here

ee site ssl-renew site
ee site ssl-renew --all

ee site update . com --le=off
Error: Site . com already contains SSL.

./letsencrypt-auto certonly --webroot -w /opt/easyengine/sites/ -d site . com -d . com --email --text --agree-tos runs into acme well-known issue

and so on.

as time is of an essence here, i’ll PP $100 to the person that provides working solution to this issue.

Tried adding --force ?

Not sure if this is the cause but just incase, have you also added a CAA dns record?

yep tried --force. dns is sound

thanks for suggestion. currently i’m backing up WP, deleting site and re-creating it…

Sorry to hear and hope you get sorted.
I have a few issues myself with non-intentional redirection and SSL not renewing itself so probably gonna abandon ship to runcloud and see what the fuss is about while the issues get sorted out in ee4.

did the same, moved important sites to sendgrid and for less important re-created under ee

Same here:

Starting SSL verification.
PHP Fatal error:  Uncaught GuzzleHttp\Exception\RequestException: cURL error 60: SSL certificate problem: certificate has expired (see in phar:///usr/local/bin/ee/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:186
Stack trace:
#0 phar:///usr/local/bin/ee/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php(149): GuzzleHttp\Handler\CurlFactory::createRejection(Object(GuzzleHttp\Handler\EasyHandle), Array)
#1 phar:///usr/local/bin/ee/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php(102): GuzzleHttp\Handler\CurlFactory::finishError(Object(GuzzleHttp\Handler\CurlHandler), Object(GuzzleHttp\Handler\EasyHandle), Object(GuzzleHttp\Handler\CurlFactory))
#2 phar:///usr/local/bin/ee/vendor/guzzlehttp/guzzle/src/Handler/CurlHandler.php(43): GuzzleHttp\Handler\CurlFactory::finish(Object(GuzzleHttp\Handler\CurlHandler), Object(GuzzleHttp\Handler\EasyHandle), Object(GuzzleHttp\Handler\CurlFactory))
#3 phar:///usr/local/bin/ee/vendor/guzzlehttp/guzzle/src/Handler/Proxy.php(28): Guz in phar:///usr/local/bin/ee/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php on line 186
Warning: An Error occurred. Initiating clean-up.
Warning: Exiting gracefully after rolling back. This may take some time.
Success: Rollback complete. Exiting now.

On sudo ee site ssl-renew
Version: EE v4.0.14
Unfortunately, I am quite disappointed with the EE v4. It’s quite slow (maybe due to the docker containers, which should be no problem), tutorials and commands are outdated (but still on the website), dockers run as root, elementary commands do not work reliably. Is there any reliable alternative to easyengine?

Hi Guys,

I found the solution to this problem in this thread.

Hope it helps you also.



Unfortunately I’ve had the exact same experience with EE v4. I’ve starting using SpinupWP by Delicious Brains (fantastic). Also tried Runcloud and it worked well, but wasn’t as focused on WordPress.

EasyEngine was awesome, but the reality is that any excellent solution is going to cost some money unless it’s being subsidized by an enormous corporation. As rtCamp has grown (well deserved success!), the EE project has gotten less love than before. As you point out, patchy docs and incomplete features are examples of that.

I would love to see rtCamp offer EE has a paid solution, a la Runcloud, SpinupWP, ServerPilot, etc. It’s clear that as a free side project it’s not what it once was. And that’s not really anybody’s fault.

EE is great.

SSL problems are an easy fix:
1. You can be careful and pay attention to your emails when the Let’s Encrypt informs you about ssl expiration, and simply renew your ssl before it expires.
2. you can add a simple cron command which will run the ssl renew command few weeks before expiration - Done!

If you let it expire, your options are to simply redeploy the server/website. It takes a lot less time than to write posts of how unsatisfied you are with ee.

I was in the same situation. Then I redeployed server/deleted my website, and added it again.
Took me less than an hour. (with my methods)

Hey Guys,

Just a heads up for people that fail with this method. I find that it fails if you try to keep the old file as in.
mv oldfile.crt oldfile.crtBAK

But it will work if you delete it.

and then run ee site ssl-renew --force