From e94faba126bbbbaec7f990bc50c9387d26cd0eea Mon Sep 17 00:00:00 2001 From: Daniel McKnight Date: Thu, 3 Oct 2024 05:27:34 +0000 Subject: [PATCH] Add note to update DNS --- 2024-10-02_Cloudflare-DNS.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/2024-10-02_Cloudflare-DNS.md b/2024-10-02_Cloudflare-DNS.md index c5b15ae..c199a36 100644 --- a/2024-10-02_Cloudflare-DNS.md +++ b/2024-10-02_Cloudflare-DNS.md @@ -72,6 +72,9 @@ might get that running remotely for a more complete test. With routing all updated, that [configured certificate](#acme-client) can now be issued. After watching LetsEncrypt issue the certificate, I am confident that all of my changes were successful. +With the DNS Certificate issued, I updated nginx to use the new certificate and then restarted that service in OPNSense. I usually wait +a few minutes and then open a page in a private browser to check for the new certificate without worrying about the old one being cached. + ## Conclusion This was a quick change that I am very glad to have made. Now, I can add services/subdomains simply by updating Nginx and they will automatically have working SSL with a valid certificate. I am also interested in checking out all the analytics Cloudflare exposes;