From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: Suddenly: connection refused on 'git.ipfire.org' Date: Thu, 26 Sep 2019 20:18:02 +0200 Message-ID: In-Reply-To: <9BB5B5AC-873B-4DB8-A48A-4E77441FBE31@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0084897004913552228==" List-Id: --===============0084897004913552228== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 26.09.2019 20:04, Michael Tremer wrote: > Hi, >=20 > Did you have multiple failed password attempts? None that I know of. I sent two commits without problems, but when I tried to update a new 'suricata' branch, connection was suddenly refused... > This seems to be fail2ban blocking you again. Arne and Erik have had the sa= me issues. Thank god its not only ME. ;-)) > Are you behind carrier grade NAT? As far as I know: no. (Err, what's this?) Best, Matthias > @Peter: Could you please handle this? >=20 > -Michael >=20 >> On 26 Sep 2019, at 19:03, Matthias Fischer = wrote: >>=20 >> Hi, >>=20 >> I fear I killed something on git.ipfire.org!? ;-) >>=20 >> After the last two commits suddenly all I get is: >>=20 >> ... >> root(a)Devel: /home/matz/ipfire-2.x # git pull origin next >> ssh: connect to host git.ipfire.org port 22: Connection refused >> fatal: Could not read from remote repository. >>=20 >> Please make sure you have the correct access rights >> and the repository exists. >> ... >>=20 >> In my connections I see "SYN_SENT" but no answer anymore. >>=20 >> I have 'suricata 4.1.5' here waiting (and running on Core135), so could >> someone please take a look? ;-) >>=20 >> Thanks in advance! >>=20 >> Best, >> Matthias >=20 >=20 --===============0084897004913552228==--