Browser fails to load CPM GUI with the "Bad Request" error

Browser may fail to load CPM GUI with the "Bad Request" error, with reason listed as "You're speaking plain HTTP to an SSL-enabled server port":

The reason is that you are trying to access port 443 over HTTP instead of HTTPS, like this:

http://cpmhostname:443/console/

You should use this instead:

https://cpmhostname/console/

• Related Articles

• Failed to open IdP login page or to test connection with the errors: "HTTP Error 503. The service is unavailable." or "404 - File or directory not found."

  Issue:  When trying to connect to IdP from CPM, you may receive errors:  "HTTP Error 503. The service is unavailable."  or "404 - File or directory not found." There are no errors in the AD FS event log or  OKTA System logs, as well as CPM logs. ...

• Permission checks fails with Error: “User not Found”

  Permission checks fails with Error: “User not Found”   You may receive the following error when checking permissions on an account within CPM.  Also, the policy check .CSV file will show only “User not Found” when opened. In the cpm_server logs you ...

• CPM installation may fail when the instance is fronted by an Elastic Load Balancer (ELB) or an Application Load Balancer (ALB)

  Background: By default when creating a new AWS Elastic Load Balancer (ELB) or an Application Load Balancer (ALB) it has a default timeout of 60 seconds. During the CPM installation this timeout value can be exceeded and cause the CPM installation to ...

• CPM in Recovery Mode error - S3 worker fails with worker i-12345678912345678 stopped communicating - terminating operation

  CPM in Recovery Mode error - S3 worker fails with worker i-12345678912345678 stopped communicating - terminating operation Issue: When CPM is in recovery mode being used for DR drills, the original CPM’s process to detect “zombie” worker’s can be ...

• "SnapshotQuotaExceeded" error when trying to backup RDS

  Customer may receive the following error when trying to backup RDS: ERROR:  get_object(connection.py:1202)  400 Bad Request ERROR:  get_object(connection.py:1203)  <ErrorResponse xmlns="http://rds.amazonaws.com/doc/2013-05-15/">   <Error>     ...