Open Bug 1965580 Opened 5 days ago Updated 5 days ago

Firefox issues with TLS HANDSHAKE

Categories

(Firefox for Android :: General, defect)

Firefox 138
defect

Tracking

()

UNCONFIRMED

People

(Reporter: frinckelballings, Unassigned)

Details

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

Steps to reproduce:

It seems vpn is causing handshake problems in SOME websites. The worst is github, recently started to hang for at leas 10 seconds before loading while firefox displays a "tls handshake" message on the down-left corner. Once it loads it one time, chances are that it will stay working for a little time before it exhibits this behavior again.

Now, I know you will send me to proton vpn (my vpn) to tell them the problem BUT this issue doesn't happen if I use chromium. I tried both, pc and android phone, on both the problem is the same. If I use chromium on the pc it works like a charm on vpn, and if I use "Browser" (default for lineage OS) it works perfectly too.

I've tried troubleshoot mode, so this also happens without any extensions. I also tried a portable FF to test and it was the same.

Librewolf has the same issue. (makes sense, its firefox after all).

IT SEEMS TO WORK WHEN I DON'T USE A VPN. But... before you tell me to not use it or to befriend bare WAN, as I've said, other browsers work just fine.

  • tried the usual stuff, "no strict mode", no extensions, clean profile (portable) + clean FF, default settings.

Actual results:

FF still hangs for 6-10 seconds before loading the webpage. Github is a constant pain.

Expected results:

Load github immediately

The Bugbug bot thinks this bug should belong to the 'Firefox for Android::General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → General
Product: Firefox → Firefox for Android

(In reply to BugBot [:suhaib / :marco/ :calixte] from comment #1)

The Bugbug bot thinks this bug should belong to the 'Firefox for Android::General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

No Mr Bot, the issue is primarily on desktop PC.

You need to log in before you can comment on or make changes to this bug.