MissingCommandlineFlag(msg) certbot.errors.MissingCommandlineFlag: Missing command line flag or config entry for this setting: Please choose an account

Hi, this is just a note for anyone else that encounters this issue. I recently moved my box to a new host/server. When the certificates came up for renewal (after the reinstall on the new server) I started to get these errors: MissingCommandlineFlag(msg)
certbot.errors.MissingCommandlineFlag: Missing command line flag or config entry for this setting:
Please choose an account

Basically, it looks like the restore moved the original certificate information and the reinstall created a new one. So, when the renewal attempted to happen it was confused about which one to use to renew. To fix, I went to /home/user-data/ssl/lets_encrypt/accounts/acme-v02.api.letsencrypt.org/directory and chose the oldest directory there (there should be 3 files in it) and moved the entire directory to a temp directory just in case it didn’t fix it. I than ran the “provision” request from inside the MIAB GUI and it ran successfully and updated the pending certificates. In case anyone else encounters this, I hope this helps.

9 Likes

thanks a lot Dave !!!
it saved my day !!!

1 Like

+1 for thanks to Dave. That solution worked perfectly.

1 Like

And many thanks also from me. This problem bit me weeks after I moved my box from my home to the cloud; your post saved me a lot of frustration!

:+1: for Dave! Thanks for posting, this saved my day also!

Maximum Karma coming your way, my new hero friend! My exact issue… you saved me hours… :people_hugging:

Another happy customer here!

Same situation, same problem.

I would never have found out on my own. Thanks.

I know these replies are all saying the same thing, but I’ll echo the sentiment of the last responder… I would not have found that on my own either, and I found your post in like 30 seconds on my first try. I’m not sure how you found that (I’d love to know) or maybe you’re just really good w/ LE, but a huge thank you my friend!

I’m actually kind of surprised that this hasn’t been fixed in some way, or this kind of solution incorporated into the instructions for doing a backup / restore / move of you MIAB. In my case, I was upgrading a couple of months ago from an older Linux image to the more modern one, and I went through the process documented on MIAB for backing it up and restoring on my new installation. That all worked perfectly and there was no indication that there was a lurking problem with duplicate LE certs… for a couple of months anyway. I’m going to try and write something about that in the dev forums so that hopefully it can get addressed.

Again, you’re a real hero here man. You helped a lot of people out with this one, so again thank you!

Everyone is welcome to fix it.

But this is already documented … Mail-in-a-Box Maintenance Guide

In the “Moving to a new Box” section: