Cumulus Support

Hi all,

I've been testing Cumulus MX on a PI for about 2 years now. Never had the need to access the web interface from outside my internal network. Yesterday I decided to have a test and do a port forwarding (TCP & UDP) to see if I can access from the outer world. The result is that I can access the web interface but no displayed data. Just a popup message "Conection is Closed". I'm using the last 3.9.4 (build 3099) in a Raspbian Stretch. I'm also running an Nginx server that is not giving me any problems to access outside.

I can access configuration, recent charts and so on, only happens in the Dashboard and Now Menus. I was wondering if I'm missing some port forwarding or configuration here, any ideas are welcome.

And finally, thanks to all the comunity and developers for a fantastic piece of software!

roger

I wouldn't open your MX interface to the Internet as anybody can access it and potentially read/adjust your configuration settings.

That aside, some MX interface webpages use websockets to access data. Perhaps that is the problem?

Freddie is correct, you will need to allow web sockets through your firewall as well. But I'd also reinforce - this is a really bad idea.

If you need to see it remotely then set up a VPN, or worse allow a desktop sharing app through. Limit them to known IP addresses, or IP ranges as well if you can.

freddie wrote: ↑Mon 04 Jan 2021 4:46 pm I wouldn't open your MX interface to the Internet as anybody can access it and potentially read/adjust your configuration settings.

That aside, some MX interface webpages use websockets to access data. Perhaps that is the problem?

You're totally correct , luckily in this case I was using a src filter as I'm using static IP address in the office, but it's definitely a bad idea to do it without proper firewall filtering.

The websocket must be my problem here, time to configure once and for all my VPN.

Thank you freddie!

roger

From memory, the Dashboard, Now, and Gauges pages use a web socket connection.

mcrossley wrote: ↑Mon 04 Jan 2021 5:47 pm Freddie is correct, you will need to allow web sockets through your firewall as well. But I'd also reinforce - this is a really bad idea.

If you need to see it remotely then set up a VPN, or worse allow a desktop sharing app through. Limit them to known IP addresses, or IP ranges as well if you can.

Sorry, yes, I was writing my post before seeing yours. I already have my OpenVPN up and running

Thank you!