Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Wątek został zamknięty i zarchiwizowany. Jeśli potrzebujesz pomocy, zadaj nowe pytanie.

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

  • 1 odpowiedź
  • 0 osób ma ten problem
  • 176 wyświetleń
  • Ostatnia odpowiedź od SuMo Bot
  • Zablokowany

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.

Wszystkie odpowiedzi (2)

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

This question has been locked because the original author has deleted their account. While you can no longer post new replies, the existing content remains available for reference.