the ux of certbot and nginx interactions is unconscionable
@notplants Didn't they recently add a Acme client into nginx itself?
they did @forestjohnson, and I set it up earlier today on a debian server and it seemed to work well (the nginx-acme plugin)
then later I was supposed to help a friend who is not a programmer set a website up their server. their server already had ubuntu. ran into issues installing nginx with acme on ubuntu for some reason, then aborted and tried to use certbot
but explaining the chicken-and-egg dance of setting up certbot and nginx configs to non-programmer friend seemed impossible
@forestjohnson but I was thinking of you , and how this operational burden of this interaction is considered acceptable ... and i worked myself up into a frustrated state and then posted the post
@notplants Yeah, and even Caddy is no perfect savior here because it is still doing the happy path only, with some logging that is not exactly intuitive when it doesn't work. And it has to deal with DNS caching issues. which are generally impossible to deal with in a user friendly way.
@notplants Also obligatory caddy shilling, I guess.