I have installed mysql 5.5 and tomcat 6 on an amazon ec2 windows micro instance. I am unable to access the pages deployed in tomcat from my local browser.It says The server at ec2-50-19-6-147.compute-1.amazonaws.com is taking too long to respond.
When i pinged using my command prompt, it says request time out.
Can somebody please help me??
Thank you in advance.
You need to check your security settings and make sure that the ports are open for inbound requests.
Related
This is an issue in my office .I am able to take RDP for apponfly VM instance but not for Google and AWS .
This there anything from which I can Test the connection or difference in RDP file from them.
Thanks in advance
I'm running a master server on an EC2 linux instance with code deploy running a spring boot app.
I can ssh to the instance and i can see that the application is up and running, but i can't ping or hit the api. i set it up the same as i did our development server that is accessible.
the only thing i see is different is the subnet. is that to do with that and can i change it after the instance is up already?
The rules are open for all, there is a public ip.
i have tried noting, Not quite sure what to do, help would be welcome!
Thanks
Ok, turns out my security group wasn't open for all after all... so that was the issue. Thanks
I am trying to setup an amazon ec2 instance for first time.
I've created one with ubuntu 10.4, managed to connect to ssh and installed mongodb, mysql, php and apache which need for my proyect(also python but it is already setup).
Then I associated an elastic ip to the instance, but when I try to open the IP, I can't. It gives timeout.
Could it be that the apache root is not where I think it is?(/var/www/)
You need to check the security group that is associated with the instance. Make sure that you open up port 80.
Also make sure that apache is started, and configured to start on boot.
If you're logged in, you should be able to use wget localhost to verify if apache is serving up pages.
I installed Mule Community Server on AWS cloud and it is functioning properly. When I use http end point and invoke Mule services from browser on my Amazon EC2 machine they work. When I access them from outside, the request timeout. The end points are not bound to local host but mapped to 0.0.0.0:8081. I have checked all firewall settings using amaozon security group and set permission for all. Yet it doesnt work. I am able to access the Windows IIS http server on the same machine but not mule on port 8081. Any clues would help.
Hope this doesn't sound rude, but did you disable the windows firewall, or allow 8081 through the windows firewall?
I have a free Amazon EC2 instance. And I installed Apache web server on it. I have the DNS record for my domain point to the ip for the EC2 instance. I can not access to my website. Then I looked up and allow the http inbound. But I still failed to access my web? What might be the reason. Anybody gives me a clue?
Go to the AWS management console and look at the Security Group the instance is in. Then make sure you have the port open that you are trying to connect to (most likely 80). To open it to the world set the ip range to 0.0.0.0/0 and to open it to a specific ip (like only your house) set it to xxx.xxx.xxx.xxx/32.
That is almost always the reason people have problems connecting when they are new to AWS. I wrote this post, which should help get you setup.