On 2019-01-20, Vagrant Cascadian wrote:
> On 2019-01-20, Holger Levsen wrote:
>> On Sun, Jan 20, 2019 at 11:13:23AM +0100, Mattia Rizzolo wrote:
>>> I tried to ssh in, but it seems at least my key was not deployed, so I
>>> can't do the deploy.
>>
>> same here.
>
> Are you both using port 2254 to
On 2019-01-20, Holger Levsen wrote:
> On Sun, Jan 20, 2019 at 11:13:23AM +0100, Mattia Rizzolo wrote:
>> I tried to ssh in, but it seems at least my key was not deployed, so I
>> can't do the deploy.
>
> same here.
Are you both using port 2254 to connect to it?
The keys are the same keys
On Sun, Jan 20, 2019 at 11:13:23AM +0100, Mattia Rizzolo wrote:
> I tried to ssh in, but it seems at least my key was not deployed, so I
> can't do the deploy.
same here.
--
tschüß,
Holger
---
On Sat, Jan 19, 2019 at 09:13:19PM -0800, Vagrant Cascadian wrote:
> jtx1c-armhf-rb.debian.net had a disk failure, and thus needed to be
> re-installed.
>
> It has now been reinstalled, awaiting configuration.
I tried to ssh in, but it seems at least my key was not deployed, so I
can't do the
Package: jenkins.debian.org
Severity: normal
jtx1c-armhf-rb.debian.net had a disk failure, and thus needed to be
re-installed.
It has now been reinstalled, awaiting configuration.
New ssh keys:
256 SHA256:V8CIP3rzxgTHDjzhhVFPbTcfB+hHwppvcjbhQEfFTGQ root@jtx1c (ECDSA)
256
5 matches
Mail list logo
