Troubleshooting

If you think you've found a bug or just need more help, please reach out at https://fuzzinghero.com/contact.

Importing Collections

My Collection Doesn't Get Created At All

Fuzzing Hero supports Postman collections, OpenAPI 3.1, and Swagger 2.0 compatible JSON and YAML formats. If you are experiencing issues with importing a collection, please verify that your file is compatible with one of these formats.

My Collection Gets Created But It Doesn't Look Right

Make sure that your collection has a default server URL defined, such as {{baseUrl}} in Postman, or a servers[0].url defined in OpenAPI spec.

If you are using Postman and your collection has variables, try to include the variables in the collection. Fuzzing Hero will try to inherit the variables from the collection during imports.

Failed Health Checks

My App is Returning 401 Status Codes

Authentication is required and either not configured on the scan settings or the credentials have expired. Try configuring this and ensuring that the credentials are valid.

My App Should Respond with 2xx But It Responds with 4xx or 5xx

Check the request(s) in the collection that are causing issues. Review to make sure that the URI, method, headers, any any parameters are configured correctly. Try adjusting the protocol from Auto to HTTP/1.1 or HTTP/2. Use the Test button to try to verify changes.

No Connectivity or Timeouts

Review the Best Practices to ensure that you've allow listed Fuzzing Hero IPs through any network security controls such as WAFs.

You may also want to check that the base URI defined in your collection is correct and is something that can be accessed publicly.

My App is Responding with 429 Status Codes

Consider adjusting the scan configuration's rate limit. A slower value of 5 or 10 requests per second should give the service some breathing room, but you can adjust this value as needed.

Additionally, consider if allow listing Fuzzing Hero endpoints on any WAF or security appliances: Best Practices.