I am getting timeout issue while connecting to elasticache redis primary endpoint from my development machine. I have created claister and ec2 instance of windows machine and allow 6379 port in the ec2 instance. Still getting the issue. Can you please help me as we are implementing this on a live project
Hi, Anurag! 👋 I did some research, and found this doc which may help you troubleshoot: go.aws/3OCAcK1. If you're still in need of additional guidance, please reach out to our community of engineers via: go.aws/repost-dashboard. 🖥️ ^AR
nice video but i still gating the error when i connect the server using public ip so it will connect but after some time it give network error software caused connection abort while i connect the server with private ip so it run smoothly
Hi there, so sorry to hear about this. I have included an article that could help you out: go.aws/3yF2ZbG. If this does not help, you are welcome to reach out to our community of experts at re:Post to assist: go.aws/aws-repost. ^AM
@@awssupport thank you for answering but i use the own primary server and the server use the ubuntu OS and server is run smoothly but when i take the remote server access so using putty i take the public ip and connect it so it connect but after sometime it will give me error isted of public ip when i use to connect with private ip so it run proper then whats the reason behind it
hey the last one worked for me when I modified the script , I got the access but when i deleted that script ,it started again to give me the error of timeout so should I keep that scrip or not? or their is something else problem ?i am running ec2 micro instance.
Sorry to hear you're still getting an error, Shridhar. This guide will walk you through additional troubleshooting steps: go.aws/44u9Vlw. You can also reach out to our community of experts in re:Post: go.aws/aws-repost. ^RS
Now my another server have started acting up too. Its also using Ubuntu 22.04 OS. I use SSH PEM file to login usually. How to login using EC2 Serial Console? How to get the password?
very nice video but i detected problem while automation execution of instance , after execution i got output =overall status failed ,error: installEC2Rescue aws:runCommand Failed . please reply stuck on this problem for a while.
Hi there, I'm sorry to hear about this trouble. Here's an article that may assist: go.aws/3UVrOZv. 🔗 If you find this isn't quite what you were looking for, our experts over at re:Post might be able to help: go.aws/aws-repost. 🧰 ^AK
Sorry to hear about your experience, Mattia. I found the following document which might assist in resolving your issue: go.aws/3NnKoVF. A great way to get additional support is to reach out to our community of experts via our re:Post platform: go.aws/aws-repost. ^AM
Nice video, but I still have the problem. My question would be, if someone can connect to the instance, this person has showed me how to do it and I can't it would be something different than an AWS problem?
You are correct, Roberto, there could be an issue outside of AWS keeping you from connecting to the instance. It could also be a configuration or permissions issue, our Linux EC2 documentation contains some great troubleshooting that may help, you can check it out here: go.aws/3pDoO6W. Please check out these additional resources if you need additional technical help: go.aws/get-help. ^BD
Hi, The last one worked for me but after removing the script and rebooting. I am unable to connect to the instance again :(. I am getting Connection time out again.
Sorry to hear, Hemant! The technical nature of your query is slightly outside the scope of what we're able to assist with on this platform, but please see these options to get some help with your issue: go.aws/get-help. ℹ️🤝 ^RW
@@awssupport I am using AWS from a long time and never faced such issue. The current instance i am using is new 22.04 LTS Ubuntu. Its throwing such issue for the first time in first month. All health checks are fine and CPU utilization was also very less but still the issue. Its very strange behaviour of AWS instances.
Hi, there. For technical guidance, feel free to reach out to our community of helpful industry specialists at re:Post: go.aws/aws-repost. ✍️ We have additional options available, here: go.aws/tech-support. 📝 ^ZP
We are experiencing EC2 instances with mysql server stops working (ssh also not works) and requires to stop instance and start it again. Restarting the instances still does not work.
Hi, there. Please review these resources discussing EC2 and MYSQL errors: go.aws/4aINGNn & go.aws/3S8WKno. 🔗 For additional assistance, feel free to reach out to our helpful industry specialists at AWS re:Post: go.aws/aws-repost. ✍️ We have additional options for support, here: go.aws/get-help. 📝 ^ZP
