mirror of
https://github.com/dehydrated-io/dehydrated.git
synced 2026-01-11 22:30:44 +01:00
letsencrypt.sh/dehydrated: line 80: unexpected argument `(' to conditional binary operator #148
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kayyazka on GitHub (Sep 21, 2016).
Hi,
I have problem on this line
letsencrypt.sh/dehydrated: line 80: unexpected argument `(' to conditional binary operator
And i change argument with add "" in (http-01|dns-01)
from :
dns-01) || _exiterr "Unknown challenge type ${CHALLENGETYPE}... can not continue."
to :
dns-01)" || _exiterr "Unknown challenge type ${CHALLENGETYPE}... can not continue."
after that. i run ./letsencrypt.sh --config /etc/pki/config.sh --cron
and i get error
ERROR: Challenge is invalid! (returned: invalid) (result: {
"type": "http-01",
"status": "invalid",
"error": {
"type": "urn:acme:error:unauthorized",
Additional information:
cat /proc/version
Linux version 2.6.18-8.el5 (brewbuilder@ls20-bc2-14.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP Fri Jan 26 14:15:21 EST 2007
uname -a
Linux 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:21 EST 2007 i686 i686 i386 GNU/Linux
cat /etc/*release
Red Hat Enterprise Linux Server release 5 (Tikanga)
what should i do to fix it?
Thank you in advance
@kayyazka commented on GitHub (Sep 21, 2016):
I have update new script but still error like it
@lukas2511 commented on GitHub (Sep 29, 2016):
Uff... support for linux distributions from the stone age...
You could try deleting the accounts directory, maybe there just is a broken account key, but I have a feeling that if this one line results in a problem some others might too...
I'll leave this open for now, but keeping compatibility with bash versions from probably over ten years ago is definitively not something I want to spend too much time on.
@lukas2511 commented on GitHub (Jan 30, 2017):
Not going to fix this, sorry.
I'd suggest trying to update your version of Bash, or better: Update your whole OS, does that thing even get security updates anymore?...