From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Suddenly: connection refused on 'git.ipfire.org'
Date: Thu, 26 Sep 2019 19:04:26 +0100 [thread overview]
Message-ID: <9BB5B5AC-873B-4DB8-A48A-4E77441FBE31@ipfire.org> (raw)
In-Reply-To: <d6ff22ea-c3d8-8010-2a59-0df5b400bdfd@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
Hi,
Did you have multiple failed password attempts?
This seems to be fail2ban blocking you again. Arne and Erik have had the same issues.
Are you behind carrier grade NAT?
@Peter: Could you please handle this?
-Michael
> On 26 Sep 2019, at 19:03, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> I fear I killed something on git.ipfire.org!? ;-)
>
> After the last two commits suddenly all I get is:
>
> ...
> 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.
>
> Please make sure you have the correct access rights
> and the repository exists.
> ...
>
> In my connections I see "SYN_SENT" but no answer anymore.
>
> I have 'suricata 4.1.5' here waiting (and running on Core135), so could
> someone please take a look? ;-)
>
> Thanks in advance!
>
> Best,
> Matthias
next prev parent reply other threads:[~2019-09-26 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 18:03 Matthias Fischer
2019-09-26 18:04 ` Michael Tremer [this message]
2019-09-26 18:18 ` Matthias Fischer
2019-09-27 16:10 ` Matthias Fischer
2019-09-28 16:33 ` Michael Tremer
2019-10-05 7:21 ` Matthias Fischer
2019-10-05 10:07 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9BB5B5AC-873B-4DB8-A48A-4E77441FBE31@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox