@Gertjan said in ACME using dynv6:

but I can't see the usefulness of publishing my "pfSense LAN-ipv6-address".

You don't publish it, you use it, to update only the prefix part of a given dns-record.

I for example changed to only use ULAs in my LANs. But also I have some "unused" VLANs set to "Track Interface" to get the daily changing prefixes to then use them with NPt for my ULA-LANs. I would benefit from what I have described before.
If you, as an expert user, found a solution, that works for you, that is great. I still wait for pfSense to bring a better solution to this for the rest of us.

@SteveITS Feature request created: https://redmine.pfsense.org/issues/16150

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

I ended up signing up for duckdns and users still use my old no-ip.com ddns. apparently lets encrypt certs work on multiple domains

@Maxpower said in Issue with ACME Certificates Refresh & Restarting HAProxy:

For this, I have configured the command /usr/local/etc/rc.d/haproxy.sh to restart HAProxy, as its described in the GUI

What exactly did you do here ?
Can you go into detail ?

Thanks for the insight, that resolved the issue

@Gertjan Yes it is but the GUI still laggs so at least now I know I can use the cert without waiting for GUI to update.

@Gertjan Thank you so much for the help. I've removed all of the child nodes of <acme>, reinstalled the package and it completed.

Thanks again!

@michmoor said in Unable to delete TXT record:

My domain expired

😊

@Gertjan

Oh you helped solve the problem!

Thank you!

The PHP error is a symptom of the configuration file being corrupted in some way. If I remember correctly, the corrupted configuration file is kept either in /tmp or /conf. If it exists, you can do a diff of the good and bad configuration file and post that here for review.

@tinfoilmatt it looks like I have finally gotten the certificate to pop up but now I am dealing with getting 503 Service Unavailable error. Do you know if this is an HAProxy issue or on the cloudflare side?

Screenshot 2024-12-05 at 12.51.02 PM.png

Under the General Settings tab, check Write Certificates, and then you can grab the full chain from /conf/acme/ after the next renwal.

Alternately, if you export a PKCS#12 archive instead of just downloading the cert, the archive includes the full chain.

@Gertjan
Thank you very much 😊 👍