1 Answer
- Newest
- Most votes
- Most comments
0
You are using SFTP (port 22). According to your error message, the network settings look OK because you are getting a response from the SFTP process refusing your key. Take a look at this to help troubleshoot: Why am I getting a "Server refused our key" error when I try to connect to my EC2 instance using SSH?.
Relevant content
- asked a year ago
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Your developer's inability to access FTP and view code to fix bugs, unavailability of EC2, and API errors on other servers indicate problems with some of your AWS resources. The first thing to focus on is checking the EC2 console to confirm if your EC2 instance is running properly. If stopped, restart it immediately. If impaired or terminated, recover or redeploy. If the instance is running, check its security group to ensure FTP port 21 is open inbound. Also check network configuration for any issues. If fixed and FTP access is still unavailable, it could be an application issue and you'll need to check FTP software logs. Unreachable EC2 means any service relying on that instance will be Impacted. Get EC2 to a healthy state first. If unable to recover the instance, you'll need to redeploy from a backup or replica. Servers with API errors likely indicate an issue with the AWS services they depend on. Check if AWS has notified of any service impacts that could relate to your issues. Look at application logs on these servers to determine the API errors and root cause. It could be anything like network, authentication, routes, ACLs, etc. Fixing the failing AWS services will resolve the API errors.
Hi Tison, after following the suggested options, we still get another error. I have added another screenshot with the error meaasage.