- Release notes for the latest v2.3.x CPM release
- Logging into CPM using Identity Provider may fail with an error "An error occurred"
- Permission check may fail with an error "Could not assume role"
- What are the required minimal AWS permissions/roles for CPM operation?
- Login failure with the reason https://%cpm servername%/remote_auth/metadata is not a valid audience for this Response (invalid_response)
- See all articles
- Instance recovery may fail with the following error: "Recovery Operation Failed. Reason: EBS-optimized instances are not supported for your requested configuration."
- Backup stuck in "pending" status after restart
- N2WS-1040 - "Trying to download a file or directory from a backup and receive "There are no active explore sessions..." message."
- IDP/SAML integration may fail with "Failed getting CPM public host name"
- The "Users" panel may become non-functional after an upgrade to v2.2.x
- See all articles
- Encrypted Snapshot Recovery from DR account may fail with the “Given key ID is not accessible” error
- How to improve CPM’s performance or overcome high memory consumption by creating a swap partition
- All CPM operations may fail with the "Name or service not known" error
- Cross-Region DR RDS backup may fail with "Copy failed due to an AWS limitation regarding default encryption key” error
- AD FS may produce “An error occurred” page when logging in or performing Test Connection
- See all articles