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
Zerossl Register account Error #5062
Comments
Please upgrade to the latest code and try again first. Maybe it's already fixed. |
In the logs of --debug 2 you can obviously see that it is the latest version. |
On my server I currently have a letsencrypt certificate with no problem.
I attempt to change to zerossl and it does not allow me to do so.
My problem is located in the user registration, I have seen several Issues with the same problem but none of them has a clear solution, usually the Issue ends with the phrase "it works for me with the last code update". That answer obviously doesn't work for me, I have the latest version of acme.
I want to find out why it doesn't work because I've tested it on another server and it does work, but I can't find the difference that causes it to fail.
Mi output from ```.acme.sh/acme.sh --register-account -m [email protected] --debug 2````:
UPDATE:
I tried previous versions and I was able to register and issue without any problems on version 3.0.2 but in version 3.0.3 the problem arises.
UPDATE2:
I have found that the error starts to appear as of this commit in version 3.0.3
My Openssl version is 1.0.1 so when I do
openssl base64 -d
without the-A
option during _dbase64 registration it returns an empty stringUPDATE3:
I think the problem is related to the fact that during registration a _dbase64 multi request is made, specifically with the
multi
option, which would imply that the base64 string to be decoded is a string with a character length of > 64 that is separated by line breaks, where each initial or intermediate line is of length == 64 and the last line being <=64. However, the base64 string to be decoded, the eab_hmac key that is automatically generated if none is stored or the one found in the web dashboard has a length greater than 64 characters and no line breaks separating it. Hence I understand that there is a bug and themulti
option should not be passed, because although in openssl 1.1.1 and greater it works without problems, it fails for openssl 1.0.1.@Neilpang coul I have your opinion?
The text was updated successfully, but these errors were encountered: