Troubleshooting Certificate Reports Configuration
Issues in Configuring the Validation Status Report
| Error Message | Possible Cause | Possible Solution |
|---|---|---|
| FQDN cannot be null or empty. | The FQDN value provided is either null or empty. | Provide a valid FQDN value. |
| Certificate network discovery plugin may not be enabled. Contact AppViewX support team. | The plugin avx_vendor_cert_network_discovery is not enabled. | Enable avx_vendor_cert_network_discovery plugin. |
| Certificate network discovery plugin may be in not running state. | The plugin avx_vendor_cert_network_discovery may be in the “Not Running” state. | Start avx_vendor_cert_network_discovery plugin and try again. |
| IP <ipPort> is invalid | Given IP port is not valid. | Check and provide a valid IP port. |
| Invalid FQDN. | AppViewX is not able to access the given FQDN. | Check if the FQDN is valid and whether AppViewX has access to the FQDN. |
| Missing user information. | User information is not available in the request. | Provide a valid session-id or username and password in the request. |
Issues in Configuring the Certificate Summary Report
| Error Message | Possible Cause | Possible Solution |
|---|---|---|
| Cert report settings name already exists, Please verify. | The report settings name provided is already taken. | Report settings name should be unique. |
| Unable to schedule report generation, skipping to add/update the settings. | AppViewX is not able to add/update the scheduler job in crontab. |
1. Provide valid cron settings. 2. DB may not be reachable, try after some time. |
Issues in Configuring the Count by Issuer Report
| Error Message | Possible Cause | Possible Solution |
|---|---|---|
| Cert report settings name already exists, Please verify. | The report settings name provided is already taken. | Report settings name should be unique. |
| Unable to schedule report generation, skipping to add/update the settings. | AppViewX is not able to add/update the scheduler job in crontab. |
1. Provide a valid cron setting. 2. DB may not be reachable, try after some time. |
