Cannot Configure PFSense ACME Package wtih DYNU Cannot Configure PFSense ...

Topic: Cannot Configure PFSense ACME Package wtih DYNU

Post Cannot Configure PFSense ACME Package wtih DYNU
by rickskirch on lundi 3 juillet 2023

Hey folks, Here is the setup:
1. PFSense 2.7.0
2, ACME Package: 0.7.4
3. DYNU Paid Membership

ACME Package Section Domain SAN List has a DYNU method. The pertinent inputs are :
API Client ID: Dynu API Client ID created in the Dynu account settings
Secret: Dynu API Secret

The issue is that the transaction section only contains the shared secret, but no client id. I have tried my username, but that is not working. is there a way to generate a client ID (I could not find this), or another method (DNS-NSupdate / RFC 2136, although I tried messing with this and had no luck)?

Logs of transaction with username/key:

[Mon Jul 3 19:30:00 PDT 2023] Using CA: https://acme-v02.api.letsencrypt.org/directory
[Mon Jul 3 19:30:00 PDT 2023] Single domain='remote.kt1.in'
[Mon Jul 3 19:30:00 PDT 2023] Getting domain auth token for each domain
[Mon Jul 3 19:30:01 PDT 2023] Getting webroot for domain='remote.kt1.in'
[Mon Jul 3 19:30:01 PDT 2023] Adding txt value: sOOnlBJJkzphydIu8rcr71pPLTZmKa6GJiijhnacNyc for domain: _acme-challenge.remote.kt1.in
[Mon Jul 3 19:30:01 PDT 2023] Getting Dynu token.
[Mon Jul 3 19:30:03 PDT 2023] Getting https://api.dynu.com/v2/dns/getroot/remote.kt1.in
[Mon Jul 3 19:30:03 PDT 2023] Getting https://api.dynu.com/v2/dns/getroot/kt1.in
[Mon Jul 3 19:30:05 PDT 2023] Getting https://api.dynu.com/v2/dns/getroot/in
[Mon Jul 3 19:30:03 PDT 2023] Authentication failed.
[Mon Jul 3 19:30:03 PDT 2023] Can not get token.
[Mon Jul 3 19:30:05 PDT 2023] Invalid domain.
[Mon Jul 3 19:30:05 PDT 2023] Error add txt for domain:_acme-challenge.remote.kt1.in
[Mon Jul 3 19:30:05 PDT 2023] Please check log file for more details: /tmp/acme/kt1Cert/acme_issuecert.log

Thanks, Rick

Reply with quote | Report
vendredi 21 juin 2024 01:23
Loading...