There are several possibilities and usually the error message can give you some hints.
Your account has expired
Please send us an email to email@example.com with the current end date of your contract and we will extend your account accordingly.
Permission denied (publickey)
Basically, you are NOT able to connect to the access servers until your SSH public key is configured. There can be several reason that explain the permission denied message:
- Ensure you have run your SSH agent
- If you have a new computer or for some other reason you have generated a new ssh key, please update your ssh keys on the IPA user portal.
- You are using (deprecated) DSA keys. As per the OpenSSH website: “OpenSSH 7.0 and greater similarly disable the ssh-dss (DSA) public key algorithm. It too is weak and we recommend against its use”. Solution: generate a new RSA keypair (3092 bit or more) and re-upload it on the IPA web portal (use the URL communicated to you by the UL HPC team in your “welcome” mail). For more information on keys, see this website.
- Your public key is corrupted, please verify and re-upload it on the IPA web portal.
- We have taken the cluster down for maintenance and we forgot to activate the banner message mentioning this. Please check the calendar, the latest Twitter messages (box on the right of this page) and the messages sent on the
Be careful with permission changes to your $HOME
If you change your home directory to be writeable by the group,
ssh will not let you connect anymore.
It requires drwxr-xr-x or 755 (or less) on your
~/.ssh, and -rw-r–r– or 644 (or less) on
File and folder permissions can be verified at any time using
stat $path, e.g.:
$> stat $HOME $> stat $HOME/.ssh $> stat $HOME/.ssh/authorized_keys
Check out the description of the notation of file permissions in both symbolic and numeric mode.