# Securing Emoncms with an SSL certificate **URL:** \ **Category:** Emoncms\ **Tags:** ssl, emoncms\ **Created:** [3 June 2016 11:56 UTC](https://community.openenergymonitor.org/t/securing-emoncms-with-an-ssl-certificate/634 "2016-06-03T11:56:27Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![mhamer](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/m/3da27b/32.png) [@mhamer](https://community.openenergymonitor.org/u/mhamer)\ **Post date:** [3 June 2016 11:56 UTC](https://community.openenergymonitor.org/t/securing-emoncms-with-an-ssl-certificate/634/1 "2016-06-03T11:56:27Z")
An information update to an earlier posting in the old forum on securing Emoncms using SSL certificates when using the latest Jessie Lite SD card image. ---
**Author:** ![mhamer](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/m/3da27b/32.png) [@mhamer](https://community.openenergymonitor.org/u/mhamer)\ **Post date:** [3 June 2016 12:39 UTC](https://community.openenergymonitor.org/t/securing-emoncms-with-an-ssl-certificate/634/2 "2016-06-03T12:39:44Z")
When attempting to secure Emoncms version 9.7 on the latest Jessie Lite SD card release using the method previously employed for the old Wheezy image, I encountered a problem related to the upgrade of Apache from v2.2 to 2.4. The background to the method can be found in an [article](https://hoast.dk/wordpress/2015/09/22/enabling-ssl-for-emoncms/) which references a [posting](https://openenergymonitor.org/emon/node/5997) by Paul Reed in the old OpenEnergyMonitor forum. In Paul’s posting he describes how to make changes to the file: **/etc/apache2/sites-available/default-ssl** to point to the 3 certificates required as well as some changes to the _Directory / and /var/www/_ lines. In the latest SD image the file **default-ssl** no longer exists being replaced with **default-ssl.conf** which no longer contains references to the _Directory_ structure. As a first attempt, I copied the old **default-ssl** file to the new area and completed Paul’s instructions. On the face of it, accessing Emoncms using _https://_ appeared to work. I could login the site and view my inputs. However, the _Feeds_ page hung displaying the word _loading…_ and no visualisations were visible. After some searching I found that [someone else](http://serverfault.com/questions/693437/after-upgrade-wheezy-to-jessie-apache-2-ssl-stops-working) had experienced an unrelated but similar issue when upgrading from Wheezy to Jessie. In essence, the new version of Apache appears to mandate the **.conf** file ending. Making the certificate changes but ignoring the Directory line changes, which are not present, to this file enabled SSL access to Emoncms as before. 😌 I do not understand Apache well enough to offer any explanations but feel it useful to alert others to the fact that there are issues that require attention when upgrading to SSL on the new image. Perhaps, others more knowledgable than me could comment on the problem ---
**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\ **Post date:** [3 June 2016 23:37 UTC](https://community.openenergymonitor.org/t/securing-emoncms-with-an-ssl-certificate/634/3 "2016-06-03T23:37:53Z")
We used [Lets Encrypt](https://letsencrypt.org/) to secure [emoncms.org](http://emoncms.org), was a very easy process. Apparently Let’s Encrypt will also work on RaspberryPi