Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Firefox takes a long time to resolve first website, but is fine after that

  • 1 Antwort
  • 0 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von billeverhart

more options

We are using firefox on Redhat 7 workstations and, when we first open firefox and attempt to load a web address it takes 25-30 seconds to connect.

After that first attempt, web addresses load almost instantly.

Our systems are only connected to a local network and not the internet, if that makes a difference. Also, we are using web addresses and not IP addresses. When I try by Ip address it's much faster, but I get the security risk warning for the ssl cert. So I'm not sure if my issue is something between firefox and dns, or if it has to do with the SSL certs? Both dns and ssl are handled by Red Hat IDM.

We are seeing the same behavior on all of our workstations.

We are using firefox on Redhat 7 workstations and, when we first open firefox and attempt to load a web address it takes 25-30 seconds to connect. After that first attempt, web addresses load almost instantly. Our systems are only connected to a local network and not the internet, if that makes a difference. Also, we are using web addresses and not IP addresses. When I try by Ip address it's much faster, but I get the security risk warning for the ssl cert. So I'm not sure if my issue is something between firefox and dns, or if it has to do with the SSL certs? Both dns and ssl are handled by Red Hat IDM. We are seeing the same behavior on all of our workstations.

Geändert am von billeverhart

Alle Antworten (1)

more options

I noticed today that if I start firefox with --safe-mode the issue goes away.