# Error on renew cert: unexpected error: Missing command line flag or config entry for this setting:

**URL:** https://community.letsencrypt.org/t/error-on-renew-cert-unexpected-error-missing-command-line-flag-or-config-entry-for-this-setting/95215
**Category:** Help
**Created:** [June 5, 2019, 4:57pm UTC](https://community.letsencrypt.org/t/error-on-renew-cert-unexpected-error-missing-command-line-flag-or-config-entry-for-this-setting/95215 "2019-06-05T16:57:54Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![pluplu](https://avatars.discourse-cdn.com/v4/letter/p/839c29/32.png) [@pluplu](https://community.letsencrypt.org/u/pluplu)
#### Post date: [June 5, 2019, 4:57pm UTC](https://community.letsencrypt.org/t/error-on-renew-cert-unexpected-error-missing-command-line-flag-or-config-entry-for-this-setting/95215/1 "2019-06-05T16:57:55Z")

</div>

whenever i try to renew my domain’s certificate using cerbot I’m faced with an error message.

this a linux server running ubuntu and apache, the certificate was issued by certbot, the server doesn’t have a control panel so everything is done using ssh.

the commandline response with error message at the bottom:

```auto
Attempting to parse the version 0.32.0 renewal configuration file found at /etc/letsencrypt/renewal/mydomin.com.conf with version 0.31.0 of Certbot.

This might not work.

Cert is due for renewal, auto-renewing...

Plugins selected: Authenticator webroot, Installer None

Renewing an existing certificate

Performing the following challenges:

http-01 challenge for mydomin.com

http-01 challenge for www.mydomin.com

Cleaning up challenges

Attempting to renew cert (mydomin.com) from /etc/letsencrypt/renewal
/mydomin.com.conf produced an unexpected error: Missing command line flag or config entry for this setting:

Input the webroot for mydomin.com:. Skipping.

All renewal attempts failed. The following certs could not be renewed:

  /etc/letsencrypt/live/mydomin.com/fullchain.pem (failure)

```

---

<div class="post-metadata">

### 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: [June 5, 2019, 5:12pm UTC](https://community.letsencrypt.org/t/error-on-renew-cert-unexpected-error-missing-command-line-flag-or-config-entry-for-this-setting/95215/2 "2019-06-05T17:12:24Z")

</div>

Hi @pluplu

> [@pluplu](#):
>
> Attempting to parse the version 0.32.0 renewal configuration file found at /etc/letsencrypt/renewal/mydomin.com.conf with version 0.31.0 of Certbot.

please share the content of that config file. And your domain name.

* * *

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. [crt.sh | example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot):

---

<div class="post-metadata">

### Author: ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)
#### Post date: [July 5, 2019, 5:12pm UTC](https://community.letsencrypt.org/t/error-on-renew-cert-unexpected-error-missing-command-line-flag-or-config-entry-for-this-setting/95215/3 "2019-07-05T17:12:33Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
