# HTTPS is now enabled for the forum **URL:** \ **Category:** Forum\ **Tags:** https, forum\ **Created:** [1 May 2016 18:28 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124 "2016-05-01T18:28:07Z")\ **Posts on this page:** 20\ **Page:** 1
**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:** [1 May 2016 18:28 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/1 "2016-05-01T18:28:07Z")
After 8hrs of casual slightly stressful Sunday afternoon server config HTTPS is now enabled for the new forum 😃 **Please report any HTTP issues to this thread..** The pain points came from having the move HTTPS from Apache to Nginx and then reverse proxy via socket to docker instance for the Discourse forum and to Apache for PHP requests on our old sites. I wrote more about this here: > [@New forum migrated to our servers](https://community.openenergymonitor.org/t/new-forum-migrated-to-our-servers/48/8): > > Welcome to the new forums yes we’re still finding our feet but it’s taking shape will invite everyone over soon I have had to re-create all the SSL certificate for all our sites. I have gone for using a free cloud flare SSL certificate to secure the connection between our server and cloudflare. Cloudflare then presents it’s own certificate to users: [https://blog.cloudflare.com/universal-ssl-encryption-all-the-way-to-the-origin-for-free/](https://blog.cloudflare.com/universal-ssl-encryption-all-the-way-to-the-origin-for-free/) ![image](https://community.openenergymonitor.org/uploads/default/original/1X/228b027c5cd6129ca61151addc859536f2f5a88c.png) ---
**Author:** ![borpin](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/borpin/32/193_2.png) [@borpin](https://community.openenergymonitor.org/u/borpin)\ **Post date:** [1 May 2016 19:12 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/2 "2016-05-01T19:12:52Z")
I’m getting a warning in Firefox that some parts of the site are not secure such as images and if I mouse over the padlock I get a warning that ‘This website does not supply identity information.’. ---
**Author:** ![Paul](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/paul/32/28_2.png) [@Paul](https://community.openenergymonitor.org/u/Paul)\ **Post date:** [1 May 2016 19:15 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/3 "2016-05-01T19:15:28Z")
I’m thinking something’s not right too as I don’t see the green padlock - usually caused by mixed content. I’ll do a little digging! ---
**Author:** ![Jon](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/jon/32/1876_2.png) [@Jon](https://community.openenergymonitor.org/u/Jon)\ **Post date:** [1 May 2016 19:17 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/4 "2016-05-01T19:17:29Z")
no padlock for me even though I do see the https:// ---
**Author:** ![Paul](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/paul/32/28_2.png) [@Paul](https://community.openenergymonitor.org/u/Paul)\ **Post date:** [1 May 2016 19:17 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/5 "2016-05-01T19:17:45Z")
…in fact it’s the [Oem favicon](http://guide.openenergymonitor.org/images/favicon-144.png) which is being served http and not https, and which is causing the problem (mixed content). @glyn.hudson the Oem favicon needs moving to the [https://community.openenergymonitor.org](https://community.openenergymonitor.org) sub-domain, instead of linking to it from [http://guide.openenergymonitor.org/images/favicon-144.png](http://guide.openenergymonitor.org/images/favicon-144.png) Paul ---
**Author:** ![borpin](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/borpin/32/193_2.png) [@borpin](https://community.openenergymonitor.org/u/borpin)\ **Post date:** [1 May 2016 19:27 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/7 "2016-05-01T19:27:16Z")
I note that I get a similar issue when I view a topic/thread on the old forum as well. ---
**Author:** ![Paul](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/paul/32/28_2.png) [@Paul](https://community.openenergymonitor.org/u/Paul)\ **Post date:** [1 May 2016 19:56 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/8 "2016-05-01T19:56:03Z")
I’m also seeing a browser error that; [https://community.openenergymonitor.org/discourse/components/home-logo](https://community.openenergymonitor.org/discourse/components/home-logo) module is missing or not accessible. (Don’t know if it’s connected, but [number of changes were made](https://github.com/discourse/discourse/commit/1ac6dd194d811d4bb5609562dc52176ce2bdc34f) to the home-logo.js.es6 in discourse’s github repo just 2 days ago) Paul ---
**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:** [1 May 2016 20:44 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/9 "2016-05-01T20:44:24Z")
> …in fact it’s the Oem favicon which is being served http and not https, and which is causing the problem (mixed content). > @glyn.hudson the Oem favicon needs moving to the [https://community.openenergymonitor.org](https://community.openenergymonitor.org) sub-domain, instead of linking to it from [http://guide.openenergymonitor.org/images/favicon-144.png](http://guide.openenergymonitor.org/images/favicon-144.png) Thanks for debugging, should be fixed now. You may need to clear your cache. ---
**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:** [1 May 2016 20:45 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/10 "2016-05-01T20:45:46Z")
> [@Paul](#): > > I’m also seeing a browser error that;[https://community.openenergymonitor.org/discourse/components/home-logomodule](https://community.openenergymonitor.org/discourse/components/home-logomodule) is missing or not accessible. What browser are you using? I don’t see any errors in Chrome. Could you post a screen grab? ---
**Author:** ![Paul](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/paul/32/28_2.png) [@Paul](https://community.openenergymonitor.org/u/Paul)\ **Post date:** [1 May 2016 20:54 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/11 "2016-05-01T20:54:01Z")
I’m using Chrome also - in developers mode (F12) ![](https://community.openenergymonitor.org/uploads/default/original/1X/d3afa8e2ec5e6edc745d621a762e231dc7a68034.png) ---
**Author:** ![Paul](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/paul/32/28_2.png) [@Paul](https://community.openenergymonitor.org/u/Paul)\ **Post date:** [1 May 2016 20:59 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/12 "2016-05-01T20:59:41Z")
…and in Firefox ![](https://community.openenergymonitor.org/uploads/default/original/1X/2eb976a48f6a57057287496b71b139dc06ecdff1.png) ---
**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:** [1 May 2016 21:15 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/13 "2016-05-01T21:15:10Z")
Thanks for the info. The header logo error should now be fixed. Thanks to the info on [this thread](https://meta.discourse.org/t/redirect-for-non-logged-in-users/33500/17) it was due to a recent upgrade to Discourse header which required a change in the way we do the redirect to /latest on the top logo is clicked ---
**Author:** ![Paul](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/paul/32/28_2.png) [@Paul](https://community.openenergymonitor.org/u/Paul)\ **Post date:** [1 May 2016 21:19 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/14 "2016-05-01T21:19:14Z")
All looks good now! Paul ---
**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:** [1 May 2016 21:56 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/15 "2016-05-01T21:56:17Z")
Also just managed to fix the mixed content issue on [OpenEnergyMonitor.org](https://OpenEnergyMonitor.org) by adding ` `to the Drupal header. This automatically tells the browser to upgrade http content e.g .images requests to https before serving. [Thanks Google developers](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content?hl=en) ---
**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:** [1 May 2016 22:51 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/16 "2016-05-01T22:51:53Z")
> [@borpin](#): > > I note that I get a similar issue when I view a topic/thread on the old forum as well. mixed content on the old forum show now also be fixed, see my post above. Please confirm. _You may need to clear browser cache_. ---
**Author:** ![Bill.Thomson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/bill.thomson/32/1834_2.png) [@Bill.Thomson](https://community.openenergymonitor.org/u/Bill.Thomson)\ **Post date:** [3 May 2016 15:01 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/17 "2016-05-03T15:01:54Z")
Glyn, Opera v36.0.2130.65 gives me this error: ![](https://community.openenergymonitor.org/uploads/default/original/1X/5352e574f8c2a6d96d7e04efef5e31f6ac4cf171.png) and Chrome v49.0.2623.112 m gives this one: ![](https://community.openenergymonitor.org/uploads/default/original/1X/f3b9c594cd756b1f85debdec08814ce07d43f9b2.png) ---
**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 May 2016 17:05 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/18 "2016-05-03T17:05:47Z")
Interesting… Universal SSL should work fine with Opera 8 and above, from the [Cloud Flare page on Universal SSL](https://support.cloudflare.com/hc/en-us/articles/203041594-What-browsers-work-with-CloudFlare-s-SSL-certificates-) > Universal SSL uses Server Name Indication (SNI) certificates using Elliptic Curve Digital Signature Algorithm (ECDSA). SNI and ECDSA certificates work with the following modern browsers: > Desktop Browsers installed on Windows Vista or OS X 10.6 or later: > Internet Explorer 7 > Firefox 2 > Opera 8 (with TLS 1.1 enabled) > Google Chrome v5.0.342.0 > Safari 2.1 Update: just installed Opera and the forum works fine for me on Opera 36. ![](https://community.openenergymonitor.org/uploads/default/original/1X/9933427e37590f203a7e30fc31f0315ef4313a8c.png) Do you have any issues with any other SSL sites? Could you post the output of some SSL testers: [https://www.howsmyssl.com/](https://www.howsmyssl.com/) [https://www.ssllabs.com/ssltest/viewMyClient.html](https://www.ssllabs.com/ssltest/viewMyClient.html) ---
**Author:** ![Paul](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/paul/32/28_2.png) [@Paul](https://community.openenergymonitor.org/u/Paul)\ **Post date:** [3 May 2016 18:23 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/19 "2016-05-03T18:23:08Z")
@Bill.Thomson - can you access my ‘poor excuse for a site’ - [https://www.digitalnut.co.uk/](https://www.digitalnut.co.uk/) I’m also using Cloudflare, similar as Oem (not full -strict though). Paul ---
**Author:** ![Bill.Thomson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/bill.thomson/32/1834_2.png) [@Bill.Thomson](https://community.openenergymonitor.org/u/Bill.Thomson)\ **Post date:** [4 May 2016 01:48 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/20 "2016-05-04T01:48:06Z")
> [@Paul](#): > > can you access my ‘poor excuse for a site’ - [https://www.digitalnut.co.uk/](https://www.digitalnut.co.uk/) Thanks for the cross-check, Paul I get the same results with your site as I do with the new OEM site, i.e no joy with Opera or Chrome. Firefox works OK. This check was performed with my home desktop machine. The earlier test was with a laptop at my office. I’m going to try with another laptop/OS combo. Update… Looks like the issue is Win XP. Opera and Chrome work OK with Win 7, Win 10 and Linux. I know, I know, should have ditched XP, but I don’t like the W7 UI, and like the W10 UI even less. At least the solution is easy (for me, anyway) - switch to Slackware, Debian, etc. etc. Paul, thanks again for the help! ---
**Author:** ![bidouilleur](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/bidouilleur/32/12_2.png) [@bidouilleur](https://community.openenergymonitor.org/u/bidouilleur)\ **Post date:** [5 May 2016 19:06 UTC](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124/21 "2016-05-05T19:06:39Z")
with all changes from last hours the ssl link doesn’t seem to be clean anymore ![](https://community.openenergymonitor.org/uploads/default/original/1X/7feb1b770a121f5f3ed3bd53f1c35cbf0502bd70.png) [Next page](https://community.openenergymonitor.org/t/https-is-now-enabled-for-the-forum/124.md?page=2)