How do I troubleshoot scan errors?

The following section explains the scan errors you might encounter while using Crashtest Security Suite, what they mean, and how to troubleshoot them.

General error codes

Error Code	Description	What To Do
General Error	Unfortunately, the scanner ran into an error, and cannot determine what happened.	Restart the scan. If the error continues to occur, contact Veracode Technical Support.
Container Failed	This is an internal error. It means that the scanner failed but did not report the error for unknown reasons.	Restart the scan. If the error continues to occur, contact Veracode Technical Support.
Too many redirects	The scanner is allowed to redirect only ten times in a row. Once this amount is surpassed, the scanner cannot go through the redirection again.	Ensure there is no Infinite redirect loop. If it is not clear which URL redirects, contact Veracode Technical Support.

The scanner cannot reach the application

Error Code	Description	What To Do
URL not reachable / application not reachable	The scanner could not access the web application you are trying to scan.	Confirm that the required IP addresses are on your allowlist and that the application is reachable.
Connection Timeout	One or more connection timeouts related to the application you are trying to scan.	Ensure that it is configured in a stable staging environment that the scanner can access. If the load is too high for the system, you can reduce the throttling limit in the scan target preferences. Check if the required IP addresses are on your allowlist.
Connection Failed	Could not establish a reliable connection with the Scan Target, or the connection dropped throughout the scan.	Ensure that the required IP addresses are on your allowlist, and the application is reachable for an external scanner. Reduce the throttling limit for the frontend in the scan target preferences.

Log in problems

Error Code	Description	What To Do
HTTP Basic Auth Missing	Your system is using HTTP Basic Auth protection. However, the scanner has no credentials configured within the scan target preferences.	Configure the system authentication parameters and restart the scan.
HTTP Basic Auth failed	The scanner tried to use the provided HTTP Basic Auth credentials. However, the Log-In was not successful. This can be due to several reasons: Wrong credentials The scanner cannot access the system.	Ensure that the credentials you submitted are still valid. For this, ensure it is reachable from the outside. Restart the scan. If the error persists, contact Veracode Technical Support.

API problems

Error Code	Description	What To Do
URL Mismatch	The project URL from the frontend and the scanned URL from the Swagger file does not match.	Ensure that the project URL and the swagger file URL are the same. For OpenAPIs, the swagger file only recognizes the first URL.
API Specification parsing failed	While trying to parse the API specification, the scanner detected that it does not follow the Swagger 2.0 or OpenAPI 3.0 standard.	Ensure the API specification follows the OpenAPI 3.0 or Swagger 2.0 standard. Restart the scan.