SSH Permission Denied Fix

### 1. **Check Your SSH Key**
– Ensure you are using the correct SSH private key to authenticate.
– If you're using AWS, make sure the key pair you are using to connect matches the key that was assigned to your EC2 instance when it was launched.

### 2. **Verify Permissions**
– Ensure the private key file has proper permissions:

chmod 600 /path/to/your/private-key.pem

### 3. **Use Correct SSH Command**
– Ensure you're specifying the correct username (usually `ubuntu` for Ubuntu EC2 instances). Your command should look like this:

ssh -i /path/to/your/private-key.pem ubuntu@ec2-13-53-193-53.eu-north-1.compute.amazonaws.com

### 4. **Check SSH Configurations**
– Make sure that your SSH client is using the correct authentication method. Verify that the public key is present in the `~/.ssh/authorized_keys` file on the EC2 instance.

### 5. **Instance Security Group**
– Ensure that the security group associated with the EC2 instance allows inbound SSH (port 22) traffic from your IP address.

### 6. **Check for SSH Agent Issues**
– If you are using an SSH agent, make sure the key is properly added to the agent:

ssh-add /path/to/your/private-key.pem

### 7. **Instance Key Pair**
– If you're unable to use the correct key pair, you may need to create a new EC2 key pair, stop the instance, detach the root volume, attach it to another instance, and update the `authorized_keys` file. Afterward, reattach the root volume to the original instance.

### 8. **Check for Instance Status**
– Ensure the EC2 instance is running and reachable. You can check this via the AWS console or EC2 CLI.

Let me know if you need more details on any of these steps!