Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Firefox can't connect to google from searchbar

  • 1 antwurd
  • 1 hat dit probleem
  • 8 werjeftes
  • Lêste antwurd fan 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.

Keazen oplossing

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

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (1)

rspencer01
rspencer01 Fraacheigener
more options

Keazen oplossing

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