Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

FF 15.01 Cannot Access Router Admin Page (Netgear WNDR3700)

  • 2 பதிலளிப்புகள்
  • 3 இந்த பிரச்னைகள் உள்ளது
  • 4 views
  • Last reply by wmcole

I can log into the page, log out of the page, and it displays all the forms on each settings page, however the current settings are not filled in and I cannot make any changes.

Error console shows a slew of error messages like:

Timestamp: 9/15/2012 8:35:32 PM Error: Exposing chrome JS objects to content without __exposedProps__ is insecure and deprecated. See https://developer.mozilla.org/en/XPConnect_wrappers for more information. Source File: resource://jid0-lmznvk7a82o8cufhdfb9dudfa2w-at-jetpack/api-utils/lib/cuddlefish.js -> resource://jid0-lmznvk7a82o8cufhdfb9dudfa2w-at-jetpack/api-utils/lib/sandbox.js -> resource://jid0-lmznvk7a82o8cufhdfb9dudfa2w-at-jetpack/api-utils/data/worker.js Line: 130

whenever I invoke the page.

I have selected to enable JavaScript and Java. This appears to a worsening of the problem associated with showing, and being able to execute buttons in web mail at my company web host, Infoquest.com (reported for FF4. and later, never bee addressed). Also, each new rev of FF seems to increase the number of existing web pages that FF can't properly handle, especially script-driven and interactive pages like the Hewlett Packard Support Community Forums - you can type a message all you want, but FF will not let you execute the "Post" button.

NOTE: this just started in FF 15. Until this time I had "normal" access and control of the router. Now I have to use IE 9.

(Win 7 64-bit, sp1)

I can log into the page, log out of the page, and it displays all the forms on each settings page, however the current settings are not filled in and I cannot make any changes. Error console shows a slew of error messages like: Timestamp: 9/15/2012 8:35:32 PM Error: Exposing chrome JS objects to content without __exposedProps__ is insecure and deprecated. See https://developer.mozilla.org/en/XPConnect_wrappers for more information. Source File: resource://jid0-lmznvk7a82o8cufhdfb9dudfa2w-at-jetpack/api-utils/lib/cuddlefish.js -> resource://jid0-lmznvk7a82o8cufhdfb9dudfa2w-at-jetpack/api-utils/lib/sandbox.js -> resource://jid0-lmznvk7a82o8cufhdfb9dudfa2w-at-jetpack/api-utils/data/worker.js Line: 130 whenever I invoke the page. I have selected to enable JavaScript and Java. This appears to a worsening of the problem associated with showing, and being able to execute buttons in web mail at my company web host, Infoquest.com (reported for FF4. and later, never bee addressed). Also, each new rev of FF seems to increase the number of existing web pages that FF can't properly handle, especially script-driven and interactive pages like the Hewlett Packard Support Community Forums - you can type a message all you want, but FF will not let you execute the "Post" button. NOTE: this just started in FF 15. Until this time I had "normal" access and control of the router. Now I have to use IE 9. (Win 7 64-bit, sp1)

தீர்வு தேர்ந்தெடுக்கப்பட்டது

hello wmcole, the error message that you've cited is triggered by one of the addons that you have installed - although i'm not sure if it is causing the problems on your router's web interface. please try launching firefox in safe mode once and see if the issue is occurring there too.

Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems

Read this answer in context 👍 1

All Replies (2)

தீர்வு தேர்ந்தெடுக்கப்பட்டது

hello wmcole, the error message that you've cited is triggered by one of the addons that you have installed - although i'm not sure if it is causing the problems on your router's web interface. please try launching firefox in safe mode once and see if the issue is occurring there too.

Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems

That did it. The culprit was the Dragon Naturally Speaking v12 add-on.

Thanks.

wmc