AppScan Presence troubleshooting
Troubleshooting tasks for errors found when working with the AppScan Presence in an AppScan 360° environment..
Startup errors
| Error | Cause | Solution |
|---|---|---|
| Another instance of this AppScan Presence installation is already running. | An instance of AppScan Presence is already running from the same directory. |
|
Key errors
When you create a new presence in AppScan 360°, a unique file named
presence.key is generated and
included in the downloaded ZIP file. This key identifies the
Presence to your local AppScan 360°
instance.
In most cases, key issues are resolved by generating a new key through the AppScan 360° web console and placing it in the Presence directory.
| Error | Cause | Solution |
|---|---|---|
| Presence Key expired. | The key has reached its expiration limit or a new key was generated for this instance. | Renew the Presence key file via the AppScan 360° console and place it in the directory. |
| Presence Key not found. | The presence.key file is
missing from the directory. |
Download the key from your AppScan 360° server and place it in the Presence folder. |
| Presence Key invalid. | The presence.key file is
corrupted or belongs to a different AppScan 360°
environment. |
Generate and download a valid key file from the AppScan 360° website. |
| Presence was deleted. | The presence entry was removed from the AppScan 360°console. | Create and download a new AppScan Presence. |
| Presence Key in use. | A key file can only be used by one instance at a time. | Ensure the Presence isn't running elsewhere. If a process was aborted, wait 5 minutes for the AppScan 360°server to heartbeat the timeout before restarting. |
Connection errors
The machine running AppScan Presence must
have a stable connection to your AppScan 360°Server
URL (e.g., https://appscan360.yourdomain.com)
on port 443 (or your custom configured port).
If a proxy is required to reach the
AppScan 360°server, configure it in the
appsettings.json file in the
OutgoingProxyEndpoint section.
| Error | Cause | Solution |
|---|---|---|
| Failed to connect to the internal proxy... | Presence could not reach your designated outgoing proxy. | Verify proxy host/port settings in
appsettings.json under
OutgoingProxyEndpoint. |
| Unable to authenticate with outgoing proxy server. | Incorrect credentials for the proxy. | Update the username and password in the
OutgoingProxyEndpoint section of
appsettings.json |
| Error connecting to server. | Presence cannot reach the AppScan 360° on-prem server. |
1. Verify your AppScan 360°URL is reachable from the machine. 2. Ensure internal firewalls allow traffic to the AppScan 360°host. 3. Check for SSL inspection tools that might interfere with self-signed certificates. |
Tunnel startup errors
Ensure the Presence machine has direct network access to the application being tested.
| Error | Cause | Solution |
|---|---|---|
| Failed to connect to the internal proxy... | Presence could not reach the proxy used to talk to the target application. | Verify settings in the
InternalProxyEndpoint section of
appsettings.json. |
| Warning: received invalid HTTP response / status... | The Presence reached the Starting URL, but the app returned an error. | Verify the machine running the Presence has permission to access the target website. Check for local WAFs or IP whitelists. |
| Tunnel client failed to start. | The private site scanning process failed to initialize. | Consult the Presence logs in the installation directory and contact your internal AppScan 360°administrator. |
Miscellaneous errors
| Error | Cause | Solution |
|---|---|---|
| Failed to update required component. | Presence could not download updates from the AppScan 360° server. | Ensure the user account has Write permissions to the Presence directory and the system Temp folder. |