Hi,
I fear I killed something on git.ipfire.org!? ;-)
After the last two commits suddenly all I get is:
... root@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
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@ipfire.org wrote:
Hi,
I fear I killed something on git.ipfire.org!? ;-)
After the last two commits suddenly all I get is:
... root@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
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@ipfire.org wrote:
Hi,
I fear I killed something on git.ipfire.org!? ;-)
After the last two commits suddenly all I get is:
... root@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
Hi,
I suppose that nobody did anything and the blocking rule has been removed automatically after a while.
-Michael
On 27 Sep 2019, at 17:10, Matthias Fischer matthias.fischer@ipfire.org wrote:
On 26.09.2019 20:04, Michael Tremer wrote:
@Peter: Could you please handle this?
Works.
Thanks!
Hi,
On 28.09.2019 18:33, Michael Tremer wrote:
... I suppose that nobody did anything and the blocking rule has been removed automatically after a while.
Today it happened again: sending to 'patchwork' ("git send-email ...") was ok, but in the next moment 'git' ("git push mfischer ...") doesn't like me anymore:
***SNIP*** Password for 'smtp://mfischer@submissions.ipfire.org:465': OK. Log says: Server: submissions.ipfire.org MAIL FROM:matthias.fischer@ipfire.org RCPT TO:development@lists.ipfire.org From: Matthias Fischer matthias.fischer@ipfire.org To: development@lists.ipfire.org Subject: [PATCH] unbound: Update to 1.9.4 Date: Sat, 5 Oct 2019 09:09:29 +0200 Message-Id: 20191005070929.3484-1-matthias.fischer@ipfire.org X-Mailer: git-send-email 2.18.0
Result: 250 root@Devel: /home/matz/ipfire-2.x # git push mfischer unbound mfischer@git.ipfire.org's password:
[...long pause...]
Connection to git.ipfire.org closed by remote host. fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists. root@Devel: /home/matz/ipfire-2.x # ***SNAP***
Could someone please tell me how long "after a while" is? ;-)
Thanks in advance.
Best, Matthias
Hi,
I think this is an hour right now.
@Peter: Can you find a solution for this?
Best, -Michael
On 5 Oct 2019, at 08:21, Matthias Fischer matthias.fischer@ipfire.org wrote:
Hi,
On 28.09.2019 18:33, Michael Tremer wrote:
... I suppose that nobody did anything and the blocking rule has been removed automatically after a while.
Today it happened again: sending to 'patchwork' ("git send-email ...") was ok, but in the next moment 'git' ("git push mfischer ...") doesn't like me anymore:
***SNIP*** Password for 'smtp://mfischer@submissions.ipfire.org:465': OK. Log says: Server: submissions.ipfire.org MAIL FROM:matthias.fischer@ipfire.org RCPT TO:development@lists.ipfire.org From: Matthias Fischer matthias.fischer@ipfire.org To: development@lists.ipfire.org Subject: [PATCH] unbound: Update to 1.9.4 Date: Sat, 5 Oct 2019 09:09:29 +0200 Message-Id: 20191005070929.3484-1-matthias.fischer@ipfire.org X-Mailer: git-send-email 2.18.0
Result: 250 root@Devel: /home/matz/ipfire-2.x # git push mfischer unbound mfischer@git.ipfire.org's password:
[...long pause...]
Connection to git.ipfire.org closed by remote host. fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists. root@Devel: /home/matz/ipfire-2.x # ***SNAP***
Could someone please tell me how long "after a while" is? ;-)
Thanks in advance.
Best, Matthias