1. 1

The certificate is only valid for lobste.rs

I have www.lobste.rs in my browser history and keep hitting it by mistake.

  1.  

  2. 4
    1. 1

      OK, thanks!

      1. 1

        Question is why it’s taking this long to just generate a new cert with the extra SAN…

        1. 4

          No one is paid to work on lobsters. If you know ansible and letsencrypt you should be able to help out.

          1. 1

            Well I don’t really know how the current Lets Encrypt cert was generated, but it’s literally just another argument. Did ask about it when it came up on IRC 3 weeks ago, but didn’t get a reply then, and figured it would probably be fixed pretty quickly then so completely forgot about it.

            1. 1

              It was manually created with certbot but, as noted in the bug, should probably be replaced with use of acmeclient to have much fewer moving parts, if nothing else.

              It’d be great to have someone who knows the topic well to help the issue along in any capacity, if you have the spare attention.

              1. 1

                I’ve done entirely too much work with acmeclient to automate certs for http://conj.io and some other properties I run. Will try and find time this weekend to take a run at this.

                1. 1

                  That or to use dehydrated: in a text file, one certificate per line, each domain separated by a space.