Этот сайт имеет ограниченную функциональность, пока мы проводим техническое обслуживание для улучшения его работы. Если какая-либо статья не решила вашу проблему и вы хотите задать вопрос, наше сообщество поддержки ждёт вас: @FirefoxSupport в Твиттере и /r/firefox на Reddit.

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

Cannot Open Developer Toolbox - Component returned failure code: 0x804b000d (NS_ERROR_CONNECTION_REUSED)

  • 8 ответов
  • 0 имеют эту проблему
  • 1 просмотр
  • Последний ответ от 4WoofGrrrr

more options

For months I have been using the Developer Toolbox (Inspector) to develop and test changes to my userChrome.css.

Suddenly, today, when I try to open it, I get an error "Component returned failure code: 0x804b000d (NS_ERROR_CONNECTION_REUSED)" - see attachment for screenshot of entire error message (why doesn't the window allow me to copy and paste?) However, there is no such problem on new PC I am setting up

I am used to getting a dialog asking me to accept the connection, but I am not getting that today. It just silently fails. Did I accidentally reject this connection in the past? If so, is this remembered? How would I "un-remember" this?


I have checked several advanced settings that I have read about:

  • devtools.toolbox.sideEnabled is set to true
  • devtools.debugger.remote-enabled is set to true
  • devtools.debugger.remote-port is set to 6000
  • devtools.debugger.remote-host is set to localhost
  • devtools.debugger.prompt-connection is set to true


I tried restarting in 'Troubleshoot Mode'

I tried downloading and installing over the existing install.

I have tried completely uninstalling and re-installing. No help.

I have tried creating a new profile and using that. No help.

I have tried with my VPN connected AND disconnected.

I have restarted my system. No Help.

Thunderbird is allowed to communicate through the Winders Defender Firewall. I have no other Firewall or Anti-Virus software other than Windows Defender.

I have tried with the firewall both OFF and ON.


TB 102.6.1 (64-bit) on Windows 10, both at latest updates.

I am trying to think of what might have changed in the past few days. I know I HAVE NOT changed Anything in advanced Config. I think I got 102.6.1 a few days ago.

For months I have been using the Developer Toolbox (Inspector) to develop and test changes to my userChrome.css. Suddenly, today, when I try to open it, I get an error "Component returned failure code: 0x804b000d (NS_ERROR_CONNECTION_REUSED)" - see attachment for screenshot of entire error message (why doesn't the window allow me to copy and paste?) However, there is no such problem on new PC I am setting up I am used to getting a dialog asking me to accept the connection, but I am not getting that today. It just silently fails. Did I accidentally reject this connection in the past? If so, is this remembered? How would I "un-remember" this? I have checked several advanced settings that I have read about: * devtools.toolbox.sideEnabled is set to true * devtools.debugger.remote-enabled is set to true * devtools.debugger.remote-port is set to 6000 * devtools.debugger.remote-host is set to localhost * devtools.debugger.prompt-connection is set to true I tried restarting in ''''''Troubleshoot Mode'''''' I tried downloading and installing over the existing install. I have tried completely uninstalling and re-installing. No help. I have tried creating a new profile and using that. No help. I have tried with my VPN connected AND disconnected. I have restarted my system. No Help. Thunderbird is allowed to communicate through the Winders Defender Firewall. I have no other Firewall or Anti-Virus software other than Windows Defender. I have tried with the firewall both OFF and ON. TB 102.6.1 (64-bit) on Windows 10, both at latest updates. I am trying to think of what might have changed in the past few days. I know I HAVE NOT changed Anything in advanced Config. I think I got 102.6.1 a few days ago.
Приложенные скриншоты

Изменено 4WoofGrrrr

Выбранное решение

It seems that we've found the problem.

After completely uninstalling the VPN, things worked again.

The strange thing is, I'm using the same VPN on my new PC with no problem.

Прочитайте этот ответ в контексте 👍 0

Все ответы (8)

more options

(moved this additional info to my initial question now that I know how)

Изменено 4WoofGrrrr

more options

(moved this additional info to my initial question)

Изменено 4WoofGrrrr

more options

Hello

Maybe you clicked on 'disable' when asked to open the toolbox ? check devtools.debugger.remote-enabled in the advanced configuration.

more options

gp said

Hello Maybe you clicked on 'disable' when asked to open the toolbox ? check devtools.debugger.remote-enabled in the advanced configuration.

Thanks for your reply.

  • devtools.debugger.remote-enabled true
more options

Duh, sorry, you did say that in your first post and I missed it. I'm sure that you tried to see all modified settings between the working computer and the not working. Maybe it could be an OS or even a driver problem ? could you start windows in safe mode with networking ?

more options

Well, I think I've found the culprit.

Atfer gp suggested

gp said

Duh, sorry, you did say that in your first post and I missed it. I'm sure that you tried to see all modified settings between the working computer and the not working. Maybe it could be an OS or even a driver problem ? could you start windows in safe mode with networking ?

Thank you.

Problem goes away in Windows Safe Mode. Go figure!

I've tried disconnecting my VPN. And then stopping the service. That didn't help. Now I'm going to uninstall it and see if that helps.

more options

Выбранное решение

It seems that we've found the problem.

After completely uninstalling the VPN, things worked again.

The strange thing is, I'm using the same VPN on my new PC with no problem.

more options

And after re-installing the VPN, the problem did not come back.