I'm trying to open up the MySQL (3306) port on my EC2 instance and even though I've added the rule, it appears the port is still closed. Do I need to reboot my instance for the policy changes to take effect?
on 10/27/2012 – Made popular on 10/27/2012
So I've done this a few dozen times on a 'normal' box (not in EC2) and it seems simple enough. I was trying to run ssh on port 22 and 80 but I couldn't, for the life of me, figure out why I can't connect through port 80 but I can connect fine using port 22.
I have not changed the security settings on my Amazon EC2 m1.small instance, but ever since I recently installed security updates, including a new kernel, it stopped accepting new ICMP echo and tcp connections to ports other than 22.
I have a QEMU instance running on a CentOS 6.4 server. I need to make it so that when one connects to port 23 on the host, they connect to port 23 on the QEMU instance's guest OS. How can I accomplish this? Note that I only have SSH access, so if eth0 goes down I loose control of the server and reboot it using my provider's management panel.
I'm on a Linux machine and am trying to replace an Apache2 instance with a Tomcat 6 instance. I shut down the Apache instance by running a kill on the appropriate pid, but when I try to access any pages, I get an error 504 instead of 404. Additionally, when I run the Tomcat 6 instance, I still get the error 504. Requests to port 80 get returned much faster than requests to port 8080.