Have same problem across multiple Emonpis on different networks. Worked OK on Thursday as I set up a unit. Didn’t work yesterday when I tried the same thing with another one. Then found a common problem across all Dataplicity linked devices.
I noticed that it’s the browser blocking the css and js files as it says these are not being encrypted properly as per https requirements. It is possible to temporarily bypass but probably not recommended.
We were relying on the $_SERVER parameter ‘HTTP_X_FORWARDED_PROTO’ or apache_request_headers equivalent to state ‘https’. For some reason this has changed and it’s coming through as ‘http’.
Parameter ‘HTTP_X_FORWARDED_PORT’ however is coming through as the correct port for https (443) and so I’ve added a check for this as well. If it detects either HTTP_X_FORWARDED_PROTO == https or HTTP_X_FORWARDED_PORT == 443, emoncms will now return paths with https at the start.
Our apologies for inconvenience you’re experienced caused by that issue, we already found it and have deployed a fix.
As pointed out by @TrystanLea, the issue arose from a recent infrastructure upgrade, which resulted in the export of HTTP_X_FORWARDED_PROTO http instead of https. Big thanks for your help. We appreciate it much.
Also thanks for everyone who pointed out the issue and reported it to us. It helped to solve the problem fast. Please not hesitate to contact us in future through chat on our main page in case of any problems or questions.