jelastic-jps / lets-encrypt

Let’s Encrypt Add-on for Jelastic PaaS

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

autoupdate doesn't work

bubbl opened this issue · comments

related to #14 .

At the current state, due to broken cron, the autoupdate doesn't work at all.

Also, I am not 100% sure but it seems the autoupdate feature does not update certificate at all.

Here's an example of failed update when ran manually:

{"response":{"response":"can't read ssl certificate","result":99,"error":"can't read ssl certificate","debug":[{"result":0,"responses":[{"result":0,"error":"--2017-03-06 14:40:10--  https://raw.githubusercontent.com/jelastic-jps/lets-encrypt/master/scripts/install-le.sh?_r=0.27541487818954036\nResolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.60.133\nConnecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.60.133|:443... connected.\nHTTP request sent, awaiting response... 200 OK\nLength: 741 [text/plain]\nSaving to: \u2018/root/install-le.sh\u2019\n\n     0K                                                       100%  366M=0s\n\n2017-03-06 14:40:11 (366 MB/s) - \u2018/root/install-le.sh\u2019 saved [741/741]\n\n\tpackage libcom_err-devel-1.42.12.wc1-4.el7.centos.x86_64 is already installed\nfatal: destination path '/opt/letsencrypt' already exists and is not an empty directory.\n--2017-03-06 14:40:13--  https://raw.githubusercontent.com/jelastic/jem/master/usr/lib/jelastic/modules/ssl.module\nResolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.60.133\nConnecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.60.133|:443... connected.\nHTTP request sent, awaiting response... 200 OK\nLength: 3054 (3.0K) [text/plain]\nSaving to: \u2018/usr/lib/jelastic/modules/ssl.module\u2019\n\n     0K ..                                                    100% 56.1M=0s\n\n2017-03-06 14:40:13 (56.1 MB/s) - \u2018/usr/lib/jelastic/modules/ssl.module\u2019 saved [3054/3054]","exitStatus":0,"nodeid":137039,"out":""}]},{"result":0,"responses":[{"result":0,"error":"--2017-03-06 14:40:16--  https://raw.githubusercontent.com/jelastic-jps/lets-encrypt/master/scripts/generate-ssl-cert.sh?_r=0.27541487818954036\nResolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.60.133\nConnecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.60.133|:443... connected.\nHTTP request sent, awaiting response... 200 OK\nLength: 2219 (2.2K) [text/plain]\nSaving to: \u2018/root/generate-ssl-cert.sh\u2019\n\n     0K ..                                                    100% 51.4M=0s\n\n2017-03-06 14:40:16 (51.4 MB/s) - \u2018/root/generate-ssl-cert.sh\u2019 saved [2219/2219]","exitStatus":0,"nodeid":137039,"out":""}]},{"result":0,"responses":[{"result":0,"error":"","exitStatus":0,"nodeid":137039,"out":""}]},{"result":0,"responses":[{"result":0,"error":"","exitStatus":0,"nodeid":137039,"out":""}]},{"result":0,"responses":[{"result":0,"error":"From https://github.com/letsencrypt/letsencrypt\n * branch            master     -> FETCH_HEAD\nSaving debug log to /var/log/letsencrypt/letsencrypt.log\nRenewing an existing certificate\nPerforming the following challenges:\ntls-sni-01 challenge for vetportal.royalcanin.co.uk\nWaiting for verification...\nCleaning up challenges\nGenerating key (2048 bits): /etc/letsencrypt/keys/0002_key-certbot.pem\nCreating CSR: /etc/letsencrypt/csr/0002_csr-certbot.pem\n  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed connect to http:80; Connection refused","exitStatus":0,"nodeid":137039,"out":"Already up-to-date.\nIMPORTANT NOTES:\n - Congratulations! Your certificate and chain have been saved at\n   /etc/letsencrypt/live/vetportal.royalcanin.co.uk/fullchain.pem.\n   Your cert will expire on 2017-06-04. To obtain a new or tweaked\n   version of this certificate in the future, simply run\n   letsencrypt-auto again. To non-interactively renew *all* of your\n   certificates, run \"letsencrypt-auto renew\"\n - If you like Certbot, please consider supporting our work by:\n\n   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate\n   Donating to EFF:                    https://eff.org/donate-le\n\nappid = 6576787f36a0251b1acbea9f9860b838\nappdomain = j.layershift.co.uk"}]},{"result":0,"responses":[{"result":0,"error":"","exitStatus":0,"nodeid":137039,"out":"e, simply run\n   letsencrypt-auto again. To non-interactively renew *all* of your\n   certificates, run \"letsencrypt-auto renew\"\n - If you like Certbot, please consider supporting our work by:\n\n   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate\n   Donating to EFF:                    https://eff.org/donate-le\n\nappid = 6576787f36a0251b1acbea9f9860b838\nappdomain = j.layershift.co.uk"}]}]},"result":0,"debug":{"time":37388,"cpu":{"time":98,"usage":"0"}}}

@ihorman, take a look at the error in the provided logs
package libcom_err-devel-1.42.12.wc1-4.el7.centos.x86_64 is already installed fatal: destination path '/opt/letsencrypt' already exists and is not an empty directory.

fixed, thanks everyone )))