# Patching Heartbleed
**URL:** https://meta.discourse.org/t/patching-heartbleed/14711
**Category:** Self-hosting
**Tags:** hosting
**Created:** [April 12, 2014, 2:50am UTC](https://meta.discourse.org/t/patching-heartbleed/14711 "2014-04-12T02:50:08Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@PabloC](https://meta.discourse.org/u/PabloC)
#### Post date: [April 12, 2014, 2:50am UTC](https://meta.discourse.org/t/patching-heartbleed/14711/1 "2014-04-12T02:50:08Z")
Hi gents, one question.
What’s the best way to patch Heartbleed bug on a Ubuntu Server 13.10 installation without Docker?
Any recommended approach?
Tks!
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [April 12, 2014, 2:57am UTC](https://meta.discourse.org/t/patching-heartbleed/14711/2 "2014-04-12T02:57:10Z")
Just install the new openssl packages from the repositories and restart all services using it.
(If you don’t care about your precious uptime, restarting the whole server works too.)
---
### Author:  [@haiku](https://meta.discourse.org/u/haiku)
#### Post date: [April 12, 2014, 3:29pm UTC](https://meta.discourse.org/t/patching-heartbleed/14711/3 "2014-04-12T15:29:01Z")
And according to [Netcraft](http://news.netcraft.com/archives/2014/04/11/heartbleed-certificate-revocation-tsunami-yet-to-arrive.html) you need to reissue your SSL certs as well.
---
### Author:  [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [April 13, 2014, 8:09pm UTC](https://meta.discourse.org/t/patching-heartbleed/14711/4 "2014-04-13T20:09:24Z")
Let’s be clear here - reissuing your SSL certs against existing keys won’t help. You need to generate new private keys (and thus new certificates based on those).
---
### Author:  [@mlapida](https://meta.discourse.org/u/mlapida)
#### Post date: [April 16, 2014, 11:39am UTC](https://meta.discourse.org/t/patching-heartbleed/14711/5 "2014-04-16T11:39:19Z")
I’ve updated the entire server, docker and discourse. Destroyed and bootstrapped the container and rebooted the entire server. My site is still showing up as vulnerable. What am I missing here?
---
### Author:  [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [April 16, 2014, 6:07pm UTC](https://meta.discourse.org/t/patching-heartbleed/14711/6 "2014-04-16T18:07:09Z")
Have you pulled the latest discourse-docker?
The updated image (0.2.0) is necessary and the templates have changed to reflect that.
`docker images --tree` should show the ancestry similar to:
```
…
│ └─7fbcf08c75da Virtual Size: 804.8 MB
│ └─610a44f81f75 Virtual Size: 1.124 GB Tags: samsaffron/discourse:0.2.0
│ ├─656cc0013dad Virtual Size: 1.916 GB Tags: discourse/test:latest
```
---
### Author:  [@mlapida](https://meta.discourse.org/u/mlapida)
#### Post date: [April 18, 2014, 4:32am UTC](https://meta.discourse.org/t/patching-heartbleed/14711/7 "2014-04-18T04:32:19Z")
I ended up running the docker build from your post below and rebuilding. I did this after pulling the latest discourse-docker build.
[https://meta.discourse.org/t/patching-the-heartbleed-vuln-in-a-docker-image/14574/10?u=mlapida](https://meta.discourse.org/t/patching-the-heartbleed-vuln-in-a-docker-image/14574/10)
Thanks!