Intel® DevCloud
Help for those needing help starting or connecting to the Intel® DevCloud
1626 Discussions

unable to connect to devcloud

paul24
Beginner
1,499 Views

paul@mars:~> ssh -v devcloud
OpenSSH_8.4p1, OpenSSL 1.1.1d 10 Sep 2019
debug1: Reading configuration data /home/paul/.ssh/config
debug1: /home/paul/.ssh/config line 8: Applying options for devcloud
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 20: Applying options for *
debug1: Executing proxy command: exec ssh -T -i ~/.ssh/devcloud-access-key-163970.txt guest@ssh.devcloud.intel.com
debug1: identity file /home/paul/.ssh/devcloud-access-key-163970.txt type -1
debug1: identity file /home/paul/.ssh/devcloud-access-key-163970.txt-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.4
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug1: Authenticating to devcloud:22 as 'u163970'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: curve25519-sha256 need=64 dh_need=64
debug1: kex: curve25519-sha256 need=64 dh_need=64
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:7R/nUuhf2mWQej8YRr+FNr0T0++Rw71wmvZpsrysbFU
debug1: Host 'devcloud' is known and matches the ECDSA host key.
debug1: Found key in /home/paul/.ssh/known_hosts:13
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /home/paul/.ssh/devcloud-access-key-163970.txt explicit
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /home/paul/.ssh/devcloud-access-key-163970.txt
^C

hangs 

paul@mars:~> ssh -v -i ~/.ssh/devcloud-access-key-163970.txt guest@ssh.devcloud.intel.com
OpenSSH_8.4p1, OpenSSL 1.1.1d 10 Sep 2019
debug1: Reading configuration data /home/paul/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 20: Applying options for *
debug1: Connecting to ssh.devcloud.intel.com [12.229.61.118] port 22.
debug1: Connection established.
debug1: identity file /home/paul/.ssh/devcloud-access-key-163970.txt type -1
debug1: identity file /home/paul/.ssh/devcloud-access-key-163970.txt-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.4
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 Ubuntu-4ubuntu0.5
debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.5 pat OpenSSH* compat 0x04000000
debug1: Authenticating to ssh.devcloud.intel.com:22 as 'guest'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: curve25519-sha256 need=64 dh_need=64
debug1: kex: curve25519-sha256 need=64 dh_need=64
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:fdh1CzIao2MCh6YQ3uP7ZZyZF0XqieU7OY6DjcDctq4
debug1: Host 'ssh.devcloud.intel.com' is known and matches the ECDSA host key.
debug1: Found key in /home/paul/.ssh/known_hosts:12
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /home/paul/.ssh/devcloud-access-key-163970.txt explicit
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,sk-ssh-ed25519@openssh.com,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ecdsa-sha2-nistp256@openssh.com>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /home/paul/.ssh/devcloud-access-key-163970.txt
debug1: Authentication succeeded (publickey).
Authenticated to ssh.devcloud.intel.com ([12.229.61.118]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug1: Remote: /opt/ssh/getkey %f:1: key options: agent-forwarding command permitopen port-forwarding pty user-rc x11-forwarding
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

Protocol mismatch.

debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
debug1: channel 0: free: client-session, nchannels 1
Connection to ssh.devcloud.intel.com closed.
Transferred: sent 3152, received 2704 bytes, in 12.3 seconds
Bytes per second: sent 255.4, received 219.1
debug1: Exit status 0

 

0 Kudos
16 Replies
AthiraM_Intel
Moderator
1,478 Views

Hi,


Thank you for posting in Intel Communities.


Could you please share the config file you are using?


Also check whether you are able to access JupyterLab.



Thanks




0 Kudos
paul24
Beginner
1,472 Views

cat ~/.ssh/config

 

################################################################################################
# oneAPI DevCloud SSH config
################################################################################################
Host devcloud
User u163970
IdentityFile ~/.ssh/devcloud-access-key-163970.txt
ProxyCommand ssh -T -i ~/.ssh/devcloud-access-key-163970.txt guest@ssh.devcloud.intel.com

Host devcloud.proxy
User u163970
Port 4022
IdentityFile ~/.ssh/devcloud-access-key-163970.txt
ProxyCommand ssh -T devcloud-via-proxy

# If you must route outgoing SSH connection via a corporate proxy,
# replace PROXY_HOSTNAME and PORT below with the values provided by
# your network administrator.
Host devcloud-via-proxy
User guest
Hostname ssh.devcloud.intel.com
IdentityFile ~/.ssh/devcloud-access-key-163970.txt
LocalForward 4022 c009:22
ProxyCommand nc -x PROXY_HOSTNAME:PORT %h %p
################################################################################################

################################################################################################
# DevCloud VSCode config
################################################################################################
Host devcloud-vscode
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
Hostname localhost
User u163970
Port 5022
IdentityFile ~/.ssh/devcloud-access-key-163970.txt
################################################################################################

################################################################################################
# SSH Tunnel config
################################################################################################
Host *.aidevcloud
User u163970
IdentityFile ~/.ssh/devcloud-access-key-163970.txt
ProxyCommand ssh -T devcloud nc %h %p
LocalForward 5022 localhost:22
LocalForward 5901 localhost:5901
################################################################################################

 

i will check JupyterLab

0 Kudos
AthiraM_Intel
Moderator
1,425 Views

Hi,


Could you please let us know whether you are able to access JupyterLab?




Thanks


0 Kudos
paul24
Beginner
1,421 Views

i am unable to use JupyterLab, it tells me  

'DevCloud Enrollment is Required'.

if i click this i get

There is already an Intel DevCloud account associated with this email. Go to https://www.intel.com/content/www/us/en/developer/tools/devcloud/overview.html to access Intel DevCloud. For assistance resolving account issues, visit the Intel DevCloud Forum.

 

and im back where i started

 

 

0 Kudos
AthiraM_Intel
Moderator
1,410 Views

Hi,


Could you please check whether your account is expired or not?


To check the account expiration of your DevCloud account, please follow the below link :

https://community.intel.com/t5/Intel-DevCloud/DevCloud-Account-Expiration-How-to-check/m-p/1296418


If you face any issue, please let us know.



Thanks





0 Kudos
paul24
Beginner
1,394 Views

hi,

it was expired, the mess started with reactivation of the account.

 

'DevCloud Enrollment is Required'.

if i click this i get

There is already an Intel DevCloud account associated with this email. Go to https://www.intel.com/content/www/us/en/developer/tools/devcloud/overview.html to access Intel DevCloud. For assistance resolving account issues, visit the Intel DevCloud Forum.

 

thanks

0 Kudos
AthiraM_Intel
Moderator
1,370 Views

Hi,

 

We apologize for the inconvenience caused.

 

Can you try registering for Intel DevCloud for oneAPI using another email address and see if you are able to create a new account? If not, do get back to us.

 

Registration Link: https://devcloud.intel.com/oneapi/

 

Thanks


0 Kudos
AthiraM_Intel
Moderator
1,335 Views

Hi,


We have not heard back from you. Could you please give us an update?



Thanks


0 Kudos
paul24
Beginner
1,267 Views

i created a new account as tarflah@posteo.de got devcloud user id u183069.

it authenticated 

     debug1: Authentication succeeded (publickey).
     Authenticated to ssh.devcloud.intel.com ([12.229.61.118]:22).

but then the problem is 

     debug2: shell request accepted on channel 0 
     SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

    Protocol mismatch.

and the connection is closed

niels

 

 

 

0 Kudos
AthiraM_Intel
Moderator
1,239 Views

Hi,


Could you please let us know whether you are able access JupyterLab?


Also share the screenshot of the error and the command you used.



Thanks


0 Kudos
niels1
Beginner
1,226 Views

hi,

access via JupyterLab works.

via ssh does not.

so probably there is all correct on your side.

 

thank you

0 Kudos
AthiraM_Intel
Moderator
1,215 Views

Hi,

 

Thank you for the update.

 

Could you please follow the below steps to connect to DevCloud via cygwin:

 

1. Download this simple Windows batch script install_cygwin.bat (highlighted in the screenshot) from below link: https://devcloud.intel.com/oneapi/documentation/connect-with-ssh-windows-cygwin/

AthiraM_Intel_0-1673435044406.png

 

2. Extract the downloaded script (keep it as default c:\cygwin64)

AthiraM_Intel_8-1673435467814.png

 

3. Now open the Cygwin64 terminal, which looks like below.

AthiraM_Intel_7-1673435436377.png

 

4. Now go to the below path and add the setup-devcloud-access-xxxxxx.txt to that path. (Connect with Cygwin | Intel® DevCloud)

path: C:\cygwin64\home\<User_name>

file: setup-devcloud-access-xxxxxx.txt

AthiraM_Intel_5-1673435341570.pngAthiraM_Intel_6-1673435368287.png

 5. Open the Cygwin terminal and follow the below commands.

 

 

 

ls

 

 

 

 setup-devcloud-access-xxxxxx.txt

  

 

 

bash ./setup-devcloud-access-xxxxxx.txt

 

 

 

6. Connect to the DevCloud using( ssh devcloud)

 

 

 

ssh devcloud

 

 

  

If you face any further issue, please let us know.

 

 

Thanks

 

 

0 Kudos
niels1
Beginner
1,171 Views

hi,

i installed cygwin, following your instructions but its the same result:

 

u183069@devcloud: Permission denied (publickey)

 

niels

0 Kudos
AthiraM_Intel
Moderator
1,148 Views

Hi,


We are checking on this issue internally, will get back to you soon.



Thanks


0 Kudos
AthiraM_Intel
Moderator
1,031 Views

Hi,

 

The issue could be that account keys are corrupted. Could you please create a new account.

If you gets a message that "account already exists", please let us know.




Thanks


0 Kudos
AthiraM_Intel
Moderator
978 Views

Hi,


Glad to know 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


0 Kudos
Reply