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!

Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

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

  • 1 odpověď
  • 0 má tento problém
  • 1 zobrazení
  • Poslední odpověď od 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.

Upravil uživatel billeverhart dne

Všechny odpovědi (1)

more options

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