We have upgraded several ePMP-1000 SM’s to firmware version 4.81 in the past few days…
Before upgrading, these SM’s were previously set up to be accessed via their Ethernet ports by HTTP ONLY. Access of the radios by HTTPS on these SM’s was turned off.
As has been the case for the past many firmware versions, EVERY time that a ePMP radio is upgraded to a higher version firmware, the firmware turns back on access by HTTPS - which the firmware versions should not do.
If we have access to the radios set up for HTTP, we want it to stay as HTTP.
As been the case for all of the last firmware versions, when this occurs - you cannot get into the radios via HTTP even though when you finally get in the radio via HTTPS - the radio button in the radio’s software is defaulted back to HTTP/HTTPS, which means you should be able to access the radio by EITHER HTTP or HTTPS. That has never worked.
Now to the crust of the immediate problem… After upgrading these SM’s for current firmware, the only way that you can get into each radio is via HTTPS…
However, when you access each ePMP radio with by it’s preprogrammed IP address (or the default 169.254.1.1 address) - a Windows Crash Report error message is shown after logging into each SM. This message occurs when using Firefox, Chrome or Edge browsers on either computers running Windows 7 or Windows 10.
It appears that there is a problem with the HTTPS certificate (that I assume is being delivered to each ePMP radio) during the firmware upgrade that is sent between the radios and the Windows operating system in the computers after you log on. All of the browsers think that the HTTPS certificate is bogus.
I tried to copy and past the Crash Report Error Message to this message for you to see, however I am unable to get the screen print to paste the picture to this page.
What is causing this and how can you get rid of it?
This is very strange - I don’t think an HTTPS certificate should ever be able to trigger a Windows crash report. I would be very interested to see the screenshot if you are able to capture one (even if you just point a phone camera at your monitor).
I am tempted to suggest that something else on the host computer is causing this; either some antivirus/security software, or perhaps even malware. It sounds like you have tested from multiple computers though.
I will be happy to send the report to you, if you can provide me with your email address.
Again, this screen does not allow the pasting of a Jpeg to this screen.
Yes, it happens on 3 different laptops. I removed AVG and Windows Security from the first laptop and speed a couple of hours looking for other things in Windows 7 that was in the first laptop to no avail.
Rather than being an actual crash report, I believe this is a dialog for configuring ePMP Device Security and Crash Reports. It does appear to be badly titled, and @Danny_Ray_Boyer reported via email that nothing he does on that dialog will actually get rid of it, so we are still investigating.
The problem with “Device Security and Crash Reports configuration” window you described is known and is fixed on 5.9.0. You should be able to change default passwords without any problem using this popup window. Could you please upgrade to this version and see if it works?
Regarding the Web Access mode defaulting to HTTP/HTTPS, this issue is now under investigation of our engineering team.
