Output and Troubleshooting
This section describes the expected output of the Nimbusec Server Agent and covers the success case as well as common error conditions.
Exit Codes
If you run the server agent as through scheduling like cron or windows scheduled tasks or you use the server agent as part of a scripted automation you can test for the following exit codes to trigger actions or send notifications.
| Code | Meaning |
| 0 | Success. The agent scanned all configured directories and was able to upload all scan results to the Nimbusec Servers. |
| 1 | An error occurred while reading the configuration through the config file or the environment variables. Due to this no scans were performed. |
| 2 | An unknown command line parameter was used when starting the server agent. |
| 3 | An error occurred during at least one scan. Unaffected domains may have been scanned successfully. Please check the logs to see errors and affected domains. |
| 4 | An error occurred during at least one upload of scan results. Unaffected domains may have been scanned successfully. Please check the logs to see errors and affected domains. |
Log Output
The log output of server agent is structured as follows:
General Messages: Date Time [log level] log message
Domain Specific Messages: Date Time [log level][domain] log message
Log Level can be [info] to indicate an information-message or [error] indicating an error condition. If [error] is followed by [domain] the error message only relates to the scan for this domain.
The following example shows the log output for a scan with multiple domains (nimbusec.com, cyberrisk-rating.at, portal.nimbusec.com).
Common Error Messages
oauth2: "invalid_client"
The most common reason for this an error in the API key or secret. The message indicates that the server agent could not authenticate with the Nimbusec API Server.
In both cases this error prevents all scans from taking place because the the api credentials are shared between all scanned domains in the config file.
no such file or directory
The configured directory could not be found.
permission denied
The configured directory was found but the permissions prevented the server agent from scanning its contents.
Status 403 Forbidden
This error occurs if the configured domain does not match any of the domains which are configured in your website security monitor account.
Note: www.example.com and example.com do not count as matching domains as the full domain name must be identical.