Cannot Configure PFSense ...
Cannot Configure PFSense ACME Package wtih DYNU
- 主页
- 后台控制中心
- Community Forum
- Services
- Dynamic DNS Service
- Cannot Configure PFSense ACME Package wtih DYNU
- Community Forum
- Cannot Configure PFSense ACME Package wtih DYNU
Topic: Cannot Configure PFSense ACME Package wtih DYNU
Hey folks, Here is the setup:1. PFSense 2.7.02, ACME Package: 0.7.43. DYNU Paid MembershipACME 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 settingsSecret: Dynu API SecretThe 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.logThanks, Rick
Reply with quote | Report
Author | Topic: Cannot Configure PFSense ACME Package wtih DYNU |
---|---|
rickskirch Joined: 2017/5/25 |
Cannot Configure PFSense ACME Package wtih DYNU 2023年7月3日 19:46
Hey folks, Here is the setup:1. PFSense 2.7.02, ACME Package: 0.7.43. DYNU Paid MembershipACME 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 settingsSecret: Dynu API SecretThe 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.logThanks, Rick
|
It is currently 2024年10月8日 12:06 US Mountain Standard Time
2024年10月8日 12:06