I have an weird issue with EC2 instance:
I start a new Ubuntu instance (or any other).
It initialize the instance and I can ping and connect via SSH, fine...
Suddenly, I can't ping anymore! :(
I have enabled all TCP, UDP and ICMP (inbound and outbound) connections in the instance's Security Group. But no luck.
I also have tried connecting via SSH using Putty. No luck too.
I have searched a lot, but everyone says about the Security Group, which I already had configured to allow all traffic.
Any help will be appreciated! Thanks!
Prints :
http://i.stack.imgur.com/7UtE6.jpg
http://i.stack.imgur.com/E3Ou8.jpg
PS: I don't have reputation to post the images directly... :(
I've just waited and now it seems to be ok.
Maybe it was just a matter of time, wait for AWS to apply the configuration to the EC2 instance (I am using the South America region, São Paulo). But it drove me crazy because I took almost a entire day to try to connect to the instance.
Related
I have two EC2 instances running Windows. They are both in the same security group which allows for all outgoing ports, but only RDP ports from my IP. What I can't figure out is that both, to my examination, have the same security and networking settings, but one connects through RDP but the other one doesn't.
Any suggestions for settings to look at?
After a few attempts of download the .rdp file, checking the inbound rules, running nslookup myip.opendns.com resolver1.opendns.com to see my IP just to make sure I wasn't going crazy.
Ultimately what solved the problem was restarting my own computer and running the .rdp file. Not sure why, but maybe my computer was sending stale configuration data.
I have a running instance on the Linux 2 AMI.
I have a default VPC and network interface.
Security groups taken care of, even opened all traffic and still got nothing.
There is an Internet Gateway
Routes are open on the VPC
The server is running
nginx is running
Once the instance is initiated and installed, all of this is ready
I can reach the http website the first 2-3 minutes, then it is unreacheable.
No idea why, everything else still running, can still ssh into the server, but http port 80 not running.
I opened everything from iptables, still nothing.
If I reboot the server, I get a minute where I can reach the server via http, but then a minute later its the same again.
I can reach http if I use $ wget http://localhost
So I think it is probably something from the EC2 control panel, not the instance itself.
I tried on new instances too.
Anyone has an idea?
The reason behind this weird behavior was that AWS abuse team had blocked some of my ports, had to upgrade to the developer plan to be able to know this, contacting them at the moment
I am having trouble sshing into my EC2 instances since I restarted my account. I connect to a new tmicro instance for about 4 minutes, but I get a broken pipe error and am thereafter unable to connect despite restarting the instance and my computer (timeout err).
I've confirmed that I'm connecting on port 22. I've confirmed that port 22 is open and unblocked. Shut off the firewall and all that. Connected to other sites via ssh. I have read through the troubleshooting on security groups and what not. It all seems very simple and obvious stuff that I haven't done wrong. Everything appears to be in order, as I confirmed launching an instance with an identical configuration as a friends, and we walked through the steps together over a hangout...
Can anybody advise on follow up? Has anybody encountered something like this with SSH in general? Nothing pops out to me in my logs or the server logs I can see on AWS. And it seems I've isolated most of the variables that I can in the steps I tried.
Firewall - "Shut off the firewall and all that" - are you using something like iptables on the instance itself? To keep things simple, I just use the AWS security groups because otherwise you need to maintain two firewalls which is confusing. Maybe there's an issue here. What do you mean by shutting the firewall off?
Logs - tail the ssh logs while you're still connected (I think tail -f /var/log/audit.log). Is there anything in there?
SSH - when you fail connect, use the -vvv flag and let us know what you get.
To prevent the broken pipe, you probably need to modify config in /etc/ssh/ssh_config. Look at ServerAliveInterval.
I have an EC2 instance which until last week I could connect through ssh using a key fine. Since then, I can not connect on it anymore. Also, ping do not respond. But, I can still access my website that runs on that instance. To the best of my knowledge, I havent applied any change on security settings that could be blocking it. Is there any suggestions on what could going on?
I followed everything in exact same order as refered here :Amazon Set Up Documentation. I also read many SO answers but everyone suggested on checking the security group and route tables. I did everything none of them helped.
I have a USB Dongle which I use to surf internet. Its IP changes everytime I disconnect the dongle and reconnect it. But if I stay connected its IP remains same. So I did created a security group my_ip/32 and launched an ec2 instance. So without disconnecting my dongle i.e keeping my IP intact I tried to connect to the instance through SSH with simple
ssh -v -i my-key-pair.pem user#public_dns
command but with no luck.
But the funny thing is I can connect to the ec2 instance if I change my security group to 0.0.0.0/0 which is not suggested by amazon because of security issue.
Does anybody has faced the similar situation. Or Amazon did miss something in their documentation.
NOTE:
I also enable firewall in ubuntu for ssh as follows:
sudo ufw allow ssh/tcp
sudo ufw enable
Am I missing something??
When you google 'what is my ip' does it give you the result you expected for my_ip? Google will report back the IP the outside world sees you as.
I have a feeling you might be going through a NAT router which you're recieving DHCP from, as such you're dongles IP isn't even being seen by EC2 to match a security group.