1954276 - Secure Connection Failed to hg.mozilla.org

Status: RESOLVED FIXED

(Developer Services :: Mercurial: hg.mozilla.org, defect)

Description

[Ian Neal]

Since yesterday I have been unable to access hg.mozilla.org from my broadband provider (Virgin Media)
Firefox produces:
Secure Connection Failed
An error occurred during a connection to hg.mozilla.org. PR_END_OF_FILE_ERROR
Error code: PR_END_OF_FILE_ERROR

Chrome produces a less useful:
This site can’t be reached
hg.mozilla.org unexpectedly closed the connection.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_CLOSED

I can provide the IP block information if required.

Comment 1

[Richard Marti (:Paenglab)]

And I get with HG abort: error: [SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1006)

Comment 2

[Wayne Mery (:wsmwk)]

For me on Mac, it fails only in chrome, Firefox 136 and safari are fine

Comment 3

[Ian Neal]

I've tested on Linux (Fedora) and Android with Firefox and Chrome.
I've also now tested on Mac using Firefox and Safari.
All fail for me.

Comment 4

[Connor Sheehan [:sheehan]]

hg.mozilla.org was experiencing a DDoS yesterday, so we added some bans of large IP blocks to try and stabilize the service. I removed a few of the larger blocks just now. Please try accessing the site again, if you are still blocked and could provide your IP address space I can see if I missed any of the ranges. Sorry for the inconvenience!

Comment 5

[Ian Neal]

It's working for me now, thanks.

Comment 6

[Matt A. Tobin [:nsITobin]]

Seems some fallout from mitigating the mentioned DDOS is some web clients can no longer connect to hg.m.o.

Edge and other chromium browsers are indicating:

Hmmm… can't reach this page
It looks like the webpage at https://hg.mozilla.org/ might be having issues, or it may have moved permanently to a new web address.
ERR_HTTP2_PROTOCOL_ERROR

While, SeaMonkey 2.53.x, and anything UXP-based can connect.

Comment 7

[Richard Marti (:Paenglab)]

It's working for me too again, thanks.

Comment 8

[Connor Sheehan [:sheehan]]

(In reply to Matt A. Tobin [:nsITobin] from comment #6)

Seems some fallout from mitigating the mentioned DDOS is some web clients can no longer connect to hg.m.o.

Edge and other chromium browsers are indicating:

Hmmm… can't reach this page
It looks like the webpage at https://hg.mozilla.org/ might be having issues, or it may have moved permanently to a new web address.
ERR_HTTP2_PROTOCOL_ERROR

While, SeaMonkey 2.53.x, and anything UXP-based can connect.

We banned a few User-Agent strings as well, I have just rolled those changes back. Please try again and let me know if you are still unable to connect.

Edit: after rolling the UA rules back, the DDoS immediately started again. I have re-instated the rules.

Comment 10

[Matt A. Tobin [:nsITobin]]

No change on Edge.
Rocky 8 Userspace with a 6.10.x custom built kernel.

Microsoft Edge	132.0.2957.127 (Official build) (64-bit) 
Revision	cbce079b96b28be9fa4f42e62594c7635966a2af
Chromium version	132.0.6834.111
Operating system	Linux
JavaScript	V8 13.2.28.9
User agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36 Edg/132.0.0.0

Anything based on .. well "Late Model" XUL Platforms (style glitches not withstanding) though current Firefox versions seems to connect fine however.

EDIT-- Ah ok I skimmed over the edit that the mitigation are back in place. Hmm.. Well, past several months, DDOS attacks on Mozilla fork repo forges has been something happening out in Moonville as well as crippling my own ineffectual attempts at much. I wonder if it is related.

Granted hg is rather heavy to host and serve so it may be easier for a smaller force to disrupt vs a lighter modern forge like Gitea or baselevel Gogs which some run on smaller servers with the same level of attack. Has mozilla gotten any comments from anyone taking credit? Perhaps someone whom has a long running almost joke-level dislike of a certain Texas elected official that has been terrorizing SeaMonkey, Pale Moon, and my self (a tragedy, I'm sure) for a while now with spam and attacks on repositories and interaction venues?

Comment 11

[Julien Cristau [:jcristau] (back August 18)]

This should be working again now.