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

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

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

  • 1 amsa
  • 1 yana da wannan matsala
  • 213 views
  • Amsa ta ƙarshe daga 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?

Mafitar da aka zaɓa

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.

Karanta wannan amsa a matsayinta 👍 0

All Replies (1)

more options

Zaɓi Mafita

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.