From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: git.ipfire.org Network is unreachable
Date: Tue, 01 Dec 2020 16:19:41 +0000 [thread overview]
Message-ID: <4F8B0EB6-4B71-427D-A1EE-59587B967752@ipfire.org> (raw)
In-Reply-To: <07f48ad8-6248-9c17-dcf1-68a5d8ec42d2@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
Okay. Let me know if it happens again…
Sounds like you ran into fail2ban again.
> On 1 Dec 2020, at 16:19, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> On 01.12.2020 17:06, Michael Tremer wrote:
>> Hi Matthias,
>
> Hi,
>
>> Sorry, I missed to reply to this.
>>
>> Is this still an issue or did it resolve itself?
>
> No problem => self-healing. ;-)
>
> Yesterday everything was normal again.
>
> Best,
> Matthias
>
>> -Michael
>>
>>> On 29 Nov 2020, at 13:29, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>
>>> Hi,
>>>
>>> again, I got some problems pushing/pulling to/from GIT:
>>>
>>> ...
>>> root(a)Devel64: /git/ipfire-2.x # git push mfischer next
>>> ssh: connect to host git.ipfire.org port 22: Network is unreachable
>>> fatal: Could not read from remote repository.
>>>
>>> Please make sure you have the correct access rights
>>> and the repository exists.
>>> ...
>>>
>>> I payed my bills! I promise! The check is in the mail! Really! ;-)
>>>
>>> Can we be friends again? Or have I done something wrong?
>>>
>>> Best,
>>> Matthias
>>
>
next prev parent reply other threads:[~2020-12-01 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 13:29 Matthias Fischer
2020-12-01 16:06 ` Michael Tremer
2020-12-01 16:19 ` Matthias Fischer
2020-12-01 16:19 ` Michael Tremer [this message]
2020-12-01 22:04 ` Peter Müller
2020-12-02 15:29 ` Michael Tremer
2020-12-02 17:16 ` Matthias Fischer
2020-12-03 7:41 ` Arne Fitzenreiter
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=4F8B0EB6-4B71-427D-A1EE-59587B967752@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