-
Notifications
You must be signed in to change notification settings - Fork 64
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
A way to force using wget #3
Comments
@ColtonDRG Yes, I will consider it. For now, as a temp workaround, please add a file in you home dir:
Then your curl should be able to work. |
Please give me the output if you still have problems. |
Same error: |
fwiw, if I manually make it use wget by editing get.sh and running it, I get the following.
|
@ColtonDRG fixed. export ACME_USE_WGET=1
wget -O- https://get.acme.sh | sh |
Ok, now I'm getting a different problem. Perhaps I should give up on getting a certificate for my router (at least from my router, getting one on another computer and uploading it could still work).
|
Please check if your wget --header "a:b" https://www.google.com |
It does not.
|
The copy of curl included with my router firmware does not support https. The copy of wget in it does, but even if I use wget to execute get.acme.sh, the script still searches for curl and uses it by default.
I know I have a unique use-case trying to get an SSL cert for a router, but it would be nice if this was supported. This is (as far as I know) the only shell script style ACME client that doesn't require bash or some other more advanced shell. The router runs busybox, which of course only implements ash.
The text was updated successfully, but these errors were encountered: