So, I setup GitLab about 2 years ago, and generated a certificate with our Microsoft PKI CA, it just expired. I don’t really remember all of what I did, but basically in /etc/GitLab/ssl there where three files, ca_cert.cer servername.crt, and servername.key. So I was following these instructions: https://docs.gitlab.com/omnibus/settings/ssl.html#details-on-how-gitlab-and-ssl-work and I created a new request, spit out a new p7b, converted that to a pem with openssl. copied it to /etc/GitLab/trusted_certs and ran sudo GitLab-crt reconfigure, but its still using the old cert. I ran the test from the webpage to make sure the .pem is fine, and it works, no errors, the symlink is created and exits, im not really sure what else to do. all the ssl info is commented out in my GitLab.rb. and the article mentions that there may be symlinks in /etc/GitLab/ssl/trusted_certs, but that directory doesn’t exist for me. I did notice that the symlink created in /opts/GitLab/embedded/ssl/certs also exists in /etc/GitLab/trusted_certs, and if I delete it, in both locations, it comes back after running GitLab-ctl reconfigure. Any help is appreciated. thanks.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Gitlab uses wrong SSL cert and I'm not even sure where it is! | 0 | 1078 | March 17, 2022 | |
After ssl cert replacement unable to reach gitlab page | 10 | 3464 | February 8, 2022 | |
Need Assistance installing SSL certificate | 5 | 1278 | February 23, 2021 | |
GitLab / Letsencrypt didn't renew certificate. Nginx won't accept HTTPS anymore | 7 | 6032 | January 14, 2020 | |
SSL certificate expired - Gitlab not accessible | 1 | 684 | May 14, 2024 |