# Website is down because ssl is expired

**URL:** <https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104>\
**Category:** Help\
**Created:** [May 18, 2020, 3:30pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104 "2020-05-18T15:30:23Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![sickom0de](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sickom0de](https://community.letsencrypt.org/u/sickom0de)\
**Post date:** [May 18, 2020, 3:30pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/1 "2020-05-18T15:30:23Z")

</div>

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. [https://crt.sh/?q=example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: spnone.no

I ran this command: certbot renew

It produced this output: ssl didn’t get renewed

My web server is (include version): nginx 1.18.0

The operating system my web server runs on is (include version): centos 7

My hosting provider, if applicable, is: [ovh.com](http://ovh.com)

I can login to a root shell on my machine (yes or no, or I don’t know): yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no.

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you’re using Certbot): 1.3.0

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [May 18, 2020, 3:33pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/2 "2020-05-18T15:33:59Z")

</div>

Four new certificates were issued today; two of them include the `www` subdomain and two do not.

[https://crt.sh/?q=spnone.no](https://crt.sh/?q=spnone.no)

[https://spnone.no/](https://spnone.no/) and [https://www.spnone.no/](https://www.spnone.no/) are both using one of the new certificates without `www` – so the former works, and visiting the latter results in a certificate mismatch error.

What does “`sudo certbot certificates`” output?

---

<div class="post-metadata">

**Author:** ![sickom0de](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sickom0de](https://community.letsencrypt.org/u/sickom0de)\
**Post date:** [May 18, 2020, 4:10pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/3 "2020-05-18T16:10:51Z")

</div>

> [@mnordhoff](#):
>
> sudo certbot certificates

Found the following certs:  
Certificate Name: demo1.norwaysites.no  
Domains: demo1.norwaysites.no  
Expiry Date: 2020-08-16 12:34:09+00:00 (VALID: 89 days)  
Certificate Path: /etc/letsencrypt/live/demo1.norwaysites.no/fullchain.pem  
Private Key Path: /etc/letsencrypt/live/demo1.norwaysites.no/privkey.pem  
Certificate Name: norwaysites.no  
Domains: norwaysites.no spnone.no www.norwaysites.no www.spnone.no  
Expiry Date: 2020-08-16 12:31:56+00:00 (VALID: 89 days)  
Certificate Path: /etc/letsencrypt/live/norwaysites.no/fullchain.pem  
Private Key Path: /etc/letsencrypt/live/norwaysites.no/privkey.pem  
Certificate Name: [rumblepvp.com](http://rumblepvp.com)  
Domains: [rumblepvp.com](http://rumblepvp.com) [www.rumblepvp.com](http://www.rumblepvp.com)  
Expiry Date: 2020-08-16 11:28:27+00:00 (VALID: 89 days)  
Certificate Path: /etc/letsencrypt/live/rumblepvp.com/fullchain.pem  
Private Key Path: /etc/letsencrypt/live/rumblepvp.com/privkey.pem  
Certificate Name: [sickopvp.com](http://sickopvp.com)  
Domains: [sickopvp.com](http://sickopvp.com) [www.sickopvp.com](http://www.sickopvp.com)  
Expiry Date: 2020-08-16 11:28:40+00:00 (VALID: 89 days)  
Certificate Path: /etc/letsencrypt/live/sickopvp.com/fullchain.pem  
Private Key Path: /etc/letsencrypt/live/sickopvp.com/privkey.pem  
Certificate Name: spnone.no-0001  
Domains: spnone.no  
Expiry Date: 2020-08-16 12:34:50+00:00 (VALID: 89 days)  
Certificate Path: /etc/letsencrypt/live/spnone.no-0001/fullchain.pem  
Private Key Path: /etc/letsencrypt/live/spnone.no-0001/privkey.pem  
Certificate Name: spnone.no  
Domains: spnone.no www.spnone.no  
Expiry Date: 2020-08-16 11:28:49+00:00 (VALID: 89 days)  
Certificate Path: /etc/letsencrypt/live/spnone.no/fullchain.pem  
Private Key Path: /etc/letsencrypt/live/spnone.no/privkey.pem

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [May 18, 2020, 4:49pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/4 "2020-05-18T16:49:50Z")

</div>

I would delete this cert:

> [@sickom0de](#):
>
> Certificate Name: spnone.no-0001  
> **Domains: spnone.no**  
> Expiry Date: 2020-08-16 12:34:50+00:00 (VALID: 89 days)  
> Certificate Path: /etc/letsencrypt/live/spnone.no-0001/fullchain.pem  
> Private Key Path: /etc/letsencrypt/live/spnone.no-0001/privkey.pem

And use this one instead:

> [@sickom0de](#):
>
> Certificate Name: spnone.no  
> **Domains: spnone.no www.spnone.no**  
> Expiry Date: 2020-08-16 11:28:49+00:00 (VALID: 89 days)  
> Certificate Path: /etc/letsencrypt/live/spnone.no/fullchain.pem  
> Private Key Path: /etc/letsencrypt/live/spnone.no/privkey.pem

You can do that with:  
`certbot delete --cert-name spnone.no-0001`  
First be sure you aren't using that cert anywhere.  
Which it seems you are:

> **[SSL Server Test (Powered by Qualys SSL Labs)](https://www.ssllabs.com/ssltest/analyze.html?d=spnone.no)**
>
> A comprehensive free SSL test for your public web servers.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [May 18, 2020, 5:01pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/5 "2020-05-18T17:01:22Z")

</div>

The website is down because:

# Error establishing a database connection

```auto
wget https://spnone.no/
--2020-05-18 17:01:55-- https://spnone.no/
Resolving spnone.no (spnone.no)... 54.38.78.56
Connecting to spnone.no (spnone.no)|54.38.78.56|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2020-05-18 17:01:56 ERROR 500: Internal Server Error.

```

---

<div class="post-metadata">

**Author:** ![sickom0de](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sickom0de](https://community.letsencrypt.org/u/sickom0de)\
**Post date:** [May 18, 2020, 6:36pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/6 "2020-05-18T18:36:07Z")

</div>

The sites are still down.

I did `certbot renew`

And got the following:  
The following certs are not due for renewal yet:  
/etc/letsencrypt/live/demo1.norwaysites.no/fullchain.pem expires on 2020-08-16 (skipped)  
/etc/letsencrypt/live/norwaysites.no/fullchain.pem expires on 2020-08-16 (skipped)  
/etc/letsencrypt/live/rumblepvp.com/fullchain.pem expires on 2020-08-16 (skipped)  
/etc/letsencrypt/live/sickopvp.com/fullchain.pem expires on 2020-08-16 (skipped)  
/etc/letsencrypt/live/spnone.no/fullchain.pem expires on 2020-08-16 (skipped)  
No renewals were attempted.

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [May 18, 2020, 6:45pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/7 "2020-05-18T18:45:19Z")

</div>

Which sites are down? Do any of them have problems with their certificates, or do they have problems with other things?

---

<div class="post-metadata">

**Author:** ![sickom0de](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sickom0de](https://community.letsencrypt.org/u/sickom0de)\
**Post date:** [May 18, 2020, 6:49pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/8 "2020-05-18T18:49:47Z")

</div>

Spnone.no and Norwaysites.no.

I assume these two websites went offline because the SSL expired today. The sites were running fine yesterday for example. I have problems renewing the certificates.

I get the following when I do `certbot renew`:

> /etc/letsencrypt/live/spnone.no/fullchain.pem expires on 2020-08-16 (skipped)  
> No renewals were attempted.

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [May 18, 2020, 6:55pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/9 "2020-05-18T18:55:02Z")

</div>

Hi @sickom0de

that domain

> [@sickom0de](#):
>
> Norwaysites.no

isn't down - [https://check-your-website.server-daten.de/?q=norwaysites.no](https://check-your-website.server-daten.de/?q=norwaysites.no)

There is a new Letsencrypt certificate

```nohighlight
CN=norwaysites.no
	18.05.2020
	16.08.2020
expires in 90 days	norwaysites.no, spnone.no, 
www.norwaysites.no, www.spnone.no - 4 entries

```

and both connections (www and non-www) use that certificate.

There is a problem - http status 500 - Server Error:

> Error establishing a database connection

So your site doesn't work.

But that's not a certificate problem.

PS:

> I have problems renewing the certificates.

You have renewed and installed the certificate. Fix your database problem.

---

<div class="post-metadata">

**Author:** ![sickom0de](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sickom0de](https://community.letsencrypt.org/u/sickom0de)\
**Post date:** [May 18, 2020, 7:12pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/10 "2020-05-18T19:12:12Z")

</div>

`But that’s not a certificate problem.`  
Any idea how I fix this? I have tried restarting the MySql database, etc.  
The error message says:

> Error establishing a database connection

---

<div class="post-metadata">

**Author:** ![sickom0de](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sickom0de](https://community.letsencrypt.org/u/sickom0de)\
**Post date:** [May 18, 2020, 7:27pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/11 "2020-05-18T19:27:23Z")

</div>

I restarted the VPS. Now the site went offline. I did the command

> systemctl restart nginx

and got the following  
● nginx.service - nginx - high performance web server  
Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; vendor preset: disabled)  
Active: failed (Result: exit-code) since Mon 2020-05-18 21:25:03 CEST; 10s ago  
Docs: [nginx documentation](http://nginx.org/en/docs/)  
Process: 10803 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=1/FAILURE)

May 18 21:25:03 [vps785737.ovh.net](http://vps785737.ovh.net) systemd[1]: Starting nginx - high performa....  
May 18 21:25:03 [vps785737.ovh.net](http://vps785737.ovh.net) nginx[10803]: nginx: [emerg] cannot load ce...  
May 18 21:25:03 [vps785737.ovh.net](http://vps785737.ovh.net) systemd[1]: nginx.service: control process...1  
May 18 21:25:03 [vps785737.ovh.net](http://vps785737.ovh.net) systemd[1]: Failed to start nginx - high p....  
May 18 21:25:03 [vps785737.ovh.net](http://vps785737.ovh.net) systemd[1]: Unit nginx.service entered fai....  
May 18 21:25:03 [vps785737.ovh.net](http://vps785737.ovh.net) systemd[1]: nginx.service failed.  
Hint: Some lines were ellipsized, use -l to show in full.

---

<div class="post-metadata">

**Author:** ![sickom0de](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sickom0de](https://community.letsencrypt.org/u/sickom0de)\
**Post date:** [May 18, 2020, 7:56pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/12 "2020-05-18T19:56:17Z")

</div>

nginx -t gives me:

[root@vps785737 ~]# nginx -t

nginx: [emerg] cannot load certificate “/etc/letsencrypt/live/spnone.no-0001/fullchain.pem”: BIO\_new\_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen(’/etc/letsencrypt/live/spnone.no-0001/fullchain.pem’,‘r’) error:2006D080:BIO routines:BIO\_new\_file:no such file)

nginx: configuration file /etc/nginx/nginx.conf test failed

---

<div class="post-metadata">

**Author:** ![sickom0de](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sickom0de](https://community.letsencrypt.org/u/sickom0de)\
**Post date:** [May 18, 2020, 11:07pm UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/13 "2020-05-18T23:07:03Z")

</div>

Update: I managed to fix the problem.

I followed this guide: [https://certbot.eff.org/lets-encrypt/centosrhel7-nginx](https://certbot.eff.org/lets-encrypt/centosrhel7-nginx)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [June 18, 2020, 12:32am UTC](https://community.letsencrypt.org/t/website-is-down-because-ssl-is-expired/123104/15 "2020-06-18T00:32:28Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.