Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Cloudflare Tunnel - Remote Access to CumulusMX
Moderator: mcrossley
-
sparkynerd
- Posts: 39
- Joined: Wed 14 Jan 2015 10:08 pm
- Weather Station: Davis Vantage Vue
- Operating System: Windows, Linux, Proxmox
- Location: United States
Cloudflare Tunnel - Remote Access to CumulusMX
I have a Cloudflare tunnel setup to access CumulusMX remotely. The webpage loads, but the gauges don't show any information. I can successfully get into the other tabs, such as MX settings. I have similar Cloudflare tunnels setup for other services, and they work fine. The browser opens the CumulusMX page as https, not sure if that could be the issue? Any ideas?
__________
Davis Vantage Vue
Proxmox / Ubuntu LXC
Cumulus MX v4
Davis Vantage Vue
Proxmox / Ubuntu LXC
Cumulus MX v4
-
mcrossley
- Posts: 14384
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Cloudflare Tunnel - Remote Access to CumulusMX
The gauges use a web sockets connection for the data by default - unsecured as the containing web page.
If you have managed to get remote access working over https, then will secure web sockets work as well - edit gaugefeed.js and change line 14 from 'ws://' to 'wss'://'
Alternatively, switch the page to use polling rather than web sockets, gaugefeed.js line 4 "var useWebSockets = false;"
If you have managed to get remote access working over https, then will secure web sockets work as well - edit gaugefeed.js and change line 14 from 'ws://' to 'wss'://'
Alternatively, switch the page to use polling rather than web sockets, gaugefeed.js line 4 "var useWebSockets = false;"