If you do find that Cloudera Manager is listening on 7180, make sure it is listening on all interfaces.
If you are getting a timed out message or a hang, that makes me suspicious that the server is coming up, but your route to that host is not working properly. Could there be a proxy configured in your browser that cannot connect to your CM server?
You might try tcpdump or browser developer tools to find out what the client/server communication looks like.
I'd start with making sure the server is listening on 7180 and review the log for any exceptions or errors that look important.
Hi @dewdrop, It seems that you have opened the port 7180 on the EC2 Instance Firewall. But also you need to open TCP port 7180 in EC2 Security group.
How you can do this. Go to the "Network & Security" -> Security Group settings in the left hand navigation Find the Security Group that your instance is apart of Click on Inbound Rules Use the drop down and add port 7180 Click Apply.
If your browser cannot connect to ip-172-31-44-224.us-west-2.compute.internal:7180, then make sure that curl can connect You tested with curl, but used "localhost" so the test was not as close a comparison as one would like.
Make sure that the ip-172-31-44-224.us-west-2.compute.internal hostname can be resolved to a proper IP address and that your host has a route to that IP address.
WireShark is a great tool decoding packets sent over the wire and can give you perspective about where the problem may be occurring
I'm not saying that it isn't firewalls or otherwise, but it would be good to clarify what is stopping the client from reaching the server host/port
Thanks a lot everyone who replied back to me to help, The cloudera cm install went on fine and tats the reason I was able to connect the url internally from the host machine, it’s a mistake from my end I grabbed the private ip instead of the public ip and url failed, but when I used the public ip was able to login to cloudera manager without any issues.