SSH to Raspberry Pi with Hostname Connection Refused

[jembe]

We have chromebooks at our school and would like to be able to operate Raspberry Pi headless via ssh and vnc.

The raspberry pi is running avahi-daemon.

SSH works if you use the ip address of the Pi, but not if you use the hostname. We want to be able to easily ssh to the hostname without finding the ip address. I have been able to get the desired functionality from a Mac.

ssh pi@ipaddress:22

works perfectly

ssh p...@raspberrypi.local:22

Connection refused, NaCl plugin exited with status code 255

Is this a limitation of Chrome? Or is this a network issue, or an issue with the Pi set up?

[Mike Frysinger]

this is most likely a network setup.  the hostname has to be known by the DNS server on your network, and often that has to be integrated with your DHCP server setup.  the system running Chrome has no way of knowing hostname<->IP mappings itself.

unfortunately, this question has nothing to do with SecureShell, so you'll want to find a general networking group to get help from.  maybe one of the rasperrypi forums can help.

-mike

The contents of this email, and any attachments, are the property of the Sandwich Public School District, and are subject to the Public Records law, M.G.L. c> 66, Sec. 10.

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/c8b92472-a70b-4736-9398-1823fa615daf%40chromium.org.

[gregor...@gmail.com]

Worked for me, with just ssh pi@raspberrypi:22  . 

Other possiblity,   In the raspberry pi, there is also a configuration for setting the hostname.  By default, it did not have the ".local"

[Robert Ginda]

Whether or not this works will depend on your network setup.  If you're running an DNS server which knows the IP to hostname mapping, or if your client machine merges mDNS with regular DNS and your rpi is broadcasting mDNS records, it'll work.  Otherwise you'll need to use the IP address.

--

You received this message because you are subscribed to the Google Groups "chromium-hterm" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/0a5873cd-2d9e-446a-a0cd-4cc31e714c6a%40chromium.org.

[xerc...@gmail.com]

WOW

[Xerxes Xarya]

really me?

--
You received this message because you are subscribed to a topic in the Google Groups "chromium-hterm" group.
To unsubscribe from this topic, visit https://groups.google.com/a/chromium.org/d/topic/chromium-hterm/mhvarATK9pg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromium-hterm+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/4ef6275d-024b-487d-bb81-c7bacd8d0a43%40chromium.org.

[coyo...@gmail.com]

Nope, not you.  I have this issue trying to ssh from a Chromebook to IP addresses for Raspberry Pi 3 and Zero W using the default onboard wifi chips when using Chrome Secure Shell.  Same machines are completely available by the same IP addresses when using Windows or Ubuntu, or if you add another wlan NIC via USB.  Nobody other than Chromebook using Chrome Secure Shell has any issues.

Workaround is to set up a jumpbox on Raspberry or Ubuntu, ssh from the Chromebook to the jumpbox and the jumpbox to the actual Raspberries.  Dumb, but as the official threads all try to blame the user, it is all that I have found to get around the rather obvious limitation.

On Wednesday, August 10, 2016 at 2:46:56 PM UTC-7, Xerxes Xarya wrote:

really me?

On Wed, Aug 10, 2016 at 5:46 PM, <xerc...@gmail.com> wrote:

WOW

On Monday, February 1, 2016 at 9:33:44 AM UTC-5, jembe wrote:

We have chromebooks at our school and would like to be able to operate Raspberry Pi headless via ssh and vnc.

The raspberry pi is running avahi-daemon.

SSH works if you use the ip address of the Pi, but not if you use the hostname. We want to be able to easily ssh to the hostname without finding the ip address. I have been able to get the desired functionality from a Mac.

ssh pi@ipaddress:22

works perfectly

ssh p...@raspberrypi.local:22

Connection refused, NaCl plugin exited with status code 255

Is this a limitation of Chrome? Or is this a network issue, or an issue with the Pi set up?

--
You received this message because you are subscribed to a topic in the Google Groups "chromium-hterm" group.
To unsubscribe from this topic, visit https://groups.google.com/a/chromium.org/d/topic/chromium-hterm/mhvarATK9pg/unsubscribe.

To unsubscribe from this group and all its topics, send an email to chromium-hter...@chromium.org.

[Stephen Lewis]

I suspect it's related to mDNS name resolution, which currently doesn't work on Chrome OS.

The original FR is at crbug.com/199397 with a follow-up at crbug.com/626377

(Sorry about the OT, but at least this gives you a bug to follow so you'll know when to expect this to start working - I'm guessing using unicast name resolution isn't an option in your environment.)

Stephen

You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-hter...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/3a98d3d1-2ddd-4ce8-bc75-e6a890fdf599%40chromium.org.