Join the AMA (Ask Me Anything) with Firefox leadership team to talk about Firefox priorities in 2024. Mark your calendar! Thursday, June 13, 17:00 - 19:00 UTC.

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

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

The address wasn’t understood (webpack)

  • 4 fhreagra
  • 0 leis an bhfadhb seo
  • 79 views
  • Freagra is déanaí ó cor-el

more options

Please excuse me if I miss any details.... this is my third time trying to submit this issue.

I will just skip to the meat of it this time. I'm getting this error while working from my localhost. I have been working on a personal project for years with this set up with no issues until today. I can no longer click on the errors in the console log and be directed to the Debugger tab. When I click on errors, nothing happens. If I try to open them in a New Tab, I get the error below:


The address wasn’t understood

Firefox doesn’t know how to open this address, because one of the following protocols (webpack) isn’t associated with any program or is not allowed in this context.

   You might need to install other software to open this address.


I have also noticed firefox does not even load all the files until I refresh it at least twice. Even when it is all loaded properly, the error persists.

I have tried: - restarting firefox - restarting my computer - clearing ALL cache and cookies - running firefox in safe mode - disabling all add ons - disabling performance mode (was already off) - checking network.protocol-handler.external.javascript = false (it is)

Let me know if there is any other information I can provide. I really dislike having to work in chrome for this so I hope I can find a solution as soon as possible.

Please excuse me if I miss any details.... this is my third time trying to submit this issue. I will just skip to the meat of it this time. I'm getting this error while working from my localhost. I have been working on a personal project for years with this set up with no issues until today. I can no longer click on the errors in the console log and be directed to the Debugger tab. When I click on errors, nothing happens. If I try to open them in a New Tab, I get the error below: ''The address wasn’t understood Firefox doesn’t know how to open this address, because one of the following protocols (webpack) isn’t associated with any program or is not allowed in this context. You might need to install other software to open this address.'' I have also noticed firefox does not even load all the files until I refresh it at least twice. Even when it is all loaded properly, the error persists. I have tried: - restarting firefox - restarting my computer - clearing ALL cache and cookies - running firefox in safe mode - disabling all add ons - disabling performance mode (was already off) - checking network.protocol-handler.external.javascript = false (it is) Let me know if there is any other information I can provide. I really dislike having to work in chrome for this so I hope I can find a solution as soon as possible.

Réiteach roghnaithe

The strangest thing occured again... it managed to resolve itself without my intervention. I left it alone after I posted this question and now it works again. Despite this, I will post the information requested anyway.

An example URL that previously didn't work : webpack:///src/ui/common_menus.js?2237 With out without the url query on the end still didn't work.

Attached is a screenshot of the error in the console. A totally normal javascript error. Whether I clicked the lines under the error or next to the error, they did not resolve to the Debugger tab. Nothing would happen.

But as I mentioned.... it fixed itself and I have no idea why or how. So frustrating trying to chase this down for once and then it just starts working again without cause or reason. My apologies. I have never been able to intentionally cause this bug. It just appears to torment me for a few hours ever few months.

Even though I found similar issues mention here on support, maybe my issue has something to do with my own set up somehow.

Read this answer in context 👍 0

All Replies (4)

more options

What's the problem URL and actual screenshot of the error so there can replicate the issue?

more options

Réiteach Roghnaithe

The strangest thing occured again... it managed to resolve itself without my intervention. I left it alone after I posted this question and now it works again. Despite this, I will post the information requested anyway.

An example URL that previously didn't work : webpack:///src/ui/common_menus.js?2237 With out without the url query on the end still didn't work.

Attached is a screenshot of the error in the console. A totally normal javascript error. Whether I clicked the lines under the error or next to the error, they did not resolve to the Debugger tab. Nothing would happen.

But as I mentioned.... it fixed itself and I have no idea why or how. So frustrating trying to chase this down for once and then it just starts working again without cause or reason. My apologies. I have never been able to intentionally cause this bug. It just appears to torment me for a few hours ever few months.

Even though I found similar issues mention here on support, maybe my issue has something to do with my own set up somehow.

more options

Hi

Thank you for letting us know. If you could mark your update as the solution, it may help others in the same situation in the future.

more options

This might still have been a problem with files cached somewhere (possibly not in Firefox, but on the localhost server) and source maps.

You can reload webpage(s) and bypass the cache to refresh possibly outdated or corrupted files.

  • hold down the Shift key and left-click the Reload button
  • press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • press "Command + Shift + R" (Mac)