Cumulus Support

Is it just me, or has the C-MX dashboard stopped working (no resonse from the websocket) in Chrome 42.0.2311.135?

On the same laptop it is still working fine with IE 11.

FWIW...
Mine is working fine with this version of Chrome, IE11, and FF37.0.2....

Working for me too - any errors in the developer console anywhere?

steve wrote:Working for me too - any errors in the developer console anywhere?

Nope, just no response, then eventually a timeout. It used to work fine.

Hmm, and Chrome 42 works fine on my phone

Hi Mark
using SRWareIron - based on Google Chrome - Version Version 42.0.2250.1 - Dashborad is working.
Maybe aplugin update which is identifiying CumulusMX as a Ad Server

Hmm, started Chrome with extensions disabled - same.

Tried https://www.websocket.org/echo.html
Doesn't connect, but enable the TLS option and it does connect.

More investigation required...

Mines working on Version 42.0.2311.135 (64-bit) Linux Elementary.

Mark, i don't know whether your still using XP as described in your profile, but maybe google is just offering restricted support for Chrome on XP.

Hi, no this is a Win7 laptop, a work one though so it may be a new lock down that needs working around. Strange that IE still works but I guess that could be a named executable in a permit rule. The security software and firewall are not logging anything as blocked, still looking....

Perhaps it's something to do with the way that MX uses a separate port for http and ws? Apparently ws normally shares port 80 with http, but I'm not sure how that's supposed to work, perhaps it needs a more sophisticated web server than the one in MX.

Fixed! One of those doh! moments, I just cleared the cached data and cookies for the IP address of the Pi. I remembered that doing this had cured odd problems like this before in Chrome - it just took me a while to recall it.