I am looking for a minimalist approach. What firewall rules are needed?
I've allowed inbound access on port 80 and 443, for .letsencrypt.org/ to an external loadbalancer that forwards the tcp to my nginx ingress-controller. however I gett acme authorization failed.
I have made it so that the site is available only to letsencrypt and internal.
Hello @cccsss000111 , welcome to the Let's Encrypt community. 
Let's Encrypt uses several IP Address and other CDN providers in the challenges, so limiting to .letsencrypt.org is likely to fail most of the time.
Also there is NO LIST of IP Addresses published FAQ - Let's Encrypt
A great place to start debugging Let's Encrypt certificates is Let's Debug
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Thank you for assisting us in helping YOU!
Allow the path /.well-known/acme-challenge/ and you're good to go. LE does not provide a list of IP addresses used for validation and they are from all over the world. And they can change at any moment. So either allow the specific path for the challenge or use the dns-01 challenge.
Move to Help from Issuance Tech for better visibility.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.