On 26.09.2019 20:04, Michael Tremer wrote:
> Hi,
> 
> 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 same 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?
> 
> -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
> 
>