Troubleshooting cloud protection's gateway server errors
Errors related to gateway server communication and configuration are displayed in the Status column within the gateway server panel of the selected cluster. To access this information, navigate to Cloud Protection > Configuration > Server > Gateway Configuration and then select the target cluster . Listed below are some common gateway server errors, along with troubleshooting steps for each.
| Error code | Error message | Reason for message | Follow-up action |
| 600005 | Update Gateway Server | Outdated gateway server version preventing access to new features; the gateway server performance will remain unaffected. | Update the gateway server by following the steps in the Updating Gateway Servers page. |
| 600006 | Failed to communicate with the DataSecurity Plus server | The gateway server's attempts to communicate with the DataSecurity Plus server have failed. | To resolve communication issues, try the following steps:
|
| 600009 | Sync blocked due to Gateway Server version mismatch | Gateway server version is outdated, preventing access to new features and configuration sync updates. The gateway server will perform minimal functions only. | Update the gateway server by following the steps in the Updating Gateway Servers page. |
| 600103 | TCP port unavailable | The TCP port used by DataSecurity Plus to communicate with the gateway server is blocked or occupied by another process. | By default, DataSecurity Plus uses the TCP port 8888.To resolve issues with this port, try the following steps:
|
| 600104 | Gateway Server Access Key regenerated | The Gateway Server Access Key has been regenerated in the DataSecurity Plus server, but it has not been updated in the gateway server. | Update the Gateway Server Access Key by following the steps listed in this page. |
| 600105 | Low disk space | This error occurs when the machine running Cloud Protection 's gateway server reaches the configured minimum free disk space; this threshold is customizable. Note that the cloud app auditing will be stopped until the issue is resolved. | To resolve this issue, free up disk space or add additional space to the machine running Cloud Protection's gateway server . By default, at least 2GB of free disk space is required to store audit data.Once you have allotted the additional disk space, restart the ManageEngine DataSecurity Plus - Cloud Protection Gateway service. |
| 600202 | Failed to start proxy unit | Proxy unit within the gateway server could not be started. | For assistance in resolving the issue, please write to us at support@datasecurityplus.com. |
| 600204 | Proxy unit port unavailable | The port used by the proxy unit is unavailable. | By default, the proxy unit uses the 8200 port . Resolve the port unavailability issue to establish connection between the Gateway Server and DataSecurity Plus. To do this:
|
| 600206 | Failed to start proxy unit (-) Proxy Chain source unreachable | Incorrect proxy chain source settings. | To resolve this issue, check the existing proxy chain configuration and reset it if required. To reset proxy chain configurations:
|
| 600207 | Invalid PAC Script | The Proxy Auto-Configuration (PAC) file script has errors. | Check the existing PAC script file you've configured and rectify syntax errors, if any. |
| 600208 | Unable to download the PAC script | The PAC script location specified during the initial setup is incorrect. | To resolve this issue, ensure that the specified PAC script location is correct and that the script file is accessible.To reset the PAC script location in the gateway server configuration:
|
| 600209 | Configuration files missing or corrupted | Gateway server configuration sync during initial installation is unsuccessful. | For assistance in resolving the issue, please write to us at support@datasecurityplus.com. |
| 600301/600309 | Configuration sync mismatch | Configuration details from DataSecurity Plus Server could not be sent to the gateway server. | For assistance in resolving this issue, please write to us at support@datasecurityplus.com. |
| 600302 | Sync Error - Failed to sync CA certificate | Configuration sync with CA certificates configured was unsuccessful. | For assistance in resolving this issue, please write to us at support@datasecurityplus.com. |
| 600303 | Sync Error - Failed to sync Trust Store list | Configuration sync with Cloud Protection Trust Store was unsuccessful. | For assistance in resolving this issue, please write to us at support@datasecurityplus.com. |
| 600304 | Sync Error - Failed to sync Sanctioned Applications list | Configuration sync with Sanctioned Applications list was unsuccessful. | For assistance in resolving this issue, please write to us at support@datasecurityplus.com. |
| 600305 | Sync Error - Failed to sync Banned Applications list | Configuration sync with Banned Applications list was unsuccessful. | For assistance in resolving this issue, please write to us at support@datasecurityplus.com. |
| 600306 | Sync Error - Unable to reach Proxy Chain source | Configuration sync for updating gateway servers with Proxy Chain source details failed. | To resolve this issue, examine and rectify errors in the proxy chain source configuration.To reset the proxy chain source:
|
| 600307 | Sync Error - Unable to parse PAC script | PAC script could not be parsed due to syntax errors. | To resolve this issue, examine and rectify errors in the PAC script file. |
| 600308 | Sync Error - Unable to download PAC script | The PAC script download was unsuccessful. | To resolve this issue, ensure that the specified PAC script location is correct and that the script file is accessible.To reset the PAC script location in the gateway server configuration:
|