I have an AWS instance running in the Mumbai region that's configured as my database server for demos. We regularly stop and start this instance as needed by the sales team. It has been functioning well for about two months, but after stopping it yesterday, I was unable to SSH into it after starting it again today. Other instances with the same network and security configurations are accessible. I've tried deleting and recreating security groups to allow open internet access, but I'm still unable to connect. The instance responds to pings, but SSH gives a 'Connection refused' error. I've checked logs, looked at potential issues with fstab and sshd_config, and verified that the instance is running. I'm not a Linux expert, so I'm looking for guidance on troubleshooting this issue.
2 Answers
First off, can you share the exact SSH command you're using and the exact error message? Understanding more about your setup might help pinpoint the issue better. Also, double-check if you're trying to connect to the correct IP address.
Here’s a debug command you could run: `ssh -vvv -i ./key.id_rsa [email protected]`. It’ll give you detailed output for troubleshooting.
Make sure you check the IP address since it can change after stopping and starting the instance unless you have a static IP. If you're using a manual DNS, you might need to update it too. You can also try using the Connect option in the AWS Console, which can give you terminal access without SSH.
We have a static IP and a VPN gateway set up, so that's not the problem. AWS Connect isn't working either for me.
I know it can be frustrating! The connection refused error typically means the SSH service isn't running or listening on port 22. Have you checked the SSH server status on the machine?