Post BAVN9yzognXtWpmlxA by selea@social.linux.pizza
 (DIR) More posts by selea@social.linux.pizza
 (DIR) Post #BAVBtdNqB3qgMy1a88 by selea@social.linux.pizza
       0 likes, 0 repeats
       
       @niqdanger Do you have the complete certificate chain in the crt-file?
       
 (DIR) Post #BAVCSkNQAW34C5ZUDg by niqdanger@social.linux.pizza
       0 likes, 0 repeats
       
       @selea  Yup! host, interm (x2) and root CA. I did cheat and use the old CSR, Im going to start fresh with new key/csr/cert and try again, see if that fixes it.
       
 (DIR) Post #BAVFbZvmftfMGXXzGa by selea@social.linux.pizza
       0 likes, 0 repeats
       
       @niqdanger https://blogs.linux.pizza/how-to-properly-generate-a-csr-fileIf that helps :)
       
 (DIR) Post #BAVIi2IMQjVjprsV28 by niqdanger@social.linux.pizza
       0 likes, 0 repeats
       
       @selea That did it. Regen from scratch, new key, csr and then cert issued. (blog helped with the openssl -req) gitlab-ctl reconfigure and restart. All well. Now I have until December to get acme.sh working to generate new certs for gitlab since it only supports LetsEncrypt natively and I use a different CA.  Thanks!
       
 (DIR) Post #BAVN9yzognXtWpmlxA by selea@social.linux.pizza
       0 likes, 0 repeats
       
       @niqdanger acme.sh should support other CA's with ACME support (like Digicert, Comodo and so on)Otherwhise check out Lego (https://go-acme.github.io/lego/)