plugins
plugins copied to clipboard
DNS-01 - All-Inkl Domain API - OUTDATED
Hi there. Using acme.sh .. with OpenSense..
ACME.SH is for All-Inkl Domain API .. not up2date //
| 2022-08-07T20:08:42 | acme.sh | [Sun Aug 7 20:08:42 CEST 2022] timeout= |
|---|---|---|
| 2022-08-07T20:08:42 | acme.sh | [Sun Aug 7 20:08:42 CEST 2022] url='https://kasapi.kasserver.com/dokumentation/formular.php?kas_login= |
| 2022-08-07T20:08:42 | acme.sh | [Sun Aug 7 20:08:42 CEST 2022] GET |
The new URL is for ALL-Inkl. ::
https://test-account.com/formular.php
-- https://kasapi.kasserver.com/dokumentation/formular.php <-- is outdated!! Doesn't work anymore..
so someone need to fix it from 👍
https://kasapi.kasserver.com/dokumentation/formular.php > https://test-account.com/formular.php
could someone fix it, that OpenSense got the right version ... included that Fix!
And :: SHA1 doesn't work from 12/2022, they use : plain instead of SHA1 .. So someone needs to fix // ALL-INKL. Domain for ACME..
Regards
Thank you for creating an issue. Since the ticket doesn't seem to be using one of our templates, we're marking this issue as low priority until further notice.
For more information about the policies for this repository, please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.
The easiest option to gain traction is to close this ticket and open a new one using one of our templates.
https://kasapi.kasserver.com/dokumentation/formular.php <-- is outdated!! Doesn't work anymore..
This cannot be fixed in OPNsense, it needs to be fixed in the upstream acme.sh project. There are already pending PRs (https://github.com/acmesh-official/acme.sh/pull/4222, https://github.com/acmesh-official/acme.sh/pull/4219). When a fix is merged and included in an official release of acme.sh, it will automatically be available in one of the next OPNsense releases.
And :: SHA1 doesn't work from 12/2022, they use : plain instead of SHA1
This was addressed in https://github.com/opnsense/plugins/pull/3068.
Hi bashinator if you have shell access to your machine, you can try the dns_kas.sh script from the pull requests mentioned. Cheers
i can't need - to wait for opensense fix // still no url change .. :)
| 2022-08-19T20:51:57 | acme.sh | [Fri Aug 19 20:51:57 CEST 2022] url='https://kasapi.kasserver.com/dokumentation/formular.php?kas_login= |
|---|---|---|
| 2022-08-19T20:51:57 | acme.sh | [Fri Aug 19 20:51:57 CEST 2022] GET |
-- still old url :: doesn't work for ALL-INKL
https://kasapi.kasserver.com/dokumentation/formular.php <-- is outdated!! Doesn't work anymore..
so someone need to fix it from 👍
https://kasapi.kasserver.com/dokumentation/formular.php > https://test-account.com/formular.php
dunno how hard that mess is :)
Hi bashinator, Bug is still fixed. So you have to wait until opensense pull the latest version. URL change doesn’t fix the issue!
[Tue Sep 6 15:22:34 CEST 2022] url='https://kasapi.kasserver.com/dokumentation/formular.php?kas_login=
06.09.2022 - still no "PULL" from opnsense? Works fine.. NOT!
OpnSense coming up with "" acme.sh | Version : 3.0.4
os-acme-client | Version : 3.13
Since 18Days no upgrade? Yeah Marco, there is still not a fix outside ?? :) OLD URL STILL INCOMING !! BUT, PLAIN <Passwd> is up2date.. so there was a fix, but nobody fix the damn URL..
regards
The statement I've made is still valid:
This cannot be fixed in OPNsense, it needs to be fixed in the upstream acme.sh project. There are already pending PRs (https://github.com/acmesh-official/acme.sh/pull/4222, https://github.com/acmesh-official/acme.sh/pull/4219). When a fix is merged and included in an official release of acme.sh, it will automatically be available in one of the next OPNsense releases.
Simply put: there is still no new release of acme.sh available.
This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository, please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.