Home
FAQ & Troubleshooting
Server not responding
Some suggestions for troubleshooting if the server is not responding.

FAQ & Troubleshooting
- General FAQ
  This topic addresses general application questions.
- Troubleshooting tools
- Digital signature troubleshooting
- External traffic recorder not recording
  If your external device is configured correctly, AppScan's external login recorder and external traffic recorder will show the traffic sent from the device as you send it. This section offers suggestions if it does not.
- Insufficient disk space
- License troubleshooting
- Login troubleshooting
  Tips for troubleshooting session detection problems in Scan Configuration > Login Management view.
- Low virtual memory
- Multi-step operation troubleshooting
  Some suggestions for troubleshooting action-based multi-step operations.
- No URLs found
- Out-of-session troubleshooting
  Some suggestions for troubleshooting out-of-session issues.
- Postman Collection scan
  Some suggestions for troubleshooting a Postman Collection scan.
- Server not responding
  Some suggestions for troubleshooting if the server is not responding.
- Replacing unsigned extensions
  If you want to use an unsigned extension that you used with a previous version of AppScan, you can either elect to trust it, or see if a signed version is available to replace it with.
- Extended Support Mode
  Extended Support Mode logs all AppScan activity, for packing and sending to your support provider to help troubleshooting a problematic procedure.
- Changing the default browser
  You can configure AppScan to use a browser other than its built-in browser.
- Reporting false positive results
- Logs
  This section includes explanations of Scan Log messages (View > Scan Log).

Server not responding

Some suggestions for troubleshooting if the server is not responding.

Try the following troubleshooting steps:

Check that the Starting URL is correct, and that the Treat all paths as case-sensitive check box is deselected (see Starting URL and domains).
Verify that the site's server is up by browsing to the Starting URL in a browser.
Verify that Platform Authentication, Proxy, and AWS are configured correctly (see HTTP authentication, Communication and proxy and AWS authorization.
Decrease the number of simultaneous threads allowed to 1 (see Communication and proxy).