This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Switching & Routing
- ExtremeSwitching (VSP/Fabric Engine)
- Re: Can't access devices through EDM since Firefox...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Can't access devices through EDM since Firefox update 64.0
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
12-21-2018 11:06 AM
We're running a lot of ERS4500 series switches ( just under 100) with Avaya v5.7.2.012 firmware. Also a small number of ERS3500 that are experiencing the same issue and our ERS8800 with Firmware 7.1.5.2
Since the Firefox browser update to V64.0 we are unable to access any of the switches using EDM. After the initial login completes it shows '"Discovering Device, please wait' but never progresses.
We have found that devices with Extreme branded firmware :v5.3.8.014 are still working.
When we open the Firefox Web Developer - Debug console we see a message like the following;
TypeError: webServerName is undefined[Learn More] edmContentJs.js:1631:299
Since the Firefox browser update to V64.0 we are unable to access any of the switches using EDM. After the initial login completes it shows '"Discovering Device, please wait' but never progresses.
We have found that devices with Extreme branded firmware :v5.3.8.014 are still working.
When we open the Firefox Web Developer - Debug console we see a message like the following;
TypeError: webServerName is undefined[Learn More] edmContentJs.js:1631:299
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
06-28-2019 10:58 AM
Since the fix (https://bugzilla.mozilla.org/show_bug.cgi?id=1398718) in Firefox 64 is only a configuration change (https://phabricator.services.mozilla.com/D6589), it can be changed back.
Simply insert about:config in the address bar, accept the warning and search for dom.xhr.lowercase_header.enabled and double click it in order to set it to false.
With this change EDM on 5600's is accessible with the newest MFF version.
Simply insert about:config in the address bar, accept the warning and search for dom.xhr.lowercase_header.enabled and double click it in order to set it to false.
With this change EDM on 5600's is accessible with the newest MFF version.
25 REPLIES 25
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
02-18-2019 09:36 AM
* EDM on ERS49/59xx platforms fixed this along 7.5.0.0. Please update to any of 7.5.x or 7.6.x.
* EDM on VSP/VOSS platforms starting with 6.1.3.0 do full support Firefox & Chrome browsers. Please update to any of 6.1.3 or above 7.x -> 8.0.
As previous note, the issue seen in EDM along Firefox v64 is due to an internal browser API change. Mozilla Firefox is moving to align more and more with Chrome browser for internal APIs.
* EDM on VSP/VOSS platforms starting with 6.1.3.0 do full support Firefox & Chrome browsers. Please update to any of 6.1.3 or above 7.x -> 8.0.
As previous note, the issue seen in EDM along Firefox v64 is due to an internal browser API change. Mozilla Firefox is moving to align more and more with Chrome browser for internal APIs.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
02-14-2019 02:59 AM
Paul
This behaviour is even evident on ERS4950GTS with 7.1.0.007 and VSP 8404 with 6.1.1.0 and ERS5952GTS with 7.4.0.10
So even our newest switches have this issue.
Do you know if Extreme is going to be addressing this issue?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
01-28-2019 01:07 PM
Firefox v64 added/fixed Bug 1398718
This change how MFF browser manipulate response headers -> XMLHttpRequest.
Due to this browser API change, EDM (as a client application) on older ERS releases (e.g. 8800) it's no longer processing server response.
To bypass this you can:
a. Use IE11/Edge browsers instead of latest Firefox (current v64);
b. Downgrade MFF to v63 if want to use this browser instead of Microsoft flavors;
c. Update box image to latest version. Some releases have already support for latest MFF or Chrome browser.
This change how MFF browser manipulate response headers -> XMLHttpRequest.
Due to this browser API change, EDM (as a client application) on older ERS releases (e.g. 8800) it's no longer processing server response.
To bypass this you can:
a. Use IE11/Edge browsers instead of latest Firefox (current v64);
b. Downgrade MFF to v63 if want to use this browser instead of Microsoft flavors;
c. Update box image to latest version. Some releases have already support for latest MFF or Chrome browser.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
01-22-2019 02:12 PM
For what it's worth, Firefox ESR 60.4.0esr resolved this issue for us.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
01-07-2019 05:59 PM
Agree. As a workaround I keep an 12-14yr old laptop running a 5yo version of Xubuntu. Very solid.
And I just keep the laptop air-gapped when its not in use. I only use it when I have to. I only use it to visit the web-interfaces for switches I control.
