Energy dashboard not working any more with 2026-3 and reverse proxy

[Michel13]

Hello,

I have recently setup the energy dashboard on version 2026-2 and it works just fine.
Yesterday, I have updated to 2026-3 and since then the energy dashboard is dead : no power consumption, no current flow, nothing. All values are at 0. Checked all the setting, no change from the previous version. The power values are ok on the devices, not on the dashboard.

Any idea why dashboard information is not available ?

Platform : RPI4. I have update and upgrade the apt of the unit

Update : the problem appears when I access domoticz through reverse proxy. If I use direct IP:8080 the dashboard is working.

I have this message in the log : Status: [web:8080] Rejected WebSocket upgrade: Origin 'https://<my url>' is not allowed for a trusted-network session

Power information is a result of calculation from data collected by mqtt. Solar energy is also issued from mqtt. Question is, how reverse proxy may affect the energy dashboard ? Web sockets are activated on the reverse proxy. I do not really understand how reverse proxy is interfering with the dashboard since data is issued from domoticz devices. Is there something to do more to get dashboard working correctly with the reverse proxy ?

Update 2 : title modified

[waltervl]

If you check the recent topics on this forum you will see some related to proxy issues with stable 2026.3
Some issues are already adressed in latest beta so perhaps update to it.

[Michel13]

Thank you waltervl.

After deeper check with the web development tool, it is almost confirmed that the problem is linked with the websocket in the libwebem config.

As the only part affected so far by the 2026.3 is the energy dashboard and unless other issues appear later, I will wait for the next stable release.

[Doler]

I'm having the same problem. Apart from the 'static display' of the Energy Dashboard page I also the custom pages don't display data. In the Domoticz log I get

Code: Select all

Status: [web:8080] Rejected WebSocket upgrade: Origin 'https://domoticz.xxxx.duckdns.org' is not allowed for a trusted-network session

.
I searched for a solution using AI but that didn't work out (we both are not smart enough). Can somone help me?

I use the latest beta, security settings Allow Basic Auth = On, the recommended Trusted Networks, no CORS Origins. Using IP-Addressing all works normal, the problem occurs when using SSL offloading using https://domoticz.xxxx.duckdns.org.

[Doler]

Solved it (trial and error). Changed scheme in Nginx fro http (8080) into https (443) and everything is ok.