2 Answers
- Newest
- Most votes
- Most comments
0
Hi sir ,
As a part of trouble shooting activity first can you check the EC2 is in running state and health check is passed . Another view is once you restarted the EC2 instance your public IP address might changed verify it. in case you are not using the elastic IP for the instance.
Another possibilities is check you are using the right key configured with the instance.
when its come to service Jenkins verify the service is up and running .
Thanks
answered 3 years ago
0
Our ssh connections broke too yesterday. seems something changed 1st March ?
answered 3 years ago
Relevant content
- Accepted Answerasked 2 months ago
- asked 2 years ago
- asked 5 years ago
- asked a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 14 days ago
- AWS OFFICIALUpdated a year ago
Hello Sir, I have done the above and still have the same problem. What can I do at this point? Any ideas. This is a time sensitive project as I cannot continue without having to complete this step. If you work with the AWS team can you verify if my account has the right configurations setup?
Thanks and waiting for your feedback. Sincerely Edwin