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

Steps to reproduce:

Turn on ECH
Tried to open ISP's blocked website.
My ISP blocked https://medium.com, https://pastebin.com, https://pornhub.com, etc
here is my user.js: https://pastebin.com/KAU53qj8

Actual results:

Can't enter the websites

Expected results:

Websites should be loaded

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

As far as I can tell, none of those websites support ECH. And even if they did, it's not clear whether that could bypass the blocking.

(In reply to Valentin Gosu [:valentin] (he/him) from comment #3)

As far as I can tell, none of those websites support ECH. And even if they did, it's not clear whether that could bypass the blocking.

Some people bypassed the blocking successfully with ECH, with the same ISP. So i think it's Firefox problem. Even me, I've bypassed the blocking with pure profile and ECH enabled at the first try. But it no working anymore after i refresh the website. It' weird.

I don't think any of those websites support ECH. In about:networking, under DNS Lookup, what do you see if you search for those sites? If they support ECH, you should a long string under "HTTP RRs" which begins with echconfig.

(In reply to Dennis Jackson from comment #5)

I don't think any of those websites support ECH. In about:networking, under DNS Lookup, what do you see if you search for those sites? If they support ECH, you should a long string under "HTTP RRs" which begins with echconfig.

It just "NS_ERROR_UNKNOWN_HOST" but ECH works some time for me, after spaming click on google's search link. And as i said that some people use the same ISP with me has ECH work for those websites without any problem.

The attached log shows that the connection to pastebin.com doesn't use ECH, since there is no echConfig in the HTTPS record.
However, it does show that the connection is reset.

2023-05-24 15:36:45.056000 UTC - [Parent 12312: Socket Thread]: V/nsHttp nsHttpConnection::OnReadSegment [this=2d6824fc900]
2023-05-24 15:36:45.056000 UTC - [Parent 12312: Socket Thread]: D/nsSocketTransport nsSocketOutputStream::Write [this=2d682768ac0 count=444]
2023-05-24 15:36:45.056000 UTC - [Parent 12312: Socket Thread]: D/nsSocketTransport   calling PR_Write [count=444]
2023-05-24 15:36:45.056000 UTC - [Parent 12312: Socket Thread]: D/nsSocketTransport   PR_Write returned [n=-1]
2023-05-24 15:36:45.056000 UTC - [Parent 12312: Socket Thread]: D/nsSocketTransport ErrorAccordingToNSPR [in=-5961 out=804b0014]
2023-05-24 15:36:45.056000 UTC - [Parent 12312: Socket Thread]: D/nsSocketTransport nsSocketTransport::OnMsgOutputClosed [this=2d682768800 reason=804b0014]

I think there is not much we can do in this case, so I'll close this bug.