Our system uses anycast for DNS (DOH and DOT) services. We'd like to use IP authentication, since our IP addresses are useds by clients to bootstrap or directly communicate with our systems. I see a few problems with the current model that has been documented for IP address certificates, and I'm wondering if there can be a discussion on the topic. Cert time is too short. We own our own /24's and /48's for use, and we are listed as the "owners" of the address space in the RIR. It seems tha...| Let's Encrypt Community Support
My domain is: bitcastle.lol I ran these commands: sudo certbot renew --nginx --cert-name bitcastle.lol --dry-run sudo certbot certonly --nginx --cert-name bitcastle.lol --dry-run They all failed the with same result: authenticator: nginx, Type: unauthorized, Detail: ... Invalid response from https://bitcastle.lol/.well-known ... 404 And I see 404 status codes in nginx access.logs and perhaps more notably i see in the error.logs No such file or directory looking for the acme-challenge/| Let's Encrypt Community Support
So I went to the router, to the WAN section, then went to the "Virtal Server/Port Forwarding" section, and then in the "Port Forwarding List" section, I made the settings that I showed in the screenshot.| Let's Encrypt Community Support