Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Mozilla 도움말 검색

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

자세히 살펴보기

Web Acceleration Client Error (513) - Internal Error The Web Acceleration Client detected an internal error which caused the connection between the Web Acceler

  • 1 답장
  • 1 이 문제를 만남
  • 552 보기
  • 최종 답변자: ideato

more options

Web Acceleration Client Error (513) - Internal Error The Web Acceleration Client detected an internal error which caused the connection between the Web Acceleration Client and Web Acceleration Server to be broken. Retrying the web page may correct the problem.

I get this error continuously when working in the ancestry.com website. I have to reload the page on almost every search I do on that website. This is the ONLY website that I get this error message on, can work continuously for several hours on other websites and never get this message. I've talked to the people at Ancestry.com support and they made 2 recommendations: turn of antivirus (did not help) or switch to another web browser. I tried both IE 11 and Chrome Version 31.0.1650.63 m and I did not have the problem with either of those 2 browsers getting this error.

Is there a problem with how Firefox and ancestry.com are communicating with each other?

Web Acceleration Client Error (513) - Internal Error The Web Acceleration Client detected an internal error which caused the connection between the Web Acceleration Client and Web Acceleration Server to be broken. Retrying the web page may correct the problem. I get this error continuously when working in the ancestry.com website. I have to reload the page on almost every search I do on that website. This is the ONLY website that I get this error message on, can work continuously for several hours on other websites and never get this message. I've talked to the people at Ancestry.com support and they made 2 recommendations: turn of antivirus (did not help) or switch to another web browser. I tried both IE 11 and Chrome Version 31.0.1650.63 m and I did not have the problem with either of those 2 browsers getting this error. Is there a problem with how Firefox and ancestry.com are communicating with each other?

선택된 해결법

Hello byron.lewis, many site issues can be caused by corrupt cookies or cache. In order to try to fix these problems, the first step is to clear both cookies and the cache. Note: This will temporarily log you out of all sites you're logged in to. To clear cache and cookies do the following:

  1. Go to Firefox > History > Clear recent history or (if no Firefox button is shown) go to Tools > Clear recent history.
  2. Under "Time range to clear", select "Everything".
  3. Now, click the arrow next to Details to toggle the Details list active.
  4. From the details list, check Cache and Cookies and uncheck everything else.
  5. Now click the Clear now button.

Further information can be found in the Clear your cache, history and other personal information in Firefox article.

Did this fix your problems? Please report back to us!

Thank you.

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

모든 댓글 (1)

more options

선택된 해결법

Hello byron.lewis, many site issues can be caused by corrupt cookies or cache. In order to try to fix these problems, the first step is to clear both cookies and the cache. Note: This will temporarily log you out of all sites you're logged in to. To clear cache and cookies do the following:

  1. Go to Firefox > History > Clear recent history or (if no Firefox button is shown) go to Tools > Clear recent history.
  2. Under "Time range to clear", select "Everything".
  3. Now, click the arrow next to Details to toggle the Details list active.
  4. From the details list, check Cache and Cookies and uncheck everything else.
  5. Now click the Clear now button.

Further information can be found in the Clear your cache, history and other personal information in Firefox article.

Did this fix your problems? Please report back to us!

Thank you.