-
Notifications
You must be signed in to change notification settings - Fork 269
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
Error in Step 3: Account registration failed. Please start back at Step 1. #175
Comments
I'm facing exact same issue |
same here .. |
same... |
me too |
Same error as well. Appears that site is indeed broken at step 3 |
For anyone looking for another solution to create a certificate manually on your local computer, you can use Certbot with the --manual flag & dns validation, as explained here https://help.datica.com/hc/en-us/articles/360044373551-Creating-and-Deploying-a-LetsEncrypt-Certificate-Manually You may need to change your network interface's MTU size if certbot returns "connection reset", as explained here https://community.letsencrypt.org/t/error-coming-through-when-trying-to-get-ssl-verified-with-my-domain/118654/9 |
This happens to me when trying to use the wrong account public key for the domain im trying to generate a cert for. Generating a new public key works for me in this case. |
I finally managed to get the certificate with https://gethttpsforfree.com/
But just that you know gethttpsforfree is working 2022! Even the repo is quite inactive. |
Non-working script, idiotic geek-shmick "free" CA with install method not working for the most of the people :( Wasted a lot of time, got NOTHING :( How "fast" I should be?! What the idiotic suggestion?! |
I feel you @sensboston. I had so many frustration while doing this. Still don't understand why sharing my usage experiences here are idiotic? I just wanted to describe to others how I finally was able to use this successfully. I think i made it clear it was not easy and sure it is almost impossible to use but I managed to do so with these instructions. It is not my fault the process is buggy but I noticed that it works if the steps is executed in fast enough pace. I don't have any absolute time frame. Fast enough for me was when it didn't fail anymore. It did fail so many times either because of this or copy/paste error that I also thought it didn't work. Just wanted try "just one more time" enough times. |
Simple because of this:
Yes, it's silly and idiotic, software world isn't working this way. And try to tell your idiotic (yes, it's IDIOTIC!) suggestions to the people with disability, to push 'em retry process without any chance of luck :(
Double, triple IDIOTIC! |
You're being rude because you blame on me that you wasted your time. If software world is never time dependent and my suggestions were so idiotic why did you decide to try... actually i don't want to know. For everyone else I want to tell that I have successfully used this 3-4 times and always it fails a couple of times when I am not fast enough with my copy/paste. So it is up to everyone if you want to give a chance for this. Cannot recommend but if you don't have any other solution... maybe you get it to work like me. |
I understand your frustration at your time being wasted and maybe it's a language barrier issue, but you are being a bit rude & entitled to someone who's sharing his experience to help others for free. The code is free and open, you're welcome to fix it if you feel so strongly about it. |
If you encounter problems, you can try my webpage: https://xiangyuecn.github.io/ACME-HTML-Web-Browser-Client/ACME-HTML-Web-Browser-Client.html |
Step 1 and 2 worked fine but in step 3 I get the following error:
I tried a second time and got the following error:
I entered the single line output of the
echo -n "eyJ1...1ZX0" | openssl dgst -sha256 -hex -sign $PRIV_KEY"
command as:(stdin)= 1a7f....0835
(actual full strings shortened here for brevity).
Maybe the nonce part of the ACME protocol changed or something?
The text was updated successfully, but these errors were encountered: