Skip to content
Snippets Groups Projects
Commit 9b48a1c7 authored by Jeroen Nijhof's avatar Jeroen Nijhof
Browse files

Add ssl expiring documentation

parent 11781e35
No related branches found
No related tags found
1 merge request!88Add ssl expiring documentation
Loading
Loading
@@ -33,6 +33,7 @@ The aim of this project is to have a quick guide of what to do when an emergency
* [Runners registry is down](troubleshooting/runners_registry_is_down.md)
* [Runners cache free disk space is less than 20%](troubleshooting/runners_cache_disk_space.md)
* [Kibana is down](troubleshooting/kibana_is_down.md)
* [SSL certificate expires](troubleshooting/ssl_cert.md)
 
## Alerting and monitoring
 
Loading
Loading
# SSL Certificate expiring or expired
## First and foremost
*Don't Panic*
## Symptoms
You see alerts like
```
@channel about.gitlab.com HTTP SSL Certificate WARNING - Certificate 'about.gitlab.com' will expire on Thu Nov 30 23:59:00 2016
```
## Possible checks
Check with browser if this is really the case.
## Resolution
We use sslmate for ordering SSL certificates, get the commandline tool via https://sslmate.com/help/install.
Credentials are in 1password.
### Buy a new certificate
```
sslmate buy about.gitlab.com
```
### Use rake to update vault
Since we store the certificate or at least the key always in a vault, update it with the new certificate and key.
```
cd chef-repo/
rake edit_role_secrets[the_role_with_vault]
```
## NOTES
* For dev.gitlab.org we use the same certificate for registry so make sure you update the normal and registry certificates with the same one.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment