@johnpoz Ahhh ok! Perfect! Thank you!

@dutsnekcirf said in Is there a DNS-NoIP option?:

My public DNS is provided by No-IP.org and I've managed to get a certificate created using the DNS-Manual method. My understanding is that this verification method does not allow for automatic certificate renewal. Is there one of the automated verification methods that I could use with no-ip.org? Thanks!

I recently went through this same situation. I switched from Dyn-DNS to No-IP only to find out that No-IP does not expose API keys or anything to allow the acme package to perform the DNS changes necessary for automatic renewal.

I ended up canceling no-ip and moving to cloudflare. Cloudflare is actually great once you get it setup and so far, free for what I am doing as well.

Found the solution:

there must be 2 CNAME records according to
https://github.com/acmesh-official/acme.sh/issues/2789

one for _acme-challenge.domain,tld to _acme-challenge.domain.tld
and a second one for _acme-challenge.pfense.domain.tld to _acme-challenge.domain.tld.

@sensewolf

What did the green 'log' in the GUI tell you ?

Or, better : zero the log file I mentioned above.
Do a manual renew.
Look at the file again, it has many lines now.

Upload them to (whatever) => pastebin.org
Past the link here.

Btw : be careful, don't press several times per day at the manual reew button : after 5 times or so, you'll get blacklisted for a day, as the number of times you renew a cert is limited.

@sgw said in Exchange 2016 - pull LE cert from pfsense:

If Exchange should really require 128 GB RAM, that customer is out of the game anyway

That was basically our thought process. I checked around a bit and some people with smaller servers said Exchange 2019 seemed to be OK with 64 or 92 but in the big picture I think Microsoft expects enterprises to run their own servers, and everyone else to use 365.

re: maintenance, Microsoft only releases security updates for supported versions of Exchange which is the last two Cumulative Updates of each version. This MS page is noisy but if you look closely only the Exchange 2016 CU22 and CU23 lines have links because they are supported, and CU21 has no updates after March. Essentially, every 3-6 months one must install a CU which in my experience takes 2-3 hours because it's essentially a full Exchange install each time. If someone isn't installing those, no security updates for Exchange are installed via Windows Update. It just quietly doesn't see any.

Exchange 2016 ends support in Oct. 2025. Microsoft only allows/supports migrations for the prior two versions. So your customer will need to move to Exchange 2019 or "Exchange 2022" or whatever it will be called by 2025.

None of that is anywhere near your question but that's why we moved off local hosting, and none of it is our problem anymore. :)

Hi Everyone,

I asked the same question over in the Let’s Encrypt forums, and I got some great answered and clarification on what I was trying to do. https://community.letsencrypt.org/t/acmev2-ssl-with-google/187727/18

Hopefully Google will do ACME wildcard verification through Google Domains in the future.

I am seeing same issue in 2.6.0-RELEASE with ACME 0.7.3 package.
Provider is Cloudflare in DNS domain alias mode.

Generating cert using 256/384 ECDSA key works, but even after switching to RSA 4096 still gives 2048 bit key cert.

@flemmingss

Aha : You are using the pfSense HAproxy package.

Go back to the

2e218531-a3fd-4bbb-8478-530e10807cc3-image.png

page, and start reading.
This time, up until the bottom.

You will find the very important dns sleep.
That's why it's there.

And also this one :

f3426682-5bbe-4a3e-920a-8bef7be592c6-image.png

as it was made for you.

The certificate name will not change when it is renewed. No need to select 'another' cert in the HA Proxy settings.

Now, when acme.sh successfully renewed the certificate, it will also restart HAproxy. So it takes in account the renewed certificate.
And you can go back to the admin's main task : constantly ( 😊 ) checking if all automated tasks are correctly executed.

@gertjan Don't Worry I bought different domain name from NO-IP and the certificate started working with it.
Thank you for your help.

@ms264556 said in How do we request a new package release?:

and easy

Before you click on 'get me 2.7.0', read the top most messages from this forum : pfSense® > Software Development > CE 2.7.0 Development Snapshots

Thank you for the explanation.

I don't expose the GUI to the WAN, and frankly I have little need for SSL to my pfSense beyond getting rid of the annoying "Invalid SSL Cert" interstitial page when logging in from an internal machine. Using "dave.duckdns.org" internally works nicely for this, solving my problem.

Has anyone had any luck resolving this issue?

I'm also seeing this exact issue on 2.6.0 with the acme 0.7.1_1 package.

Deleting the CA doesn't seem to work as it just gets re-created.

@gregoinc I just went through this myself. I originally had made all my own certs and added them to clients root cert authority but the self hosted web interface for my home security system doesn't allow for adding of ssl certs. Since I already have a paid for domain name for 10 years and this was so easy I just set it up for all my home private severs on LAN. I know I'm about a month late, but for anyone else maybe it will help. YouTube: How To Create pfsense Let's Encrypt Wildcard Certificates using HAProxy

https://github.com/acmesh-official/acme.sh/wiki/dnssleep

@seanmcb said in ACME renewal timeout and "No doh":

In dns manual mode, after the dns record is added manually, acme.sh will use cloudflare public dns ....

as cloudflare public dns or google dns are only used when dnssleep is not set.
dnssleep is pretty mandatory when using some API/auto mode.
But not for manual mode (human interaction is slow by default ;) )

dnssleep exists because DNS syncing takes an unknown time.
The DNSAPI mode uses a script file and your access credentials so you it can add (and afterwards : remove) one or more TXT records. You will be updating the DNS domain name master DNS only. There should be at least one DNS slave, and it will get signalled 'by the master there is an update' in the zone.
The zone slave can then initiate a zone transfer whenever it wants, it could be right away, or x second / minutes later (the zone master admin determines the sync parameters).

When the zone is synced, LE is signalled to proceed with zone checking. It will locate the domain name servers, pick any of them, and checks the TXT record.
Btw : I thinks it checks all the listed name servers.

When using manual mode, there is no need to wait ..... sleep == dnssleep, as it will take you some time to connect to the GUI that allows you to set the needed TXT records in your domain zone
Because you didn't use dnssleep acme.sh will do now an extra step for you when you proceed : it will do a dns zone check for you by using cloudfare, google DNS etc.
So acme.sh will only signal LE to proceed with the zone checking if it knows that the TXT records are actually set (and the admin who sets the TXT records manually didn't make a mistake).

I don't understand why this check isn't actually made also when DNSAPI mod is used, as an extra local check step before LE is asked to check and deliver a cert.
My for some sites where acme.sh is used there is no google or cloudfaire access ( pfblockerng users ;) )

All this is my opinion of course.

From your https://redmine.pfsense.org/issues/13495

the purpose of the field is not to "configure how much time to wait before attempting verification" but rather it's to disable verification and instead wait the specified numbers of seconds. This is useful for people like me that block access to cloudflare and google DNS.

Well, it is waiting xxx seconds after a "successful TXT field insertion".
During this time, DNS master and slave(s) should do their sync magic.
Then control is given back to LE so it can do its checking, and give you back a cert if it was successful.

I guess this dnssleep parameters serves somehow a double function.
When absent (not set) acme.sh will do a local check using a known DNS resolvers. I tend to say : to inform you that you did your manual work ok.

IMHO :the ddnssleep can be very low, but can't be zero in 99,99 % of all cases.
It should be set to "120" if you didn't modify that setting.

Btw : I'm using nsupdate ( dns_nsupdate.sh ) method as I do not use the API of my registrar : I'm hosting my own domain name master and several domain name slaves (bind). These domain name servers only host my own domain names, so they have not much to do.
I can follow the update process while tracing the logs everywhere = the adding of the two TXT records, the signalling of the master to the slave, the reception of this signal by the slaves, the slaves that call back the master for a zone sync.

One in a while, I also use freedns.afraid.org as an extra dns slave, and the sync back of freedns can take to up to 5 minutes to sync with my master. When I use the dns salves of my registrar, this can even take longer, as they have zillions of zones (domain names) to handle.

nevermind i solved it
didnt have the letsencrypt key.
I thought clicking save would create it

Just a nudge on this question, currently I am having to disable 2FA when I want to renew.

Does anyone know how the he.net integration works, is it simply scraping dns.he.net or is it usign an API?

According to he.net it should be doing something like this ..

curl "https://dyn.dns.he.net/nic/update" -d "hostname=_acme-yourdomain.com" -d "password=txtRecordKey" -d "txt=ACMEChallenge"

That is most likely a problem with your apache SSL config, not ACME or pfSense.