Another thing worth trying is to capture network traffic on CM server host for port 7180 (you can use tcpdump to do this for example), and check when you request to access port 7180 from your web browser, does CM server host even receive the request or not. ... View more

Hi Axe,   As you are able to curl port 7180 from the CM server host successfully, but not from other machines, this proves that CM server port 7180 is listening and working fine. You need to work with Network team or AWS team to investigate further regarding network relevant issue I believe. for example iptables or firewalld configuration. Please let us know if you have any progress. ... View more

Are you even able to ping this host from your local machine? Are you able to telnet to other port from your local machine? ... View more

It looks like a network relevant configuration issue. Can you please run below command on CM server host:   netstat -lnpt | grep 7180 ... View more

Hi Axe,   You mentioned that ". I am able to run the Curl command on 7180 on the Master node and I get the output. "   When you said you get the output, do you mean the curl response content is the correct CM web UI content? If yes, it means CM server itself works fine with the Web UI part. Can you try to curl to Master node 7180 from a different machine, including the machine you are trying to connect using web browser and see if you get the correct response. ... View more

Hi @Axe ,   Can you please share CM server log? ... View more