Unable to connect via ssh

[grallewellyn]

I am just seeing my ssh as undefined (separate issue), but @rtapella gets
% ssh root@54.191.120.17 -p 32413
ssh: connect to host 54.191.120.17 port 32413: Connection refused

[rtapella]

might be fixed by #850
?

[grallewellyn]

I tested #772 and it is still not working for me and was not fixed by #850

@rtapella You were the one getting the connection refused behavior (I was not able to replicate this)
Do you still get this error after uploading your ssh key?

[rtapella]

same behavior.
tried making a fresh 2048 bit key. added to authorized_keys file and uploaded it via the Profile.

[rtapella]

(ssh key upload worked fine)

[rtapella]

I am still seeing the same behavior. Tried 2048 and 4096 bit keys

[rtapella]

I added it to the Profile and to ~/.ssh/authorized_keys and logged out/in to refresh everything. I also stopped and started the workspace. Still "Connection refused"

[jerry-clayton]

Hi, I am a new user and ran into this problem. I was finally able to get SSH to work for me using these steps:

1. Followed MAAP instructions to upload SSH key. I used a 2048 bit key.
2. run apt-get update
3. run apt-get install systemctl
4. run apt-get install openssh-server
5. run systemctl enable sshd
6. followed the instructions in this AskUbuntu answer (The answer says to add these lines to a file in /etc, but that file did not exist for me, so I just ran the commands in terminal):
7. mkdir /var/run/sshd
8. chmod 0755 /var/run/sshd
9. run systemctl start sshd

After this I was able to SSH into the server. A few linked answers to the one above imply there is some sort of issue with the version of openssh-server, but it is unclear to me the exact root of the issue is. Either way, this solved it for me. I hope it helps!

[wildintellect]

@jerry-clayton thanks for the info.

@grallewellyn seems like maybe we're not configuring the ssh service correctly in the images. Note: we don't want to leave this to the users, since we'd want to control the sshd configuration and have it be persistent. Question is what changed in recent images this used to work in older images @sujen1412 @bsatoriu ?

[grallewellyn]

@bsatoriu and I were able to replicate this by
Run this in your ADE terminal:

Following MAAP instructions to upload SSH key. I used a 2048 bit key.
apt-get update
apt-get install systemctl
apt-get install openssh-server
mkdir /var/run/sshd
chmod 0755 /var/run/sshd
/usr/sbin/sshd -ddd

Then go to your machine and make sure the right key is named id_rsa in your ~/.ssh, then running the ssh information you get from View -> Activate command palette -> Display SSH info

This ticket isn't our highest priority right now, but when we have time to get to this issue, we should just:
add the above commands to our Dockerfiles and then add in the documentation that the user needs to run /usr/sbin/sshd -ddd on the ADE then on their local machine run the SSH information and that id_rsa needs to be named correctly or else you will be prompted for a password

[ameliaholcomb]

Also, currently some environment variables (such as "MAAP_PGT", needed for maap.listJobs()) are not available via ssh.
(When started per the instructions in #849 (comment))

[sujen1412]

The MAAP_PGT token is only available in the env when logging in from the browser, that does mean it will not be set when ssh'ing. Thanks for pointing that out.
If you need to retrieve your token outside the MAAP env, it is available on your profile - https://maap-project.org/profile