Troubleshooting Nginx Server

This section helps you troubleshoot the common problems that you might encounter when using certificate Nginx Server functionalities.

Issues in Device communication

Error Message Possible Cause Possible Solution
Communication to <IP> has failed. Caused by: java.io.IOException: Unable to authenticate with password, keyboard-interactive and publickey methods Possible Remediations: 1. Kindly check the credentials provided.

1. Given credentials are incorrect.

2. Given IP may be incorrect.

3. Device not reachable

1. Check and input the correct credential.

2. Check and input the correct IP

3. Ensure device is up and accessible

Issues in Certificate Directory

Error Message Possible Cause Possible Solution
Received failed response from batch

1. Device not running or not accessible

2. No valid certificates available

1. Ensure target device is up and running

2. Check the device has valid certificate files

Issues in CSR generation at Endpoint

Error Message Possible Cause Possible Solution
CSR generation got failed/User has no permission for the given location to perform the operation. User has restricted access to the path configured for the “CSR FileName” and “Key File name”

1.Kindly ensure the user configured for device addition has read/write access to the path configured.

2. For sudo user, Please check the access elevation configured in device addition

Issues in Certificate Push

Error Message Possible Cause Possible Solution
Failure during push operation to the server Nginx due to Private key should not be empty or null.Please provide valid key to proceed push.

Private key not available in push request certificate

Please ensure the private key is available in request

Pivatekey In device configured. But key content is available with the certificate from AppViewX.. So failing push request. Trying to push a certificate with key when the “Private key in device” enabled Ensure the push certificate has no key when “Private key in device” is enabled.
Privatekey not exists in device. Private key file not available in the given key location when “Private key in device” is enabled Ensure the target device has key file in the given location
Push failed since cannot write-into/create location(s) User does not have permission to perform the operation

1.Ensure the user has permission.

2.For sudo user, please check the access elevation value given in device addition

Device is not in managed state Device is not available in managed Please check the device status in device inventory