This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Authentication required when open firefox after installing NoScript

  • 1 antwoord
  • 12 hierdie probleem
  • 9 views
  • Laaste antwoord deur vahidjavani

more options

Whenever I open Firefox authentication required pop-up appeared even when NoScript is in Allow Script Globally mode. The text of this pop-up is: 'A username and password are being requested by http://MY_INTERNET_IP_ADDRESS. The site says: "DSL-xxxxx" ' when I type user/pass my router or close it pop-up disappeared, but if fill out with wrong password ask me again.

In NoScript addon there is no any blocked script. Also this happen only when I connect to the router (connect via Ethernet), even not happen when I connect to another router with WiFI. Could you please help me to get rid of the annoying pop-up.

Whenever I open Firefox authentication required pop-up appeared even when NoScript is in Allow Script Globally mode. The text of this pop-up is: 'A username and password are being requested by http://MY_INTERNET_IP_ADDRESS. The site says: "DSL-xxxxx" ' when I type user/pass my router or close it pop-up disappeared, but if fill out with wrong password ask me again. In NoScript addon there is no any blocked script. Also this happen only when I connect to the router (connect via Ethernet), even not happen when I connect to another router with WiFI. Could you please help me to get rid of the annoying pop-up.

Gewysig op deur vahidjavani

Gekose oplossing

Solved when uncheck WAN IP -> LOCAL

Lees dié antwoord in konteks 👍 0

All Replies (1)

more options

Gekose oplossing

Solved when uncheck WAN IP -> LOCAL