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
dns_ispconfig.sh broken #3895
Comments
3.0.2 is not released yet. 3.0.1 is the latest released version. |
Released or not, the autoupdate function in acme.sh apparently updates it to 3.0.2 |
/root/.acme.sh/acme.sh -v /root/.acme.sh/acme.sh --server https://acme-v02.api.letsencrypt.org/directory --issue --dns dns_ispconfig --keypath /etc/pve/local/pveproxy-ssl.key --fullchainpath /etc/pve/local/pveproxy-ssl.pem --reloadcmd "systemctl restart pveproxy" -d domain.com You haven't specified the ISPConfig Login data, URL and whether you want check the ISPC SSL cert. Please try again. |
Yes, the old version works ok, so I overwritten it, but it's just a denture. |
fixed, can you guys please try with the latest dev branch?
|
@Neilpang I essentially already tested by editing the file on two of my machines that were giving the same error as above before reporting the commit as the problem; so "works for me". |
Without manually changing anything I can also confirm that your changes in the dev branch worked. |
Latest alterations in dns_ispconfig.sh broke the script!
As a result acme.sh is saying "You haven't specified the ISPConfig Login data" though it is specified in account.conf.
This happens when running the cron to autorenew and also when trying to get a new certificate from the command line.
After I replaced the script with the previous version all is working fine again.
What I also don't understand is why acme.sh is saying it's on version 3.0.2 when here on Github it says that latest version is 3.0.1
The text was updated successfully, but these errors were encountered: