# Renew not work anymore **URL:** \ **Category:** Server\ **Created:** [November 22, 2018, 9:47am UTC](https://community.letsencrypt.org/t/renew-not-work-anymore/78163 "2018-11-22T09:47:53Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![fwe99](https://avatars.discourse-cdn.com/v4/letter/f/54ee81/32.png) [@fwe99](https://community.letsencrypt.org/u/fwe99)\ **Post date:** [November 22, 2018, 9:47am UTC](https://community.letsencrypt.org/t/renew-not-work-anymore/78163/1 "2018-11-22T09:47:53Z")
Renew do not work anymore: > bash-4.3# /usr/bin/certbot renew > Saving debug log to /var/log/letsencrypt/letsencrypt.log > > * * * > > ## Processing /etc/letsencrypt/renewal/cloud.cc-email.eu.conf > > Cert is due for renewal, auto-renewing... > Starting new HTTPS connection (1): [acme-v01.api.letsencrypt.org](http://acme-v01.api.letsencrypt.org) > Renewing an existing certificate > Performing the following challenges: > tls-sni-01 challenge for cloud.cc-email.eu > /usr/lib/python2.7/site-packages/OpenSSL/rand.py:58: UserWarning: implicit cast from 'char \*' to a different pointer type: will be forbidden in the future (check that the types are as you expect; use an explicit ffi.cast() if they are correct) > result\_code = \_lib.RAND\_bytes(result\_buffer, num\_bytes) > Waiting for verification... > Cleaning up challenges > Attempting to renew cert from /etc/letsencrypt/renewal/cloud.cc-email.eu.conf produced an unexpected error: Failed authorization procedure. cloud.cc-email.eu (tls-sni-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Incorrect validation certificate for tls-sni-01 challenge. Requested cb7edf9e315017f47589bd9b5c034a27.2fe6fd28c9be5bc1318f6cfbcd01f9b6.acme.invalid from 89.247.194.210:443. Received 2 certificate(s), first certificate had names "cloud.cc-email.eu". Skipping. > > All renewal attempts failed. The following certs could not be renewed: > /etc/letsencrypt/live/cloud.cc-email.eu/fullchain.pem (failure) > 1 renew failure(s), 0 parse failure(s) > > IMPORTANT NOTES: > > - The following errors were reported by the server: cloud.cc-email.eu has CNAME record only. But was before not a problem. Help very appreciated ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [November 22, 2018, 9:55am UTC](https://community.letsencrypt.org/t/renew-not-work-anymore/78163/2 "2018-11-22T09:55:30Z")
Hi @fwe99 > [@fwe99](#): > > tls-sni-01 challenge for cloud.cc-email.eu the tls-sni-01 - validation is deprecated, support ends 2019-02-13. > [@March 13, 2019: End-of-Life for All TLS-SNI-01 Validation Support](https://community.letsencrypt.org/t/february-13-2019-end-of-life-for-all-tls-sni-01-validation-support/74209): > > L… So try to change to http validation. ```nohighlight certbot renew --preferred-challenges http --nginx ``` ---
**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\ **Post date:** [November 22, 2018, 10:01am UTC](https://community.letsencrypt.org/t/renew-not-work-anymore/78163/3 "2018-11-22T10:01:34Z")
Expanding a little bit on @JuergenAuer’s answer. The TLS-SNI-01 method is currently working for you, but the depreciation deadline is Feb 13, 2019. The TLS-SNI-01 was supposed to generate a certificate and ask nginx to send it before sending the real, working certificate to check if you are allowed to request the certificate. However, there are some issues with this function, and certbot sometimes place the fake (validation) certificate after the real, working certificate, which ends in this issue. Now, since it’s depreciated, there will not be any support for this method (on developers end)… You should use the command @JuergenAuer provided and switch to http based validation. Thank you ---
**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\ **Post date:** [November 22, 2018, 10:05am UTC](https://community.letsencrypt.org/t/renew-not-work-anymore/78163/4 "2018-11-22T10:05:42Z")
Also, according to the thread from owncloud, after you switched to htrp based validation, you might need to use webroot instead of the default nginx authenticator. Because the univsesal redirection (that redirect all visits to a index.php link) might provide trouble for let’s encrypt validation servers. Ref: [https://doc.owncloud.org/server/10.0/admin\_manual/installation/letsencrypt/](https://doc.owncloud.org/server/10.0/admin_manual/installation/letsencrypt/) Thank you ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [December 22, 2018, 10:05am UTC](https://community.letsencrypt.org/t/renew-not-work-anymore/78163/5 "2018-12-22T10:05:52Z")
Closed on December 22, 2018, 10:05am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.