From 0f9451d8e1b9810b13657a6bdd14820be6e09ef3 Mon Sep 17 00:00:00 2001 From: JammyDodger231 Date: Fri, 27 Jan 2017 17:45:04 +0000 Subject: [PATCH] Update mqtt.markdown (#1884) After having my own MQTT server running on a VPS that is hosted elsewhere from my home assistant server I found that after using lets encrypt it would not allow me to use the .pem files created with home assistant. They worked natively with mosquitto_sub and owntracks but this is the only method I found to work. The change should help anyone else who can't get a secure connection and save hours of searching --- source/_components/mqtt.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_components/mqtt.markdown b/source/_components/mqtt.markdown index 5f39d180cc5..e829e5da5fb 100644 --- a/source/_components/mqtt.markdown +++ b/source/_components/mqtt.markdown @@ -119,6 +119,10 @@ mqtt: There is an issue with the Mosquitto package included in Ubuntu 14.04 LTS. Specify `protocol: 3.1` in your MQTT configuration to work around this issue.

+

+If you are running a mosquitto instance on a different server with proper SSL encryption using a service like letsencrypt you may have to set the certificate to the operating systems own `.crt` certificates file. In the instance of ubuntu this would be `certificate: /etc/ssl/certs/ca-certificates.crt` +

+ ### {% linkable_title Public broker %} The Mosquitto project runs a [public broker](http://test.mosquitto.org). This is the easiest to set up, but there is no privacy as all messages are public. Use this only for testing purposes and not for real tracking of your devices.