v3032 and MS Edge

[philpugh]

Installed CMX 3032 a couple of days ago and everything working fine. However I had need to visit the :8998 interface to check a setting and the 'wonderful' MS Edge browser pops up an alert saying I will need to install another viewer for this type of file! IE 11 and assorted other browsers seem to work OK. It was OK prior to the change to 3032 but of course MS keep updating stuff on W10 - so they could have broken it. Difficult to know what has happened and where - anyone else seeing this?

[steve]

Edge works fine for me (21.10547.0.0) both with localhost and viewing my real system on my Raspberry Pi remotely. Do all of the UI pages give the same message?

[gluepack]

I've avoided using the Edge virtually altogether since switching to 10. I have three systems currently running 10. One is busy streaming The Sweeney at the moment but I tried the other two.
One of them, I got the same message as you but my video driver crashed at that moment (it often does) and, although it recovered, I couldn't access Edge, although it was still an active task. I ended the task and tried to restart it but although it is on the taskbar I can't access it. Hovering over it shows some cryptic message about "Closing Chrome." I ended it again. I'll try it again when I reboot sometime.
The other one brought up Edge on the taskbar but no sign of it on screen, then it disappeared. I started it again and this time it came up and I was able to see the MX console.
I'll try the third one, when I get a chance.
I wouldn't use it normally, nor Internet Explorer, only to look at how webpages display across browsers and I need the latter because it is the only browser where I can assure seeing moving images from my webcam.

[philpugh]

Steve,
the mystery deepens a bit - Edge only throws the alert if I omit the http:// in front of the local address.

i.e. http://192.x.x.x:8998 works but 192.x.x.x:8998 doesn't. Up to the other day they both worked fine. Missing the http:// off the default port works as well. I.e. 192.x.x.x/somepage.php works as does sandaysoft.com/forum

Both versions of the :8998 address work in chrome and IE11. We will put it down to an MS glitch and will await the next update!

[steve]

Both versions work fine for me. I'm on the Windows 10 "Insider Program", so it's possible it's something they've fixed now (assuming you're not).

[gluepack]

I'm plagued by nVidia video drivers.

As far as MX is concerned, the difference between it displaying and having a new viewer suggestion come up in Edge is a final slash.

When I start to enter 192... all other browsers (if I have used MX before, which is pretty usual) anticipate 192.168.1.103:8998 whereas Edge, after the first time, anticipates 192.168.1.103:8998/ and if I miss off the / or remove it I get the "new viewer required" message.

[philpugh]

Steve - I will wait to see what develops - thanks.

BTW I am on the insiders programme - but that doesn't mean I will be up to date knowing MS

[philpugh]

To close this off!!

Left PC on whilst out shopping - came back and W10 update was scheduled for installation. Did the deed and now everything is working as I would expect - so probably found the culprit?

[gluepack]

Well my Win 10's are updated all the time (in fact, one was just ten minutes ago). I don't use Edge very often so it doesn't matter to me but my bet is on it requiring the trailing /, which is added behind the scenes by all browsers anyway.