Cumulus MX not updating in Chrome

[Atlas]

I can't see any Cumulus MX realtime data update in google chrome. In IE and Firefox runs well but in chrome doesn't.

A few seconds after I open chrome to 127.0.0.1:8998 an alert window says "Connection is closed..." and in chrome's console is displayed:
WebSocket connection to 'ws://127.0.0.1:8002/' failed: Error during WebSocket handshake: net::ERR_CONNECTION_RESET

Anyone else had this problem?

Thanks

[steve]

A few people do seem to have a problem where one particular browser doesn't work, sometimes Chrome, sometimes another one. See this thread for a suggestion (found by searching for "Chrome" in the MX section of the forum): https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=14350

[Atlas]

Sorry I didn't see anything on google's search...

After deleting cookies Cumulus MX works in Chrome

These days I wasn't be able to run MX from the outside of my LAN though in my inner LAN it was working. I had opened only 8998 port in my router and data didn't update so after this issue I've opened 8002 port for the web sockets and it's already working fine from the web.

Any posibilities to create user and password to prevent altering configuration files from the web? Although it's only seen through a specific port it could be interesting set user and password to alter settings for more security.

Best regards

[duke]

Any posibilities to create user and password to prevent altering configuration files from the web? Although it's only seen through a specific port it could be interesting set user and password to alter settings for more security.

This has been discussed in several threads here with several possible solutions.

[Atlas]

Ok

I'll look for it

Thanks

[Wychall]

I have noticed that the MX data screen is not updating on Chrome Beta on android whilst Chrome is working fine on the same device. So check your browser before casting aspersions towards MX.