Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

Firefox can't connect to google from searchbar

  • 1 wotmołwa
  • 1 ma tutón problem
  • 5 napohladow
  • Poslednja wotmołwa wot rspencer01

rspencer01
rspencer01
more options

I recently had someone malicious change my router's DNS server IP address to a bad one. When it was changed, I could not access google or facebook. I have fixed it and can browse both sites, but the search toolbar in the top right won't take me to google. I get an "Unable to connect" error. Doing other search engines (eg wikipedia) is fine.

Firefox 37 right out of the box (+router nonsense) on Ubuntu 14.

I recently had someone malicious change my router's DNS server IP address to a bad one. When it was changed, I could not access google or facebook. I have fixed it and can browse both sites, but the search toolbar in the top right won't take me to google. I get an "Unable to connect" error. Doing other search engines (eg wikipedia) is fine. Firefox 37 right out of the box (+router nonsense) on Ubuntu 14.

Wubrane rozrisanje

Time seems to have fixed it. Perhaps the https//google.com ip was cached or something.

Tutu wotmołwu w konteksće čitać 👍 0

Wšě wotmołwy (1)

rspencer01
rspencer01 Prašer
more options

Wubrane rozrisanje

Time seems to have fixed it. Perhaps the https//google.com ip was cached or something.