Avatar for Username

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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Can't connect to internet after automatic update

  • 2 uphendule
  • 101 zinale nkinga
  • 1 view
  • Igcine ukuphendulwa ngu Stoneyec2

AnonymousUser
AnonymousUser
more options

Firefox had an automatic update this morning and ever since then I always get the page "The connection was reset". Msn messenger still works so the internet connection isn't the problem. This is on my laptop(I'm currently on my PC) and it's on Windows XP, it's firewall is ESET Smart Security. I checked Error Console and there's one that appears, "Livemark Service: feed processor received an invalid channel for http://en-us.fxfeeds.mozilla.com/en-US/firefox/headlines.xml"

This happened

Every time Firefox opened

== Automatic update on June 27, 2010

Firefox had an automatic update this morning and ever since then I always get the page "The connection was reset". Msn messenger still works so the internet connection isn't the problem. This is on my laptop(I'm currently on my PC) and it's on Windows XP, it's firewall is ESET Smart Security. I checked Error Console and there's one that appears, "Livemark Service: feed processor received an invalid channel for http://en-us.fxfeeds.mozilla.com/en-US/firefox/headlines.xml" == This happened == Every time Firefox opened == Automatic update on June 27, 2010

Isisombululo esikhethiwe

nvm i just had to change connection settings to auto-proxy the auto update must have changed the settings

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 0

All Replies (2)

AnonymousUser
AnonymousUser Umnikazi wombuzo
more options

Isisombululo Esikhethiwe

nvm i just had to change connection settings to auto-proxy the auto update must have changed the settings

Stoneyec2
Stoneyec2
more options

I have tried changing to auto-proxy but still get the same error message even in safe mode.