- Newest
- Most votes
- Most comments
Based on the SSH log, it seems that the issue is related to the private key file "ParkMotors2019.pem". It states that the key file cannot be found or loaded.
Here are a few things you can try to resolve the issue:
Make sure that the file path for the private key is correct and that the file exists in that location.
Check the permissions on the private key file. It should be set to 600 (only the owner should have read and write access). You can change the permissions with the command "chmod 600 ParkMotors2019.pem"
Try using a different private key file. Sometimes, the key file may become corrupt or may not be compatible with the server.
Check the security group for the EC2 instances. Make sure that the instances are configured to accept incoming traffic on port 22 (SSH) from your IP address.
Try connecting to the EC2 instances using the internal IP address instead of the public IP address.
If none of these steps work, you may want to contact AWS support for further assistance.
Relevant content
- Accepted Answerasked 5 months ago
- asked 5 months ago
- asked 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
Thanks for the response! Actually I try launching another instance with the same key pair and it's working perfectly. However, I launch another instance using the default snapshot as AMI and I have 0 results. Also, I try the same thing but with a new key pairs. The result is the same Permission denied (publickey).