Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


A bit more on SSH
#1
I access moOde via three devices. Using pi, moodeaudio, I can only SSH in from one and I am pretty sure that I used to be able to SSH from all three.

1. Firefox on Unbuntu - works
2. Chrome on Android tablet - nope.
3. Chrome on Android phone - nope.

Two and three do this weird echo thing when entering user and pass. At each keypress they echo back that keypress plus all the of the prior input.

Finally, I cannot ssh in from an Unbutu terminal:
$ ssh pi@192.168.50.137
ssh: connect to host 192.168.50.137 port 22: Connection refused
$ ssh pi@192.168.50.137 -p4200
ssh_exchange_identification: Connection closed by remote host

Best,

      John
Reply
#2
(07-27-2018, 02:21 PM)Listener Wrote: I access moOde via three devices. Using pi, moodeaudio, I can only SSH in from one and I am pretty sure that I used to be able to SSH from all three.

1. Firefox on Unbuntu - works
2. Chrome on Android tablet - nope.
3. Chrome on Android phone - nope.

Two and three do this weird echo thing when entering user and pass. At each keypress they echo back that keypress plus all the of the prior input.

Finally, I cannot ssh in from an Unbutu terminal:
$ ssh pi@192.168.50.137
ssh: connect to host 192.168.50.137 port 22: Connection refused
$ ssh pi@192.168.50.137 -p4200
ssh_exchange_identification: Connection closed by remote host

Best,

      John

@Listener

I find the SSH Terminal feature unusable from Chrome on my Android mobile devices. There's something weird going on with the way keypresses are being processed. Like you, I can't even manage logins. Works OK with Firefox on the same devices and also with either Chrome or Safari on the iPad I get recently.

As for ssh'ing to moOde from a Linux terminal, I do it all the time using my Linux Mint laptop. Google is your friend in diagnosing the ssh message "Connection refused".

FYI, your second effort ssh'ing to port 4200 is guaranteed to fail. It's not sshd listening to that port; it's the webserver.

Regards,
Kent
Reply
#3
I use an app called Termius on my iPad but I believe it is available for Android.

https://www.termius.com/android

I would recommend it as a tablet/phone app for ssh if you are looking for one.

It is also available for Mac, Windows and Linux.
Reply
#4
(07-27-2018, 02:21 PM)Listener Wrote: Finally, I cannot ssh in from an Unbutu terminal:
$ ssh pi@192.168.50.137
ssh: connect to host 192.168.50.137 port 22: Connection refused

OK, this is really weird.

It turns out that I couldn't ssh in as the ssh daemon wasn't running.

    service start ssh

and good to go.

Here is the question, how could moode's ssh via the web connect if the daemon wasn't up and port 22 was closed?
(Web based SSH terminal server using Shellinabox by Markus Gutschk and Luka Krajger.)

     John
Reply
#5
Answering my own question. You are providing ssh via http with your own ssh setup listening via the webserver. That's why I tried port 4200, that's the port your ssh-in-a-box reports.

     John
Reply
#6
https://www.raspberrypi.org/blog/a-secur...ian-pixel/

NFI if the above explains the difficulties.

J.
Reply
#7
(07-28-2018, 12:33 PM)jerms Wrote: https://www.raspberrypi.org/blog/a-secur...ian-pixel/

NFI if the above explains the difficulties.

J.

Ah, OK. To create that file:
sudo su
cd /boot
touch ssh
reboot now

To start ssh:
sudo service start ssh

On a normal debian system to get ssh to start on boot:
sudo update-rc.d ssh defaults

    John
Reply


Forum Jump: