Can not access dvcloud through ssh

[stomov]

Many have posted about this, so I am wondering if anyone can login right now to the devcloud or if there is general problem with it.

As others have posted

ssh devcloud

asks for password, although it shouldn't.

This is the output of

ssh devcloud -vvv
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/tomov/.ssh/config
debug1: /Users/tomov/.ssh/config line 9: Applying options for *
debug1: /Users/tomov/.ssh/config line 15: Applying options for devcloud
debug1: /Users/tomov/.ssh/config line 63: Applying options for devcloud
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 102: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Executing proxy command: exec ssh -T -i ~/.ssh/devcloud-access-key-162726.txt guest@ssh.devcloud.intel.com
debug3: Incorrect RSA1 identifier
debug3: Could not load "/Users/tomov/.ssh/devcloud-access-key-162726.txt" as a RSA1 public key
debug1: identity file /Users/tomov/.ssh/devcloud-access-key-162726.txt type -1
debug1: identity file /Users/tomov/.ssh/devcloud-access-key-162726.txt-cert type -1
debug3: Incorrect RSA1 identifier
debug3: Could not load "/Users/tomov/.ssh/devcloud-access-key-162726.txt" as a RSA1 public key
debug1: identity file /Users/tomov/.ssh/devcloud-access-key-162726.txt type -1
debug1: permanently_drop_suid: 501
debug1: identity file /Users/tomov/.ssh/devcloud-access-key-162726.txt-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
Saving password to keychain failed
Permission denied (publickey).
ssh_exchange_identification: Connection closed by remote host
stomov:~ tomov$

[ShyamS_Intel]

Hi,

Thank you for posting in Intel Communities. Please follow the below steps and check if the issue still persists.

Steps to check your account and remediate:

1. Sign into DevCloud : https://devcloud.intel.com/oneapi/
2. Login/launch Jupyter – Launch Jupyter
3. Note down account number as shown below in the Welcome.ipynb notebook
4. Next, login with ssh – if error does not show up your account is good.
5. if permission denied(public key) error message shows up during login with ssh then:
   1. Check your .ssh/config : cat .ssh/config
   2. Does your account number in your ssh/config match with the one showed in in Jupyter(Example : 25550)
   3. Make sure correct account number is reflected in the config file. If not, edit your .ssh/config to correct the account number in .ssh/config to be same as the one with what you see in Jupyter
   4. Login with ssh again

If at any point during the above steps you notice files missing please contact your support team with your original account number and the correct account number – they will work with the engineering team to help assist copy your files over.

We apologize for this inconvenience cause by the public key error issue

If this resolves your issue, make sure to accept this as solution. This will help others with similar issue. Thank you.

Regards,

Shyam Sundar

[ShyamS_Intel]

Hi,

Could you please give us an update? Is your issue resolved?

Thanks,

Shyam Sundar

[ShyamS_Intel]

Hi,

We assume that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel

Thanks

Shyam Sundar