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

 Error codeDescriptionWhat to do
————————–————————–————————–————————–
General Error 
Unfortunately, our scanner ran into an error, and we cannot tell you exactly what happened. 1. Restart the scan
2. If the error continues to occur, please get in touch with our support at support@crashtest-security.com. 
————————–————————–————————–
General Error CodesContainer Failed This is an internal error. It means that the scanner had failed, but it did not report the error for unknown reasons. 1. Restart the scan 
2. If the error continues to occur, please get in touch with our support at support@crashtest-security.com. 
————————–————————–————————–
Too many redirects Our scanner is allowed to redirect only 10 times in a row. Once this amount is surpassed, the scanner is not able to go through the redirection again.  1. Make sure there is no Infinite redirect loop. 
2. If it is not clear which URL redirects, please get in touch with our support at support@crashtest-security.com. 
————————–————————–————————–————————–
URL not reachable  / Application not reachable Our scanner could not access the web application you are trying to scan.Please confirm that our IP Addresses are whitelisted and the application is reachable. 
————————–————————–————————–
The Scanner Cannot Reach The AppConnection Timeout While running the security scan, we experience one or several connection timeouts related to the application you are trying to scan.1. Please make sure that it is configured in a stable staging environment that the scanner can access. If the load was too high for the system, please reduce the throttling limit in the scan target preferences.
2. Check if our IPs are whitelisted.
————————–————————–————————–
Connection Failed While trying to run the scan, we could not establish a reliable connection with the Scan Target, or the connection dropped throughout the scan.Please ensure that our IP Addresses are whitelisted and the application is reachable for an external scanner. Reduce the throttling limit for the frontend in n the scan target preferences
————————–————————–————————–————————–
Log-In failed: While running the scan, we tried to use the provided login credentials. However, the Log-In was not successful. This can be due to several reasons: 1. Wrong Credentials: 2. Additional Credentials (e.g., Session Cookie) needed:
3. The scanner cannot access the system. 
1. Please make sure that the credentials you submitted are still valid 
2. Please configure the credentials 
3. Make sure it is reachable from the outside
4. Restart the scan after the previous steps
5. Contact support at support@crashtest-security.com with the following information:
– Screenshot / URL of Login
– Type of log-in use (technologies)
– The time during which you are reachable to test the log-in together
————————–————————–————————–
Log In ProblemsHTTP Basic Auth Missing We detected that your system is using HTTP Basic Auth protection. However, there are no credentials for our scanner configured within the scan target preferences.Please configure the system authentication parameters and restart the scan.
————————–————————–————————–
HTTP Basic Auth failed While running the scan, we 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. 1. Please make sure that the credentials you submitted are still valid
2. For this, please make sure it is reachable from the outside
3. Restart the scan. If the error persists, please get in touch with the support under support@crashtest-security.com. 


————————–————————–————————–————————–
API ProblemsURL MismatchThe project URL from the frontend, the scanned URL from the Swagger file does not match.1. Make sure that the project URL and the swagger file URL are the same
2. For OpenAPIs, the swagger file only recognizes the first URL
————————–————————–————————–
 API Specification parsing failed While trying to parse the API specification, our scanner detected that it does not follow the Swagger 2.0 or OpenAPI 3.0 standard.1. Make sure that the API specification follows the Open API 3.0 or Swagger 2.0 standard.
2. Restart the scan 
Scan for free now