Troubleshooting

Configuring the Private PaaS demo instance

Why does the "No such file or directory" error message appear when trying to login to the Private PaaS instance?

The following is an example of the full error message that appears:

Warning: Identity file kim.pem not accessible: No such file or directory

The above error occurs when the location of the key pair file can not be located. If you have navigated to the directory of the Key Pair, enter only the name of the Key Pair, otherwise enter the full path of the Key Pair when executing the ssh command.

Why does the "unprotected private key file" warning occur when trying to log into the Private PaaS instance?

The following is an example of the entire error message that appears:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0640 for 'kim.pem' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
bad permissions: ignore key: kim.pem
Permission denied (publickey).

By default your private key file, which has a PEM file extension, will be unprotected. The above error message will appear if you execute the ssh command to log into the Private PaaS instance using a unprotected private key. You need to use the following command to secure your PEM file so that others will not have access to it.

chmod 0600 <path to the private key>