Porkbun changed their api

[mrchip]

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

[YJBrian]

@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)

[Gertjan]

@YJBrian

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

login-to-view

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.

[YJBrian]

@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]

@YJBrian

Hummmm.

0.9_1 is the latest version that uses "api.porkbun.com".
That's what I have ...

[YJBrian]

@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.
login-to-view

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...

[Gertjan]

@YJBrian

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.

[luxor84]

I'm happy to share with you how I solved this problem after making a few researches.

First of all, I installed through the Package Manager the package "System_Patches".

Then I went to System > Patches and I created a Custom System Patch.
login-to-view
Use the description you want and use this URL for the Committ ID: https://github.com/WereCatf/pfsense/commit/b4258a0d5730cb1bc6eecca6ad4f19b3797f8a4c.diff
Then apply the patch.

Next step is to edit the file /usr/local/pkg/acme/dnsapi/dns_porkbun.sh
I used the tool Diagnostic > Edit File to change the line PORKBUN_Api="https://api.porkbun.com/api/json/v3 to PORKBUN_Api="https://porkbun.com/api/json/v3 and then I saved the file
login-to-view

After that, as I went to Services > Acme Certificates and I clicked on Issue/Renew.... the Certificate was updated!

[YJBrian]

@luxor84 said in Porkbun changed their api:

https://github.com/WereCatf/pfsense/commit/b4258a0d5730cb1bc6eecca6ad4f19b3797f8a4c.diff

Thank you, I'll be honest, I'm not following the patch part of your solution. I ran across the fix in the GIT repository and simply edited the Prokbun.sh file to point to the new URL as you did in the last step. Reinstalling the package reverts the file to the old URL, but I'm wise to the problem now :)