1718399 - Can't login to google account on Firefox 89

Status: RESOLVED WORKSFORME

(Core :: Networking: HTTP, defect)

Description

[Andrei Romanenko]

Attachment: firefox-89-google-account-issue.png

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

Steps to reproduce:

Open Firefox 89 or Firefox 90 beta on Windows 10.
Try to login to google account to access any of google products (Gmail, YouTube, etc.).
Enter login, click 'Next'

Actual results:

After some time (5-10 seconds) error 'Something went wrong' appears

It works fine in Chrome/Edge, in Firefox 86 and in Firefox nightly.
Creating new profile/disabling addons/disabling enhanced tracking protection/allowing all cookes didn't help

Expected results:

An input to enter google account password should appear

Comment 1

[Andrei Romanenko]

Attachment: HTTP Logs

Comment 2

[Andrei Romanenko]

Looks like the solution is found: in attached HTTP logs you can see lines which say about HTTP 3 connection error.
If in about:config option 'network.http.http3.enabled' set to 'false' the problem is gone.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Toolkit::Add-ons Manager' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 4

[Peter Magyari (Desktop QA)]

Hi Andei,

I wasn't able to reproduce the issue on Firefox 89, Firefox Beta 90b or Firefox Nightly 91.0a1

Could you check if the issue also happens in troubleshoot mode? Here is a link that can help you with that:
https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems#w_start-firefox-in-troubleshoot-mode

If the issue occurs in troubleshoot mode as well, make a new profile and check again (you will not lose your current profile)
https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles#w_start-the-profile-manager-when-firefox-is-closed

Thank you!

Comment 5

[Andrei Romanenko]

(In reply to Peter from comment #4)

Hi Andei,

I wasn't able to reproduce the issue on Firefox 89, Firefox Beta 90b or Firefox Nightly 91.0a1

Could you check if the issue also happens in troubleshoot mode? Here is a link that can help you with that:
https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems#w_start-firefox-in-troubleshoot-mode

If the issue occurs in troubleshoot mode as well, make a new profile and check again (you will not lose your current profile)
https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles#w_start-the-profile-manager-when-firefox-is-closed

Thank you!

Hi Peter,
Unfortunately troubleshoot mode and new profile didn't help. On Firefox nightly everything works fine. The problem appears only on Firefox 89, Firefox 90 beta. Maybe this bug is hardware related, because option 'network.http.http3.enabled' is set to 'true' by default on Firefox 89/90 and it causes this bug for me. So you would for sure noticed this problem before if it was common for everyone.
I also tried to launch firefox 89/90 in Windows sandbox, to exclude inteference from some other software but the problem exists also there.
Will it help if I attach also logs of connecting to accounts.google.com with option 'network.http.http3.enabled' set to 'false'? In that case everything works for me, but maybe you can compare two logs and find what exactly causes this bug.
If you need some info from my side I will be glad to help

Comment 6

[Valentin Gosu [:valentin] (he/him)]

Hi Andrei,

Could you record some HTTP logs using these instructions?
https://firefox-source-docs.mozilla.org/networking/http/logging.html

Thanks!

Comment 7

[Andrei Romanenko]

Attachment: HTTP Log in case network.http.http3.enabled is set to 'false'

Comment 8

[Andrei Romanenko]

Attachment: HTTP Log in case network.http.http3.enabled is set to 'true'

Comment 9

[Andrei Romanenko]

(In reply to Valentin Gosu [:valentin] (he/him) [vacation until Aug 1st] from comment #6)

Hi Andrei,

Could you record some HTTP logs using these instructions?
https://firefox-source-docs.mozilla.org/networking/http/logging.html

Thanks!

Hello Valentin, there were already HTTP logs attached, but in the attachment to this comment you can find a fresh ones.
I added two log files: one for the case when 'network.http.http3.enabled' option is set to false, in this case everything works fine.
The second log file is for the case when 'network.http.http3.enabled' option is set to true (default value), in this case this bug happens for me

Comment 10

[Dragana Damjanovic [:dragana]]

What I see from the log is that HTTP/3 connection has been already created and connected (the log does not contain the beginning of the connection). The request to accounts.google.com is added to the connection as stream 0x4, that means that there was already one request performed on the connection(the first request is not in the log).
After this Firefox receives only one packet on the connection and then the connection is closed

The request is sent at:
2021-07-07 16:10:42.736000 UTC - [Parent 3256: Socket Thread]: V/nsHttp Http3Session::TryActivating [stream=2a82ff02c10, this=2a83a973800 state=2]
2021-07-07 16:10:42.736000 UTC - [Parent 3256: Socket Thread]: V/nsHttp Http3Session::TryActivating streamId=0x4 for stream=2a82ff02c10 [this=2a83a973800].
2021-07-07 16:10:42.737000 UTC - [Parent 3256: Socket Thread]: E/nsHttp nsHttpTransaction::OnSocketStatus [this=2a837ecd000 status=804b0005 progress=1047]
....

Firefox receives a packet from the server at:
2021-07-07 16:10:42.745000 UTC - [Parent 3256: Socket Thread]: V/nsHttp Http3Session::ProcessInput writer=2a837ce80e0 [this=2a83a973800 state=2]
2021-07-07 16:10:42.745000 UTC - [Parent 3256: Socket Thread]: V/nsHttp Http3Session::ProcessInput received=28
2021-07-07 16:10:42.745000 UTC - [Parent 3256: Socket Thread]: V/nsHttp Http3Session::ProcessEvents [this=2a83a973800]
2021-07-07 16:10:42.745000 UTC - [Parent 3256: Socket Thread]: V/nsHttp Http3Session::ProcessOutput reader=2a837ce80e0, [this=2a83a973800]
2021-07-07 16:10:42.745000 UTC - [Parent 3256: Socket Thread]: V/nsHttp Http3Session::SetupTimer to 5ms [this=2a83a973800].
...

Something in the child process closes the request:
2021-07-07 16:11:12.738000 UTC - [Parent 3256: Main Thread]: D/nsHttp HttpChannelParent::RecvCancel [this=2a838f2a5c0]
2021-07-07 16:11:12.738000 UTC - [Parent 3256: Main Thread]: V/nsHttp nsHttpChannel::Cancel [this=2a834c4e000 status=804b0002]
2021-07-07 16:11:12.738000 UTC - [Parent 3256: Main Thread]: V/nsHttp nsHttpConnectionMgr::CancelTransaction [trans=2a837ecd010 reason=804b0002]
...
The HTTP/3 connections times out:
2021-07-07 16:11:12.752000 UTC - [Parent 3256: Socket Thread]: V/nsHttp HttpConnectionUDP::OnQuicTimeout [this=2a837ce80e0]
2021-07-07 16:11:12.752000 UTC - [Parent 3256: Socket Thread]: V/nsHttp Http3Session::ProcessOutput reader=2a837ce80e0, [this=2a83a973800]
2021-07-07 16:11:12.752000 UTC - [Parent 3256: Socket Thread]: V/nsHttp Http3Session::ProcessEvents [this=2a83a973800]
2021-07-07 16:11:12.752000 UTC - [Parent 3256: Socket Thread]: V/nsHttp Http3Session::ProcessEvents - ConnectionClosed
2021-07-07 16:11:12.752000 UTC - [Parent 3256: Socket Thread]: V/nsHttp Http3Session::ProcessEvents - ConnectionClosed error=804b000e

This looks like as at one point Firefox stops receiving packets from the server.

Comment 11

[Dragana Damjanovic [:dragana]]

I do not see from the log how long the connection was idle before we have sent the request.

I am not sure what we can do here, A connection using HTTP/3 is obviously working fine, but at some point Firefox sops receiving packets.

Can you tell us something about your network setup? Do you have any firewall?

Comment 12

[Andrei Romanenko]

Hello, Dragana

Network setup in my case is simple: laptop connected to ISP through L3 router using Wi-Fi.
There is no additional firewall exept for default one that comes with Windows OS. I checked Windows firewall and all connections are allowed for firefox.exe, also I compared rules for Firefox and for Chrome and they look the same to me.

If you are sure that there is a problem on my side (hardware/network, etc.), we can safely close this bug because I found a solution that reliably works for me (set network.http.http3.enabled to 'false'). But it seems strange that this bug happens only on several versions of Firefox and it doesn't happen on the same machine with the same network but with different version of Firefox or with another browser (Chrome/Edge)

Comment 13

[Kershaw Chang [:kershaw]]

Hi Andrei,

Since you said that this worked with previous firefox versions, could you try to use mozregression to find out the problem?
Please also make sure http3 is enabled by adding --pref network.http.http3.enabled:true. Thanks.

Comment 14

[Andrei Romanenko]

Hello, I am not able to reproduce this problem anymore on Firefox version 89/90, that were previously affected by this bug.
Probably the problem is gone after some update on the OS side. We can safely close this bug, I guess

Comment 15

[Valentin Gosu [:valentin] (he/him)]

Thanks for checking, and for reporting this bug!