Porkbun changed their api
-
Just a heads up. In acme I am using the prepopulated "DNS-Prokbun" dropdown. Was working great until I could not renew my cert. with a failure of " Error adding TXT record to domain: _acme-challenge.mydomain.com"
Called porkbun, they said they changed api url and now it should be: api.porkbun.com -
@mrchip Been confused by this for the last hour as well. The API URL was changed in ACME pkg v0.9 according to Bug #15821. I have 0.9_1 installed and this it still point to the old URL. Not sure this is not correct in this version (on pfsense CE 2.7.2-RELEASE)
-
So 2.7.2 is 'to' old ?
porkdns changes things that they really shouldn't change, like URLs ;)@YJBrian said in Porkbun changed their api:
ACME pkg v0.9 according
Upgrade the pfSense package ?
or, if 0.9_1 isn't proposed : upgrade first to 2.8.0 (it's probably better then great already) and then you'll have 0.9_1. -
@Gertjan Not saying there is something too old or necessarily wrong, more so that I don't understand (as a novice) if there is something amiss. I show I am running ACME version 0.9_1 and based on how I read the changes made to the package, the update to Porkbun's URL was implemented in this version, however, it is not updated on my system. Not sure why that is, but is easily corrected with a file edit.
-
-
@Gertjan Perhaps you can point out what I might be doing wrong - again on pfsense CE 2.7.2-RELEASE and showing I have ACME 0.9_1 installed.
If I open /usr/local/pkg/acme/dnsapi/dns_porkbun.sh, I have edited the file to point the updated URL as follows:
PORKBUN_Api="https://api.porkbun.com/api/json/v3"
I reinstalled the ACME package though the pfsense interface and open the file again and the URL has reverted to:
PORKBUN_Api="https://porkbun.com/api/json/v3"
Not sure what would cause that...
-
The 0.9_1 2.7.2 package wasn't updated.
Let Plan B be Plan A : upgrade 2.7.2 to 2.8.0 and call it a day ?
Or redo the edit manually, the next package upgrade will be ok anyway.
