Error Renewing Certificate Today : too many currently pending authorizations

[mobifilia]

@schoen
On closer inspection I found out that above quotes are opening and closing type as below.

“”

and not standard ones as below.

""

The post editor converts standard quotes to smart ones, so added them as pre-formatted text!

[mobifilia]

@schoen

I’ve understood why you’re getting this error but I would like to know if there’s something about your configuration that led you to intentionally use --standalone. It looks to me like --standalone is not the correct authentication method for your environment.

@schoen, Now is it OK to change to the correct authentication method nginx from standalone in /etc/letsencrypt/renewal?
Also if it is okey, then will I also have to add --renew-hook to load renewed certificates in Nginx?

[schoen]

@mobifilia

Now is it OK to change to the correct authentication method nginx from standalone in /etc/letsencrypt/renewal?

We usually suggest that people try doing this with certbot certonly --cert-name whatever.org --nginx --force-renewal (just once) so that Certbot will edit the file for you and you'll immediately see if it worked or not.

Also if it is okey, then will I also have to add --renew-hook to load renewed certificates in Nginx?

If it works and it gets set as both authenticator and installer in the file, then you wouldn't need the --renew-hook because installer = nginx is able to restart the web server for you.