[Pkg-raspi-maintainers] Connection refused on port 22

Michael Stapelberg stapelberg at debian.org
Fri Jan 5 11:40:09 UTC 2018


That points towards a boot issue.

The current image doesn’t show console messages on HDMI yet (the next one
will). Add console=tty0 in front of console=ttyAMA0 in cmdline.txt on the
first partition to enable console messages.

On Fri, Jan 5, 2018 at 12:28 PM, YaguraStation <debian at honigwachs.de> wrote:

> Will do and report back, thanks. Funny thing about HDMI: Except for the
> brief rainbow coloured dash screen at the beginning, HDMI remains black
> afterwards.
>
> On 5 January 2018 at 13:22, Michael Stapelberg <stapelberg at debian.org>
> wrote:
>
>> The firewall rule https://github.com/Debian/raspi3-image-spec/blob/28566d
>> 7f29046e6cc958121aab0ffec9572bf1cb/rules.v4#L9 should permit access.
>>
>> Can you connect either a serial console to the pin header, or a keyboard
>> and HDMI monitor? Afterwards, log in locally and provide the output of
>> “iptables-save” please.
>>
>> Perhaps it’s not a firewall issue, but rather sshd not running for some
>> reason?
>>
>> On Fri, Jan 5, 2018 at 12:19 PM, YaguraStation <debian at honigwachs.de>
>> wrote:
>>
>>> ```$ ssh -v root at rpi3
>>> OpenSSH_7.6p1 Debian-2, OpenSSL 1.0.2n  7 Dec 2017
>>> debug1: Reading configuration data /etc/ssh/ssh_config
>>> debug1: /etc/ssh/ssh_config line 19: Applying options for *
>>> debug1: Connecting to rpi3 [192.168.86.160] port 22.
>>> debug1: connect to address 192.168.86.160 port 22: Connection refused
>>> ssh: connect to host rpi3 port 22: Connection refused```
>>>
>>> I'm getting the address from the local router/dhcp:
>>> ```$ dig rpi3 +short
>>> 192.168.86.160```
>>>
>>> If this is *not* a known issue, let me rather try and see if I kind find
>>> out more during the weekend and I'll get back to you.
>>>
>>> On 5 January 2018 at 13:09, Michael Stapelberg <stapelberg at debian.org>
>>> wrote:
>>>
>>>> Thanks for reaching out. This is not a known issue.
>>>>
>>>> Could you please provide the output of the ssh command you’re using,
>>>> ideally with -v for verbose output?
>>>>
>>>> How are you obtaining the Raspberry Pi’s IP address? Which IP
>>>> address/subnet is it?
>>>>
>>>> On Fri, Jan 5, 2018 at 11:54 AM, YaguraStation <debian at honigwachs.de>
>>>> wrote:
>>>>
>>>>> Following the wiki [1] of posting questions/feedback to this list and
>>>>> hoping this is not too much of a trivial one:
>>>>>
>>>>> When trying to connect from the same subnet after first time boot
>>>>> using 2016-11-24-raspberry-pi-3-stretch-PREVIEW.img, I receive
>>>>> `Connection refused` when trying to ssh into rpi3. Is this a known issue
>>>>> and how best to go about troubleshooting it?
>>>>>
>>>>> [1] https://wiki.debian.org/RaspberryPi3
>>>>>
>>>>> Thanks, Reuben
>>>>>
>>>>> _______________________________________________
>>>>> Pkg-raspi-maintainers mailing list
>>>>> Pkg-raspi-maintainers at lists.alioth.debian.org
>>>>> https://lists.alioth.debian.org/mailman/listinfo/pkg-raspi-maintainers
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Best regards,
>>>> Michael
>>>>
>>>
>>>
>>
>>
>> --
>> Best regards,
>> Michael
>>
>
>
> _______________________________________________
> Pkg-raspi-maintainers mailing list
> Pkg-raspi-maintainers at lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/pkg-raspi-maintainers
>
>


-- 
Best regards,
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-raspi-maintainers/attachments/20180105/0a124971/attachment.html>


More information about the Pkg-raspi-maintainers mailing list