Help with standalone certbot: "Failed to bind to :80 using IPv4"

[schoen]

@dwelchmd

Only problem now is that I'm not sure how to automate renewal without using port 80 or 443, since 80 is apparently not an option and I am using 443. Looks like I'll have to manually renew and change my port forwarding every time, which is not ideal. I'll read more about this to see if there's a work around.

(edited) This is a little strange, because people are routinely able to use Let's Encrypt client software to automate renewals using port 443. It would be great to know why people think that it can't be done in this case.

In particular, certbot-auto renew should still be able to renew via port 443 just as it could with port 80. And if you can run it from a cron job, it should still be able to do so automatically!