DevCloud SSH connection failed on MacOS

[Mark_L_Intel1]

This is the follow up to the other post on SSH key empty.

I got this issue a couple weeks ago when I follow the Base Toolkit sample Get Started page.

At first, I got the SSH connection problem in step #1 "Connect to DevCloud" when I selected "Linux/MacOS" path. Then I realized the key link in "Option 2" is generated empty file.

With the DevCloud's support, I have use the following page as a work around,

https://devcloud.intel.com/oneapi/documentation/connect-with-ssh-linux-macos/

The SSH key seems to be normal this time but I still got connection issue as showed in this post.

Mark

[ArunJ_Intel]

Hi Mark,

The issue is because you are behind a proxy. In the configuration generated in .ssh/config file you should replace PROXY_HOSTNAME:PORT with a valid proxy hostname and port, provided by your network administrator.

If you are in intel network a proxy that you could use is  proxy-us.intel.com:1080

Let me know in case of any further issues.

Thanks

Arun

[Mark_L_Intel1]

Thanks Arun,

Yes, you are correct. But I can't get connect by replacing with PROXY_HOSTNAME:PORT

 Yes, I can SSH to DevCloud if I disconnect my VPN.

But when I connect VPN and use SSH again, it has the same timeout error.

I used both my proxy URL and the URL you suggested, both are failed.

Mark

[ArunJ_Intel]

Hi Mark,

When connected to vpn and replacing proxy url, what is the error you are getting, are you still getting the same error as before. Also could you share your config file, so we could verify if there are any issues.

Thanks

Arun

[Mark_L_Intel1]

Hi Arun,

Yes, this is the same error.

$ ssh devcloud
ssh: connect to host devcloud.intel.com port 22: Operation timed out
kex_exchange_identification: Connection closed by remote host

I will send you my configuration file via internal email.

Mark 

[ArunJ_Intel]

Hi Mark,

As we have discussed internally and you could connect to devcloud successfully. Could you confirm if we could close this thread.

For others facing similar problem, The below were the steps required to solve this issue

1)Change the proxy command to the one below for MAC os

ProxyCommand /usr/bin/nc -X 5 -x PROXY_SITE %h %p

where PROXY_SITE is your corporate proxy

2)Use ssh devcloud.proxy instead of ssh devcloud as the ssh command to connect when using proxy.

Thanks

Arun

[Mark_L_Intel1]

Thanks Arun, 

Yes, uses following command inside VPN, solved my problem:

ssh devcloud.proxy

Thanks so much for the help.

Mark Liu

[ArunJ_Intel]

Thanks Mark for the confirmation, we wouldn't be monitoring this thread any further. Please raise a new thread in case of further issues.