acme-v01.api.letsencrypt.org Reprecated?

[mrnb]

These messages have appeared in the DNS Resolver logs since this morning:

Jan 16 15:51:04	filterdns	27598	failed to resolve host acme-staging.api.letsencrypt.org will retry later again.
Jan 16 15:51:04	filterdns	27598	failed to resolve host acme-staging.api.letsencrypt.org will retry later again.

I'm currently using the ACME certificates for a lot of hosts via HAProxy. Is this something permanently broken with the package or something temporary?

Is anyone else seeing this issue?

[patient0]

@mrnb said in acme-v01.api.letsencrypt.org Reprecated?:

acme-staging.api.letsencrypt.org

I don't use it much myself, but t doesn't resolve for me either, acme-v02.api.letsencrypt.org does though.

The internet shows that they switched to v2 in January 2018 (https://community.letsencrypt.org/t/staging-endpoint-for-acme-v2/49605). Maybe they finally switched of the old URL?

[Gertjan]

@mrnb

Why do you think the 'acme' (pfSense package) is broken ?
Question : Where does this host name "acme-staging.api.letsencrypt.org" come from ?

[24.11-RELEASE][root@pfSense.bhf.tld]/usr/local/pkg/acme: grep "acme-staging.api.letsencrypt.org" *
(not found)

so not from acme.
Where does it really come from ?
Here :
login-to-view

Who feeds filterdns with host names to resolve ?
The pfSense admin
You've entered this host name somewhere under Firewall > Aliases > IP.
Maybe it's time to edit ?

edit : staging ... wasn't that URL meant to be used for testing purposes only ? The certificates obtained when using

login-to-view

are not 'valid'.
I remember using it once, years ago, for half an hour or or to test drive my setup, as I can do as many test as I want.
As soon as I had the setting right, I switched over to the second option in the list, and never came back to this page.

[mrnb]

@Gertjan

Oh you helped solve the problem!

Thank you!