Skip to content

/ server

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

certbot: error: unrecognized arguments: -encodedCommand MAA= xml -outputFormat text #535

Open
lkloon123 opened this issue Jul 21, 2019 · 9 comments
Open

certbot: error: unrecognized arguments: -encodedCommand MAA= xml -outputFormat text #535

lkloon123 opened this issue Jul 21, 2019 · 9 comments

Comments

@lkloon123
Copy link

@lkloon123 lkloon123 commented Jul 21, 2019

Hi, may i know why this certbot error occurs?

Status: Downloaded newer image for certbot/certbot:latest
usage:
  certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...

Certbot can obtain and install HTTPS/TLS/SSL certificates.  By default,
it will attempt to use a webserver both for obtaining and installing the
certificate.
certbot: error: unrecognized arguments: -encodedCommand MAA= xml -outputFormat text
@kspearrin
Copy link
Collaborator

@kspearrin kspearrin commented Jul 21, 2019

I have no idea, sorry. Never seen this error before.
@DonDino2
Copy link

@DonDino2 DonDino2 commented Oct 20, 2019

I am also seeing this error right now, during attempts to reinstall Bitwarden on my Win10 system.
@hiyan
Copy link

@hiyan hiyan commented Nov 15, 2019

I'm getting the same error. First try no such error. Then i screwed up and tried again (deleted bwdata folder) and now i'm getting the error.

Am on win10
@DonDino2
Copy link

@DonDino2 DonDino2 commented Nov 15, 2019

Unfortunately I never solved the mystery. I ended up reinstalling Windows but I now host Bitwarden on a linux server instead.
@lkloon123
Copy link
Author

@lkloon123 lkloon123 commented Nov 20, 2019

@DonDino2
yeah me too, seems like windows is producing the problem.
@hiyan
Copy link

@hiyan hiyan commented Nov 21, 2019

Update: Wasnt able to get it working.

Workaround: Since I had WSL running, I just ran certbot there and copied the files over manually. Working fine now.
@averkiev
Copy link

@averkiev averkiev commented Jan 8, 2020

Same error here on clean install of Windows 10 Pro 1909.
@alexwaibel
Copy link

@alexwaibel alexwaibel commented Apr 18, 2020

I am also having this issue on Windows 10 Pro 1903.

@hiyan could you elaborate on how you were able to run certbot on WSL? When I try this using sudo certbot certonly --standalone I get the error The key authorization file from the server did not match.
@hiyan
Copy link

@hiyan hiyan commented Apr 20, 2020

@alexwaibel I did not have this error. I believe yours may be a different error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants
@averkiev @kspearrin @hiyan @alexwaibel @lkloon123 @DonDino2
You can’t perform that action at this time.