@AadD,   Thanks for trying out Cloudera; sorry that it has been a rocky start, but you came to the right place for help.   We'll need some information in order to assist:   - What steps did you follow to intall? What documentation? (list specific URLs if you can) - What steps did you follow to enable TLS? (list specific URLs if you can) - Did Cloudera Manager ever start and allow you to access it on port 7180? (http://cm_host:7180?) - How do you know that Cloudera Manager running or responding to HTTP requests?  What did you do to test? - If you ssh to the host where Cloudera Manager should be running, is it listening on port 7180?  7183? 7182?   Run: # netstat -nap |grep 7180;netstat -nap |grep 7183; netstat -nap |grep 7182   - If the problem is with TLS, then the following steps will turn off the TLS port for the Cloudera Manager User Interface:   (1)   Review your Cloudera Manager database configuration:   # cat /etc/cloudera-scm-server/db.properties   (2)   Use the information in db.properties to run the psql command:   For example, this is how I would connect on my host:   - I see the following in db.properties:   com.cloudera.cmf.db.type=postgresql com.cloudera.cmf.db.host=localhost:7432 com.cloudera.cmf.db.name=scm com.cloudera.cmf.db.user=scm com.cloudera.cmf.db.password=FpZ3wh9LFT com.cloudera.cmf.db.setupType=EMBEDDED   (3)   Use the db.properties information to connect to your database   For example:   - Based on the information in my environment, that would be:   # psql -U scm -h localhost -p 7432 Password for user scm: FpZ3wh9LFT psql (9.2.18) Type "help" for help. scm=>   (4)   Check the configuration that governs TLS for Cloudera Manager and Cloudera Manager agent communication:   scm=> select * from configs where attr = 'web_tls'; scm=> select * from configs where attr = 'agent_tls';   (5)   If any rows are returned from the above commands, delete them:   scm=> delete from configs where attr = 'web_tls'; scm=> delete from configs wehre attr = 'agent_tls';   Search again to verify that no rows are returned:   scm=> select * from configs where attr = 'web_tls'; scm=> select * from configs where attr = 'agent_tls';   (6)   If there are no rows returned, restart Cloudera Manager with:   # service cloudera-scm-server restart   (7)   CM can take minutes to start, so wait about 5 to be sure and then run the netstats again. If you see that CM is listening on port 7182 (agent communication) and 7180 (non-tls web ui) then try accessing it via your browser.   If CM still fails to start, review the Cloudera Manager log. On the Cloudera Manager host it is by default:   /var/log/cloudera-scm-server/cloudera-scm-server.log   Let us know how it goes.   Cheers,   Ben ... View more