Closed Bug 1676337 Opened 5 years ago Closed 5 years ago

[CentOS Linux VERSION 7] Problem loading page since version FirefoxDevEdition 83b10

Categories

(Core :: Widget: Gtk, defect)

Product:
Core
Component:
Widget: Gtk
Version:
Firefox 83
Platform:
Desktop
Linux
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1677806

People

(Reporter: juvroju, Unassigned)

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0

Steps to reproduce:

With FirefoxDevEdition 83b10 (and probably b9, b8 and b7), some local network sites (in http and not https) does not load.

Actual results:

On a colleague PC, with an older version : FirefoxDevEdition 83b5 (before autoupdate), no problem, the local network site opens..

Then we make the auto update to b10, and the site does not load : we have the page "Prolem loading page - Unable to connect".

Expected results:

The we site should open. It still works in Firefox 82.
And I tried "reset firefox, clear cache, etc", but this does not solve the problem.
And no information in console or "F12-network tab"...

QA Whiteboard: [qa-regression-triage]

Hey Julien., since this is on an internal site, could you help us find a regression range?

https://mozilla.github.io/mozregression/install.html

Flags: needinfo?(juvroju)

Hi Julien,
I tried to reproduce this on my end with localhost and a sample website downloaded (from here: https://www.html5webtemplates.co.uk/templates/) and the latest Firefox DevEdition (83.0b10 (64-bit)) does load it on my side on Windows 10.

Is there anything special about the local network sites you are trying to open? Is there any way you could share them?
Please note that I created the localhost using Python -m http.server, not sure if this is the right way to reproduce your environment but worth mentioning here in case you disagree with this.

Edit: Failed to notice this needs a site shared on the local network, not localhost. Used XAMP to serve the site on local network and managed to access it from 2 different devices (Windows 10 - LAN and macOS 10.15 - WiFI). So the questions still stand.

Component: Untriaged → Networking
Product: Firefox → Core

It would also be of great help if you could use Mozregression tool mentioned by Jim in Comment 1 to try to find out what regressed this.
Unfortunately, mozregression doesn't support devEdition at the moment but please do try it out with the Beta builds. Have the following set up when you do the setup for the bisection to work on Beta builds:
Build Type: shippable
Repository: mozilla-beta

Also, it would be nice to know is this is reproducible on other Firefox builds, such as Firefox Nightly, Beta and Release. Maybe it would be worth starting with this step first and proceed with mozregression further on the Beta builds.

Hello,

Release is ok : problem not present (already mentioned ; as in version DevEdition83beta5 : problem not present)
Beta : the installer exploded my profile. Annoyed & Disturbed, i can't remember the result. I removed this installation that cannot be "side by side" of the release
Nightly (84a1 - 11.11) : problem is present

Impossible to "publish" the web site.
Sorry, not fan to install your mozregression ; this is a professional PC.

Flags: needinfo?(juvroju)

Hello,

Same problem here : unable to join one of the hosts on the local network since update to 83b10.
Target host is an old Ubuntu 14.04.5 LTS with an old Tomcat 7.
Problem not present targeting other local network host, like the "upgraded" version of the problematic host which is an Ubuntu 18.04.3 LTS with Tomcat 8.

Access was done by targeting the port of the Tomcat server.

Access to host was fine before the update on DevEdition and still works on Firefox classic 82.0.3.

Hi kgauvain,
Is there any chance you could run Mozregression and see what exactly caused this to not work anymore? This is hard to investigate further as it is now. Updating flags based on Comment 4.
Thanks Julien for trying out the other Firefox versions!

status-firefox82: --- → unaffected
status-firefox84: --- → affected

For information, after kgauvain message, I made an other test, because indeed, when I opened the bug, the target machine involved is a linux machine.
But I just tried with a "windows server 2003" target machine, still in HTTP and not HTTPS (destination is an old Tomcat 7) : and the problem is also present with that target machine under windows..

I've also discoverd the bug on a Windows 7 target in HTTP.
I'll run Mozregression after work hours.

After further research, I won't run Mozregression, even Firefox detect it as a malware and I don't want to take any risk on a professionnal computer.

Configured Apache Tomcat 7 (tried Tomcat 10 as well) on Windows 10 x64 and accessed the site using the local network IP address on a macOS device connected to the same network and it worked on all latest Firefox versions.
Although I tried this specifically with Tomcat 7 version and couldn't repro on Windows 10, seems like that is the only common path between Comment 5 and Comment 7. So wondering if updating to the latest Tomcat 10 version or even Tomcat 8 (looking at what Guavain mentioned) would solve this issue. Julien, could you check that out?

As for the mozregression issue, unfortunately that is a known Bug 1647533 which I am sorry you had to run into.

Guavain, could you confirm if it works ok on all the latest Firefox versions with Tomcat 8?

Flags: needinfo?(juvroju)
Flags: needinfo?(kgauvain)

I confirm it works with a Tomcat 8 target on :

  • Nightly 84.0a1
  • Developer 83.0b10
  • Classic 82.0.3
Flags: needinfo?(kgauvain)

Thank you Gauvain! Looking forward to see if Julien has any positive outcome by using Tomcat 8 as well.

Hello Timea,
sorry, but the problem is present with the following target : web site running on a Apache Tomcat/9.0.30, running with jdk-11.0.5, on a CentOS Linux VERSION 7.
(Calling machine is : Windows 10 - version 2004 ; Firefox Dev Edition & Firefox Nightly)

Regards,
Julien.
PS : I still search for a Tomcat 8 on the entreprise network ; but I may not find one.

Flags: needinfo?(juvroju)

Ok, I found a "Apache Tomcat/8.5.39" !
Still on a CentOS Linux VERSION 7.
Problem is also present with that tomcat version.

Thanks Julien, moving this over to Linux specific bugs component in hope it can be handled here given that it has different behavior for different OSes. Please note that Gauvain already tried out Ubuntu 18.04.3 LTS with Tomcat 8 which worked fine.

Component: Networking → Widget: Gtk
OS: Unspecified → Linux
Hardware: Unspecified → Desktop
Summary: Problem loading page since version FirefoxDevEdition 83b10 → [CentOS Linux VERSION 7] Problem loading page since version FirefoxDevEdition 83b10

(In reply to Timea Cernea [:tbabos] from comment #15)

Hello Timea,
See "comment 7" : this occurs also with a "windows server 2003" target machine.
And "comment 8" : also with a "Windows 7 target in HTTP".
=> I 'm pretty sure that this is not specific to a "linux target".

It 's probably "not my business" to say that, but maybe it would be easier to find the the problem in examining what has changed between firefoxDevEdition83b5 and 83b10 ; I suppose that we are not talking about "hundreds" of lines of code, are we ?
(and on the other hand, of course, if you can't reproduce the problem, I understand the complexity of finding that problem ; and fixing ; and testing the fix).

Hi guys,

With the versions published this morning/yesterday, I can not reproduce the problem !!!

Everything is fine in :

  • Firefox release 83.0
  • Firefox Dev Edition 84.0b2
  • Firefox Nightly 85.0a1-2020.11.17
  • Firefox ESR 78.4.1 (before update)
  • Firefox ESR 78.5

And if nobody has changed anything compared to "2 days ago", this may be the IT guys here that have "patched" the network or the VPN ; I don't know, I did not asked.

@Gauvain : is it the same for you ? Do you still have the problem ?
If there is no problem in Gauvain 's config, this ticket can be closed...

Thanks, and sorry for the "disturbance" of that "cannot reproduce" ticket..
Julien.

Sending NI? to Gauvain to confirm as well. Thanks Julien for insisting and reporting back on this. The best I could do is to try to reproduce and follow up with reporters, as for the code debugging that is not something I can be helpful with.

Flags: needinfo?(kgauvain)

Hello,

I've updated Dev Edition and Nightly and still not working for me, be it targeting a Tomcat 7 on our Ubuntu host or targeting an Apache on a Win7 host. I'll ask our guys in charge of the network in case they broke something without knowing but it seems unlikely to me.

So for me :

  • Firefox release 82.0.3 => FIne but didn't dare to update to last version, it's my last working Firefox for those targets
  • Firefox Dev Edition 84.0b2 => Problem still there
  • Firefox Nightly 85.0a1-2020.11.17 => Same

I'll check the next updates on Dev and Nightly and post any update here.

Flags: needinfo?(kgauvain)

hi valentin, there were a couple of necko patches landing between b5 and b10 (https://bugzilla.mozilla.org/buglist.cgi?bug_id=1672528,1669355,1669780,1663571) . could you take a look if anything is standing out there that might be related to this problem here and if yes perhaps set a priority/severity?

Flags: needinfo?(valentin.gosu)

Workarounds:

  • use the complete name of the host: host.local or host.dnssuffix
  • For netbios names, you can append a dot at the end: host.
  • If all else fails, you can set the network.dns.dns_query_single_label pref to false in about:config (not recommended. may leak single word searches to the local network).
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Flags: needinfo?(valentin.gosu)
Resolution: --- → DUPLICATE

The workaround with the end dot works for me, thanks !

Removing regression-windows wanted since this is a duplicate of Bug 1677806.

Keywords: regressionwindow-wanted
You need to log in before you can comment on or make changes to this bug.