From b5cd87e3b4eb2fc6ea8f3230f1c7eb50254100af Mon Sep 17 00:00:00 2001
From: Malcolm <56974882+malcolmcdixon@users.noreply.github.com>
Date: Tue, 5 May 2020 08:47:09 +0000
Subject: [PATCH] Update tls_self_signed_certificate.markdown (#13179)

---
 .../certificates/tls_self_signed_certificate.markdown     | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown b/source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown
index 7926fedadcb..90d4701308b 100644
--- a/source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown
+++ b/source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown
@@ -50,6 +50,14 @@ http:
   ssl_key: /home/your_user/.homeassistant/privkey.pem
 ```
 
+Docker:
+
+```yaml
+http:
+  ssl_certificate: /config/fullchain.pem
+  ssl_key: /config/privkey.pem
+```
+
 A restart of Home Assistant is required for the new certificate to take effect.
 
 If you get any log error about *ssl_key* or *ssl_certificate* that is **not a file for dictionary value** when run Home Assistant, you need to change owner or access permission of the `.pem` files as following: