1847804 - "The connection has timed out" error on licensebureauvancouverwa.com

Status: RESOLVED WORKSFORME

(Web Compatibility :: Site Reports, defect, P3)

Description

[Ksenia Berezina [:ksenia]]

We've received a report in https://github.com/webcompat/web-bugs/issues/125218 where a user is unable to load the site and eventually "The connection has timed out" error is displayed.

To reproduce visit https://www.licensebureauvancouverwa.com/services2/ in Firefox Nightly (118.0a1 (2023-08-07)) on MacOS or Android.

From mozregression:

17:04.04 INFO: Last good revision: 0846d258566e1b31da040b6cd5e4ff5b8a20974d
17:04.04 INFO: First bad revision: 70dec260867a04a285867e0586434475917f480d
17:04.04 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=0846d258566e1b31da040b6cd5e4ff5b8a20974d&tochange=70dec260867a04a285867e0586434475917f480d

Comment 1

[Ksenia Berezina [:ksenia]]

Hi Dennis, wonder if you could take a look at this, please?

Comment 3

[Martin Thomson [:mt:]]

I took a look and there is no HTTPS record in place. The problem seems to be with their TLS configuration, which stalls in the presence of the ECH extension. Setting security.tls.ech.grease_probability to 0 makes the connection work.

Comment 4

[Dennis Jackson]

I had a look as well. This is similar to the other bug in that its a non-compliant TLS server which only supports TLS 1.2. The site also breaks with Chrome and its not ECH-specific as using a different extension id also triggers it. As this server times out rather than causes an error the user experience is a bit worse and there's no way for us to fall back as we can't distinguish the lack of reply from a server that's simply unavailable.

Given the site is very local and the fact Chrome is also impacted I'm not concerned by this. But I'll reach out to the site admin anyway to see if they can figure out what the root cause is... their fingerprint suggests they're using the latest version of Microsoft IIS (10.0), but I've tested with other sites using IIS 10.0 and they work fine in Firefox.

Comment 5

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

The severity field is not set for this bug.
:beurdouche, could you have a look please?

For more information, please visit BugBot documentation.

Comment 6

[Dennis Jackson]

The site operator has now resolved their misconfiguration.