Letsencrypt renew problem

[proscriptsell]

Hi
hope all are doing great . when i am running ( sudo letsencrypt renew ) Then getting bellow error…

Processing /etc/letsencrypt/renewal/edatastyle.com.conf
2016-10-24 06:52:42,882:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/edatastyle.com.conf produced an unexpected error: ‘server’. Skipping.

And edatastyle.com.conf file bellow

renew_before_expiry = 30 days

version = 0.8.1
cert = /etc/letsencrypt/live/edatastyle.com/cert.pem
privkey = /etc/letsencrypt/live/edatastyle.com/privkey.pem
chain = /etc/letsencrypt/live/edatastyle.com/chain.pem
fullchain = /etc/letsencrypt/live/edatastyle.com/fullchain.pem

Options used in the renewal process

[renewalparams]
authenticator = webroot
installer = None
account = fddddddddddddddddddd
webroot_path = /var/html/edatastyle,
[[webroot_map]]
www.edatastyle.com = /var/html/edatastyle
edatastyle.com = /var/html/edatastyle

Thanks

[serverco]

Are you using Ubuntu ? is this related to your issue ?

from Unexpected error: 'server'. Skipping:

@pfg

I believe this is a side-effect of switching from a recent release of certbot-auto (or letsencrypt-auto) to the (older) letsencrypt package in Ubuntu 16.04. The older Ubuntu package is not forwards-compatible to configuration files generated by more recent releases. You have a couple of options:

Continue using certbot-auto. You can follow the instructions on the certbot homepage for Ubuntu 14.04 - they work just fine on 16.04.
Start with a new configuration. The cleanest way would probably to do something like mv /etc/letsencrypt /etc/letsencrypt.old and then re-issue all certificates.
Try to manually fix the configuration. This is probably tricky and error-prone. The best way to attempt this would probably be to issue a new certificate with the letsencrypt command first, and then compare the generated config file in /etc/letsencrypt/renewal with the one that's failing at the moment.

[proscriptsell]

@serverco

you using Ubuntu ? is this related to

Yes i am using Ubuntu 16

[serverco]

It looks as if that is the issue then, and provides the options in that thread. I’d personally use certbot, remove the old config and create new certs, then maintain them with certbot.

[proscriptsell]

Thanks . i did and working fine