Thank you for posting in Intel communities.
Sorry for the inconvenience caused. Could you please try again to login? If the issue persists, try with a different mail id and let us know.
Regarding permission denied issue, the error was due to a bug on the web portal SSO introduced Thursday July 14th at ~1pm and resolved at ~10am July 15th. In fixing this bug, if you are still getting this error, please download the public key as shown in the credentials email.
If you are still facing this issue then let us know.
We are extremely sorry for the inconvenience caused. Kindly follow the below steps.
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:
a. Check your .ssh/config : cat .ssh/config
b. Does your account number in your ssh/config match with the one showed in in Jupyter(Example : 12345)
c. 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
d. Login with ssh again
If at any point during the above steps you notice files missing please contact us with your original account number and the correct account number – we 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.
I got the following message when I tried to launch jupyter?
500 : Internal Server Error
You can try restarting your server from the home page.
I tried to restart but nothing changed as well.
We have applied a backend fix to Jupyter/ssh at 7:55 PM on 31st July, 2022
Please try Jupyter and let us know, if you are still facing any issues.
We apologize for the inconvenience caused.
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.