X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Work around for server not found problems on FF36

Kuphostiwe

I have found a work around for all the people having server not found problems with FF36.

If you manually set your network adapter DNS to an external DNS server (as opposed to your local ISP) then the problem goes away. I set mine to use the two google DNS servers:

 Preferred: 8.8.8.8
 Alternate: 8.8.4.4

Not a clue why this works but it is 100% successful on my desktop PC, whereas before I could hardly connect to a webpage with FF36 without multiple page refreshes and much frustration, even though FF35 was fine and rolling back to FF35 was also fine.

Something has changed in FF36 and either the way it handles DNS or the way it works with some network adapters.

It is nothing to do with add-ons, profiles or firewall software as I have tried all of these things and only the DNS change made a difference. I even copied over a full working profile and the program files directory for Mozilla from my portable which was having no problems and the problem still existed on the desktop, which is why I started looking at the network adapater since everything else between the working PC and the non working one was identical.

Hopefully this will help the developers to pin down the real cause of the problem and fix it in the next release.

I have found a work around for all the people having server not found problems with FF36. If you manually set your network adapter DNS to an external DNS server (as opposed to your local ISP) then the problem goes away. I set mine to use the two google DNS servers: Preferred: 8.8.8.8 Alternate: 8.8.4.4 Not a clue why this works but it is 100% successful on my desktop PC, whereas before I could hardly connect to a webpage with FF36 without multiple page refreshes and much frustration, even though FF35 was fine and rolling back to FF35 was also fine. Something has changed in FF36 and either the way it handles DNS or the way it works with some network adapters. It is nothing to do with add-ons, profiles or firewall software as I have tried all of these things and only the DNS change made a difference. I even copied over a full working profile and the program files directory for Mozilla from my portable which was having no problems and the problem still existed on the desktop, which is why I started looking at the network adapater since everything else between the working PC and the non working one was identical. Hopefully this will help the developers to pin down the real cause of the problem and fix it in the next release.

Isisombululo esikhethiwe

Ag - your problem does seem different as you had FF36 working.

Whereas the problem a lot of us have is that when we upgrade from FF35 to FF36 we get a lot of Server not found errors when trying to load webpages.

Sometimes they load and then they stop loading, and then if you hit refresh a lot they sometimes then load again, or you have to wait a minute or two and then they load.

For some reason using an external DNS server {see #answer-698286 ~J99} has stopped this problem completely, as does going back to FF35.

We would need an expert on DNS resolution at Mozilla to look into this. [*]See My note under ~J99 Strikes me that using an external DNS server adds some latency to the name resolution and maybe this is needed for the network card in the PC's that are having this problem to resolve the webpage addresses.

Obviously something has changed from FF35 to FF36 to cause this problem. I am open to Mozilla contacting me via Email if they wish me to try anything else to help them pin this down.


*

edit Note from John99 Mozilla may investigate IF we are able to provide evidence supporting this. We need to be able to file a bug with good Steps To Reproduce (STR). Developers need to be able to see the problem themselves before we can expect them to look into this.

Funda le mpendulo ngokuhambisana nalesi sihloko 0

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Adobe PDF Plug-In For Firefox and Netscape 11.0.10
  • Amazon MP3 Downloader Plugin 1.0.18
  • Intel web components for Intel® Identity Protection Technology
  • Intel web components updater - Installs and updates the Intel web components
  • Next Generation Java Plug-in 11.31.2 for Mozilla browsers
  • NVIDIA 3D Vision Streaming plugin for Mozilla browsers
  • NVIDIA 3D Vision plugin for Mozilla browsers
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
  • Shockwave Flash 16.0 r0
  • 5.1.30514.0

Isisebenziso

  • I-ejenti Engumsebenzisi: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0

Eminye Imininingwane

hommealone 0 izisombululo 3 izimpendulo
Kuphostiwe

Impendulo Ewusizo

Thanks so much for discovering and posting this work-around!

Could you please be more explicit about exactly what settings should be applied, how to get to the screens where those settings should be made, and when to make them (before or after updating; can they be applied after the update, once the problem has already surfaced)? I know that those detailed directions would be a big help to me, and probably to a lot of others as well.

Thanks again!

Thanks so much for discovering and posting this work-around! Could you please be more explicit about exactly what settings should be applied, how to get to the screens where those settings should be made, and when to make them (before or after updating; can they be applied after the update, once the problem has already surfaced)? I know that those detailed directions would be a big help to ''me'', and probably to a lot of others as well. Thanks again!

Umnikazi wombuzo

Solution works fine even after installing FF36 and I have had no problems at all today for the first time since I installed it.

Use the following either of the following links to see how to manually set DNS:

http://support.simpledns.com/kb/a72/configuring-windows-7-to-use-local-dns-server.aspx

https://developers.google.com/speed/public-dns/docs/using

Solution works fine even after installing FF36 and I have had no problems at all today for the first time since I installed it. Use the following either of the following links to see how to manually set DNS: http://support.simpledns.com/kb/a72/configuring-windows-7-to-use-local-dns-server.aspx https://developers.google.com/speed/public-dns/docs/using

Okulungisiwe ngu smow

hommealone 0 izisombululo 3 izimpendulo
Kuphostiwe

Thanks for the link!

It sounds like this issue is due to a bug of some sort in the V36 update, no? If you or anyone else has any familiarity or past experience with how Mozilla works, would you expect that this is a 'glitch' whose correction will make it to an update of Firefox relatively quickly, or do you imagine that it will take some time before this is smoothed out?

Thanks for the link! It sounds like this issue is due to a bug of some sort in the V36 update, no? If you or anyone else has any familiarity or past experience with how Mozilla works, would you expect that this is a 'glitch' whose correction will make it to an update of Firefox relatively quickly, or do you imagine that it will take some time before this is smoothed out?
John99 971 izisombululo 13138 izimpendulo
Kuphostiwe

Hi smow, Thanks for posting a workaround.

People are already posting links to this thread. Perhaps you would like to give more information about the problem you see, maybe someone can provide a solution.

  • Note you aught to be able to attach screenshots in this thread
    How do I create a screenshot of my problem? (\use something compressed: a .jpeg or .gif rather than a bitmap, Windows snipping tool would be create a suitable image file.)

However I am sure a lot of users will want to know what causes any such problem, and of course if the problem may be demonstrated and confirmed I am sure Firefox developers will be interested in this and we (this forum & site) will try to document or better still get a fix for the problem)

Anyone with this problem

Please vote by using the button [I have this problem, too] If you do see a problem and need a solution please post a new question of your own. When doing so please try to follow the prompts to include full troubleshooting information, using the add-on offered. Please use this special link to post.

Hi smow, Thanks for posting a workaround. People are already posting links to this thread. Perhaps you would like to give more information about the problem you see, maybe someone can provide a solution. *Note you aught to be able to attach screenshots in this thread <br /> [[How do I create a screenshot of my problem?]] (\use something compressed: a .jpeg or .gif rather than a bitmap, Windows snipping tool would be create a suitable image file.) However I am sure a lot of users will want to know what causes any such problem, and of course if the problem may be demonstrated and confirmed I am sure Firefox developers will be interested in this and we (this forum & site) will try to document or better still get a fix for the problem) ===Anyone with this problem === Please vote by using the button [I have this problem, too] If you do see a problem and need a solution please post a new question of your own. When doing so please try to follow the prompts to include full troubleshooting information, using the add-on offered. Please use this [https://support.mozilla.org/en-US/questions/new/desktop/websites?search=Error+server+not+found+Firefox+36+503%28%2Fquestions%2F1049998%29#summarize-question special link] to post.
AG 0 izisombululo 7 izimpendulo
Kuphostiwe

I was using v36 with no problems. I added a password to my winXP user account and the system hung during application of security creds to all my files. Upon restarting, FFv36 continually give SERVER NOT FOUND error to any URL, while Chrome responds fine. It seems to me that something is blocking before even trying to resolve DNS. It works great in SAFE MODE w/ NETWORKING. So something my system is loading is blocking -- cannot determine what!! If anyone has any steps to try -- please reach out!!

I was using v36 with no problems. I added a password to my winXP user account and the system hung during application of security creds to all my files. Upon restarting, FFv36 continually give SERVER NOT FOUND error to any URL, while Chrome responds fine. It seems to me that something is blocking before even trying to resolve DNS. It works great in SAFE MODE w/ NETWORKING. So something my system is loading is blocking -- cannot determine what!! If anyone has any steps to try -- please reach out!!
John99 971 izisombululo 13138 izimpendulo
Kuphostiwe

Hi AG, I see you already have your own thread:

Hi AG, I see you already have your own thread: * ''Server Not Found error only affects Firefox'' [/questions/1049876]

Isisombululo Esikhethiwe

Ag - your problem does seem different as you had FF36 working.

Whereas the problem a lot of us have is that when we upgrade from FF35 to FF36 we get a lot of Server not found errors when trying to load webpages.

Sometimes they load and then they stop loading, and then if you hit refresh a lot they sometimes then load again, or you have to wait a minute or two and then they load.

For some reason using an external DNS server {see #answer-698286 ~J99} has stopped this problem completely, as does going back to FF35.

We would need an expert on DNS resolution at Mozilla to look into this. [*]See My note under ~J99 Strikes me that using an external DNS server adds some latency to the name resolution and maybe this is needed for the network card in the PC's that are having this problem to resolve the webpage addresses.

Obviously something has changed from FF35 to FF36 to cause this problem. I am open to Mozilla contacting me via Email if they wish me to try anything else to help them pin this down.


*

edit Note from John99 Mozilla may investigate IF we are able to provide evidence supporting this. We need to be able to file a bug with good Steps To Reproduce (STR). Developers need to be able to see the problem themselves before we can expect them to look into this.

Ag - your problem does seem different as you had FF36 working. Whereas the problem a lot of us have is that when we upgrade from FF35 to FF36 we get a lot of Server not found errors when trying to load webpages. Sometimes they load and then they stop loading, and then if you hit refresh a lot they sometimes then load again, or you have to wait a minute or two and then they load. For some reason using an external DNS server {see [[#answer-698286]] <sub>~J99</sub>} has stopped this problem completely, as does going back to FF35. We would need an expert on DNS resolution at Mozilla to look into this. [*]<sup>See My note under ~J99</sup> Strikes me that using an external DNS server adds some latency to the name resolution and maybe this is needed for the network card in the PC's that are having this problem to resolve the webpage addresses. Obviously something has changed from FF35 to FF36 to cause this problem. I am open to Mozilla contacting me via Email if they wish me to try anything else to help them pin this down. --------- ==*== '''edit''' Note from John99 ''Mozilla may investigate IF we are able to provide evidence supporting this. We need to be able to file a bug with good Steps To Reproduce (STR). Developers need to be able to see the problem themselves before we can expect them to look into this. ''

Okulungisiwe ngu John99

FredMcD
  • Top 10 Contributor
4245 izisombululo 59390 izimpendulo
Kuphostiwe

Hey, smow. That was very good work. Well Done. Please flag your last post #answer-698286 as Solved Problem so other will know.

Hey, smow. That was very good work. Well Done. Please flag your last post [[#answer-698286]] as '''Solved Problem''' so other will know.
John99 971 izisombululo 13138 izimpendulo
Kuphostiwe

If the problem is real and related to F36 we need to file a bug to get this investigated and fixed. (The 503 errors I did get turned out to be genuine server glitches.)

I am not able to reproduce personally, and am not going to file a bug for this unless I see multiple posts confirming the problem. In fact if this problem goes away in Windows safemode it could be some Windows issue or due to third party software or even malware. I did invite others to vote and post, but I am not seeing votes increasing, or any additional posts check

The problem may be real but site or ISP specific. That would explain why we are not seeing many reports of this, and why (afaik) no bug has been filed. As I mentioned upthread attaching a screenshot and giving examples where this is seen may help.

  1. To rule out malware please scan with multiple tools as explained in
  2. If you do suspect the issue due to a Firefox 36 problem. One change in Fx36 was support for HTTP/2 and conceivably that could somehow be involved. It is possible to temporarily disable that for test purposes. (Remember to flip the pref back again after testing)
    Toggle the two prefs to false using about:config
    1. network.http.spdy.enabled.http2
    2. network.http.spdy.enabled.http2draft

edit: couple of typos

If the problem is real and related to F36 we need to file a bug to get this investigated and fixed. (The 503 errors I did get turned out to be genuine server glitches.) I am not able to reproduce personally, and am not going to file a bug for this unless I see multiple posts confirming the problem. In fact if this problem goes away in Windows safemode it could be some Windows issue or due to third party software or even malware. I did invite others to vote and post, but I am not seeing votes increasing, or any additional posts [https://support.mozilla.org/en-US/search/advanced?q=1049998&num_voted=0&num_votes=&asked_by=&answered_by=&q_tags=&errorcreated=0&created_date=&updated=0&updated_date=&sortby=0&a=1&w=2 check] The problem may be real but site or ISP specific. That would explain why we are not seeing many reports of this, and why (afaik) no bug has been filed. As I mentioned [[#answer-698314|upthread]] attaching a screenshot and giving examples where this is seen may help. #To rule out malware please scan with multiple tools as explained in #* [[Troubleshoot Firefox issues caused by malware]] #* For general problem with page loading see <br />[[Firefox can't load websites but other browsers can]] <br />[[Websites show a spinning wheel and never finish loading]] #If you do suspect the '''issue due to a Firefox 36 problem'''. One change in Fx36 was support for HTTP/2 and conceivably that could somehow be involved. It is possible to temporarily disable that for test purposes. (Remember to flip the pref back again after testing) <br /> Toggle the two prefs to false using about:config ## network.http.spdy.enabled.http2 ## network.http.spdy.enabled.http2draft #* See http://kb.mozillazine.org/About:config <sub>edit: couple of typos </sub>

Okulungisiwe ngu John99

Umnikazi wombuzo

Looks like there was a major DNS change to FF 36 and it has a bug fix already allocated to it.

https://bugzilla.mozilla.org/show_bug.cgi?id=1093983

A quick test appears to verify this was the problem. I reverted back to using my local ISP's DNS server and then went into about:config and set network.dns.get-ttl to false. You then have to exit out of FF and run it again. After that it all works without problems as far as I can see.

So the next build may well have this fixed but for now the change to get_ttl fixes things.

Any chance someone with access to the bug system can update the bug report to point to the problems some of us have been having due to the change and how we now have to disable get-ttl to get server names resolved. Thanks.

Looks like there was a major DNS change to FF 36 and it has a bug fix already allocated to it. https://bugzilla.mozilla.org/show_bug.cgi?id=1093983 A quick test appears to verify this was the problem. I reverted back to using my local ISP's DNS server and then went into about:config and set network.dns.get-ttl to false. You then have to exit out of FF and run it again. After that it all works without problems as far as I can see. So the next build may well have this fixed but for now the change to get_ttl fixes things. Any chance someone with access to the bug system can update the bug report to point to the problems some of us have been having due to the change and how we now have to disable get-ttl to get server names resolved. Thanks.

Okulungisiwe ngu smow

John99 971 izisombululo 13138 izimpendulo
Kuphostiwe

Impendulo Ewusizo

Well done. Thanks for finding that.

That is not only assigned but has an approved patch included in the scheduled Fx36.0.1 release so it should be fixed in few days, watch out for the upgrade.

With the bug now fixed it would not really be appropriate to add further comment. I do now see another related bug assigned but not being fast tracked, so if all goes well that will probably land in Firefox 39.

  • Bug 1138242 - DNS: Request A and AAAA record types rather than ANY when obtaining TTL on Windows
Well done. Thanks for finding that. That is not only assigned but has an approved patch included in the scheduled Fx36.0.1 release so it should be fixed in few days, watch out for the upgrade. * Bug 1093983 - DNS resolver should not use 'ANY' to get cached records for TTL <sup>[https://bugzilla.mozilla.org/show_bug.cgi?id=1093983#c35 c#35]</sup> * https://wiki.mozilla.org/Firefox/Channels/Meetings/2015-03-03#Schedule_Update With the bug now fixed it would not really be appropriate to add further comment. I do now see another related bug assigned but not being fast tracked, so if all goes well that will probably land in Firefox 39. * Bug 1138242 - DNS: Request A and AAAA record types rather than ANY when obtaining TTL on Windows
Irish_Steve 0 izisombululo 9 izimpendulo
Kuphostiwe

Thanks for the pointer to how to resolve, I will post locally, as it's been causing severe pain here in Ireland with local ISP's, with many transactions hanging or failing to complete on the first attempt.

Thanks for the pointer to how to resolve, I will post locally, as it's been causing severe pain here in Ireland with local ISP's, with many transactions hanging or failing to complete on the first attempt.
John99 971 izisombululo 13138 izimpendulo
Kuphostiwe

Irish_Steve A change being made any day now and released as Fx36.0.1 may resolve this issue. If you use Firefox Menu Button -> Help -> AboutFirefox each day that will check to see if the upgrade is available.

There is a pref change that may be implemented by a use of about:config, but it is probably best not to advise the average end user of Firefox to try to do that.


For those wishing to try the fix immediately /questions/1049876#answer-699245

The easiest method is just to wait a few days for the Fx36.0.1 update. If you use
Firefox Menu Button -> Help -> AboutFirefox
each day that will check to see if the upgrade is available.

The bug fix is I think merely changing prefs and so you could do that yourself. It may be safer to use a spare additional profile, or backup the file prefs.js when trying that initially, because making mistakes in about:config may break Firefox. Just toggling the pref network.dns.get-ttl to false should fix the issue, that basically is what is done in
Bug 1093983 - DNS resolver should not use 'ANY' to get cached records for TTL 

One of the bug fixes about to be applied in the imminent Fx36.0.1 point Release

Irish_Steve A change being made any day now and released as Fx36.0.1 may resolve this issue. If you use Firefox Menu Button -> Help -> AboutFirefox each day that will check to see if the upgrade is available. There is a pref change that may be implemented by a use of ''about:config'', but it is probably best not to advise the average end user of Firefox to try to do that. -------- For those wishing to try the fix immediately [/questions/1049876#answer-699245] <blockquote> The easiest method is just to wait a few days for the Fx36.0.1 update. If you use <br /> Firefox Menu Button -> Help -> AboutFirefox <br /> each day that will check to see if the upgrade is available.<br /> <br /> The bug fix is I think merely changing prefs and so you could do that yourself. It may be safer to use a spare additional profile, or backup the file ''prefs.js'' when trying that initially, because making mistakes in about:config may break Firefox. * http://kb.mozillazine.org/Prefs.js_file * http://kb.mozillazine.org/About:config * [[Use the Profile Manager to create and remove Firefox profiles]] Just toggling the pref '''''network.dns.get-ttl''''' to '''''false''''' should fix the issue, that basically is what is done in <pre>Bug 1093983 - DNS resolver should not use 'ANY' to get cached records for TTL </pre> One of the bug fixes about to be applied in the imminent Fx36.0.1 point Release </blockquote>
John99 971 izisombululo 13138 izimpendulo
Kuphostiwe

Note Firefox 36.0.1 is now out. That may resolve some of these issues.

smow

Does 36.0.1 work ok for you now with pref network.dns.get-ttl toggled to default. (Default should now be false)

Note Firefox 36.0.1 is now out. That may resolve some of these issues. ===smow=== Does 36.0.1 work ok for you now with pref network.dns.get-ttl toggled to default. (Default should now be false)

Umnikazi wombuzo

36.0.1 does seem to have fixed the problem - which isn't a surprise as it simply did what we had already done manually - setting network.dns.get-ttl to false.

Nice to have it fixed in the build though and not have to run about:config to sort it out.

36.0.1 does seem to have fixed the problem - which isn't a surprise as it simply did what we had already done manually - setting network.dns.get-ttl to false. Nice to have it fixed in the build though and not have to run about:config to sort it out.
AG 0 izisombululo 7 izimpendulo
Kuphostiwe

setting network.dns.get-ttl to false DID NOT correct the issue on my machine. Are there others experiencing the same on WinXPsp2?

setting network.dns.get-ttl to false DID NOT correct the issue on my machine. Are there others experiencing the same on WinXPsp2?
Irish_Steve 0 izisombululo 9 izimpendulo
Kuphostiwe

I'm running XP Home SP3 here, and having upgraded to 36.0.1 and reset the TTL setting to false, I'm still seeing issues with slow or non responsive pages with Firefox, and I'm not having the same issues with Chrome, so it would seem that maybe something else is also implicated in this situation.

What I have noticed is that I can almost guarantee that if I do an obsure Google search, it won't return the first time of asking, and a web site that I've not been to since clearing the cache is also likely to fail, but a regular use site is less inclined to be a problem.

One thought, based on a somewhat suspect memory from a long time ago, there was a suggested fix for another issue that meant changing the size of the DNS cache in firefox, what is the default setting for that value, in case the cache here is either too large, or maybe now too small because of the way that the DNS is being used with the recent changes.

I'm running XP Home SP3 here, and having upgraded to 36.0.1 and reset the TTL setting to false, I'm still seeing issues with slow or non responsive pages with Firefox, and I'm not having the same issues with Chrome, so it would seem that maybe something else is also implicated in this situation. What I have noticed is that I can almost guarantee that if I do an obsure Google search, it won't return the first time of asking, and a web site that I've not been to since clearing the cache is also likely to fail, but a regular use site is less inclined to be a problem. One thought, based on a somewhat suspect memory from a long time ago, there was a suggested fix for another issue that meant changing the size of the DNS cache in firefox, what is the default setting for that value, in case the cache here is either too large, or maybe now too small because of the way that the DNS is being used with the recent changes.
John99 971 izisombululo 13138 izimpendulo
Kuphostiwe

You may have similar symptoms, but different causes of the problem. I suggest you continue with your own existing questions.

AG

Irish_Steve

You had already marked that as solved by Fx 36.0.1 /questions/1050071#answer-698850. I will remove the solved marking for you, and I suggest you post there again to confirm Fx36.0.1 does not help you.

You may have similar symptoms, but different causes of the problem. I suggest you continue with your own existing questions. ===AG=== * ''Server Not Found error only affects Firefox'' [/questions/1049876] ===Irish_Steve=== * ''Firefox 36 DNS issues, revert to 35 or go to beta to get patch?'' [/questions/1050071] You had already marked that as solved by Fx 36.0.1 [/questions/1050071#answer-698850]. I will remove the solved marking for you, and I suggest you post there again to confirm Fx36.0.1 does not help you.