Managing Let's Encrypt Certificates in Restrictive Network Environments #39212
-
I have a question about Let's Encrypt certificates. I've configured a public IP on my Teleport, and currently, it's set up and running smoothly. Now, I want to restrict access to port 443 only to known IPs, blocking all other accesses from the internet. However, I'm not sure how Let's Encrypt is functioning at the moment. I know their certificate lasts for a few weeks and then renews automatically. My question is, if I implement this block on port 443, will Let's Encrypt continue to function by automatically updating the certificate? Can I manually control Let's Encrypt to force certificate renewal when I bring down the firewall, or are there specific IPs from Let's Encrypt that I can add as trusted in the list? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Let's encrypt does not publish their IPs AFAIK. I would consider leveraging the DNS challenge renewal path. The certs there can last 3 months. You would need to set the certs within the proxy service. |
Beta Was this translation helpful? Give feedback.
-
I managed to set it up using DNS. I followed the Digital Ocean tutorial to guide me on what to do, then I just followed what was in the teleport [documentation](I managed to set it up using DNS. I followed the Digital Ocean tutorial to guide me on what to do, then I just followed what was in the teleport documentation).
Now, I'll wait for the expiration date to see if it worked. |
Beta Was this translation helpful? Give feedback.
Let's encrypt does not publish their IPs AFAIK. I would consider leveraging the DNS challenge renewal path. The certs there can last 3 months. You would need to set the certs within the proxy service.