Hi, yes, the browser does not recognize the certificate, and does the same in inprivate, or with cache turned off…
To clarify, I replace the .crt file - it is a purchased wildcard certificate, this is found in /etc/gitlab/ssl (Location confirmed by checking the config file)
I thought a restart would be required - But if i restart the server, or Github, it never comes back (Just spinning). The solution at that point is restoring to a snapshot.
My suggestion is to restore to the snapshot - as you said that is the work i.e. SSHable state. Find the exsting cert(s) (/etc/gitlab/ssl), download them and store them. Then I would delete the cert from the server - although you may not need to, but I would just to keep things tidy, after that use Certbot (https://certbot.eff.org/) to get a new one. The docs are very good and GL (10.5) supports it out of the box, https://about.gitlab.com/2018/02/22/gitlab-10-5-released/
I have found the issue - I can’t work with Wildcard certificates, or lets-encrypt… IT’s more limitations with networking\firewall in our place that stops the latter.
But if we buy a certificate, i can get through… this is done now, and Github is now working on for us…
One day. i might crack how to use a wildcard certificate, for now, getting up and running is more crucial
Yep Gitlab Running CE 10.6.4 - I’m aware there is a new version, i may look at updating sometime, but i’m looking for change logs\information first, before i plan an update…
It’s Just our server is named github that’s all - that’s why i referred to it as github… I’ll ammend going forward.
Very much a POC at the moment that is used by limited users, just something we have no experience prior. Made it a fair challenge, as we have little linux knowledge here too (That’ll be me now lol…)