Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

"Unable to connect" to remote pages ("Could not read chrome manifest file"); local pages OK; proxy set to none -- what to do?

  • 2 답장
  • 1 이 문제를 만남
  • 6 보기
  • 최종 답변자: gordonbr

more options

Firefox 5.0.1, claims to be up to date (how did it know that if it couldn't connect to the Web?), Windows XP Home 2002 SP3 on Dell DIM3000 Pentium 4, 3 GHz, 1 GB Ram.

Internet Explorer (8.0.6001.18702 with 128-bit cipher) and Opera (10.2? can't get it to display its version) can both access all local and remote (Web) pages -- Firefox does fine with all local pages but can't connect to anything remote.

Firefox 5.0.1, claims to be up to date (how did it know that if it couldn't connect to the Web?), Windows XP Home 2002 SP3 on Dell DIM3000 Pentium 4, 3 GHz, 1 GB Ram. Internet Explorer (8.0.6001.18702 with 128-bit cipher) and Opera (10.2? can't get it to display its version) can both access all local and remote (Web) pages -- Firefox does fine with all local pages but can't connect to anything remote.

선택된 해결법

A possible cause is security software (firewall) that blocks or restricts Firefox or the plugin-container process without informing you, possibly after detecting changes (update) to the Firefox program.

Remove all rules for Firefox from the permissions list in the firewall and let your firewall ask again for permission to get full unrestricted access to internet for Firefox and the plugin-container process and the updater process.

See:

문맥에 따라 이 답변을 읽어주세요 👍 0

모든 댓글 (2)

more options

선택된 해결법

A possible cause is security software (firewall) that blocks or restricts Firefox or the plugin-container process without informing you, possibly after detecting changes (update) to the Firefox program.

Remove all rules for Firefox from the permissions list in the firewall and let your firewall ask again for permission to get full unrestricted access to internet for Firefox and the plugin-container process and the updater process.

See:

more options

Yes, the Firewall was the issue. I had already stumbled upon that, but thanks anyway.