Troubleshooting AWS ELB

Overview

This section helps you troubleshoot the common problems that you might encounter when using AWS cloud functionalities for ELB service. This guide will give more troubleshooting processes on certificate discovery & certificate push.

Supported Web Browsers

Browser Version Notes
Firefox Till latest (Version 84.0.4147.135) NA
Chrome Till latest (Version 80.0) NA
IE Limited support in 9, Full support from 10+ No support for IE9 post-AppViewX Version 11.0
Safari

Till latest (Windows - Version 5.1.7,

macOS - Version 13.1.2)

 From AppViewX Version 11.1
Opera Till latest (Version 70) From AppViewX Version 11.1

Supported Devices

Device OS Resolution
Desktop Windows 1024 X 768 onwards, 1366x768, 1920x1080, Higher
Desktop Linux 1024 X 768 onwards, 1366x768, 1920x1080, Higher
Desktop Mac 1024 X 768 onwards, 1366x768, 1920x1080, Higher
iPad iOS 1024 X 768

Issues in Discovery in ELB

Table 1. Error messages and resolutions
Error Message Possible Cause Possible Solution
Please provide information as required

  1. Discovery name is not given or length is less than 2 characters.

  2. Interval between batches info. is missing when execution type is sequential.

  1. Enter a valid name with a minimum of 2 characters.

  2. Provide a time interval between batches in minutes.
Please select a device No device is selected in the “Discover By” section. Select at least one device to discover certificates from.

Issues in Push-Bind and Rollback

Table 2. Error messages and resolutions
Error Message Possible Cause Possible Solution
Unable to initiate request.
  1. Pushing to device when certificate is unavailable, i.e, in a new state.
  2. Previous work order is in progress and not completed.
  3. AppConnector might not be in sync.
  1. Push to device after certificate has been retrieved from CA.
  2. Initiate push after previous work order is finished.
  3. Synchronize the AppConnector and retry.
Unable to initiate request, template is in disabled state Given workflow is not in an enabled state Enable the push/rollback workflow from the Workflow section.
User is not authorized User does not have required permissions to push to the device. Retry after getting the access for required action.
1 validation error detected: Value at 'privateKey' failed to satisfy constraint. Private key content is not available for the certificate. Private key is mandatory for the certificate to be pushed.
Application connector(s) not found Application connector info was not found. Provide the correct connectorId if not pushing using AppViewX UI.
Request associated with the application connector is in progress Previous work order is in progress and not completed. Initiate this request after the previous work order is finished.
Push not triggered or succeeded or No existing data available for backup process. Rollback couldn’t proceed because the push was not successful. Only successfully pushed certificates can be rolled back.
Certificate not found. Pushing to the device when certificate is unavailable, i.e, in a new state. Push to the device after certificate has been retrieved from CA.
Provided certificate is not a valid self signed. Please provide either a valid self-signed certificate or certificate chain The provided certificate is not a valid certificate. Push a valid certificate.
Push failed as there exists another certificate with commonName Certificate with the same common name is present in certificate manager Check whether it is a duplicate certificate and remove the invalid one.
Cert Association failed with profile Modify access may not be available on the selected resource Provide Modify access for the resource and retry
Association failed with profile-<PROFILE_NAME>as no such profile available Profile may not be available on the cloud account Perform config fetch on the device from ADC module and retry association of cert.