Scan Scheduling Errors

^{Last updated:}^2025-11-13

Purpose

This article explains error codes and messages.

Introduction

The Scan Scheduling Errors guide outlines the various error codes and message texts that may be displayed when a scan is not completed successfully in Outscan. These errors cover scenarios such as unreachable instances, unsupported targets, invalid credentials, scanner connectivity issues, and license limitations. By familiarizing yourself with these messages, you can diagnose failed or stalled scans more effectively, correct configuration issues promptly, and maintain the integrity of your vulnerability assessment workflows.

Error Messages

Error	Description
`Virtual Host(s) does not resolve to the target IP`	Scanner reports this error when you add virtual host(s) to add the target that cannot be resolved to the target IP.
`Instance XXX was not found`	The Amazon instance is not reachable by the scanner or does not exists anymore.
`Instance type XXX is not supported`	Instance type is not supported by the Outpost24 scanner, for example, because of Amazon scanning policy.
`Instance XXXX has no public IP`	Public IP missing from the instance.
`Error during web authentication procedure`	The web authentication procedure failed.
`Target is missing in the system`	The target no longer exists in the system.
`Report is missing in the system`	The report for SLS no longer exists.
`Maximum duration reached, terminated queued\|running scan`	Terminating a scan due to exceeding the given scan duration. `Terminated a running scan` - the scan started but did not complete within the given scan duration. `Terminating a queued scan`- the scan was queued but did not start within the given scan duration.
`Could not connect to scanner`	The system are unable to connect to the selected scanner. The Distribution section provides different levels of information about the scanner.
`Scans are already running against the targets`	This error message occurs when trying to start scans against targets that already have an on-going scan against them.
`Scanner not approved or inactive`	This is reported when the scanner is not approved or have been removed from the system. The Distribution section provides different levels of information about the scanner.
`Invalid AWS credentials`	Check if your Amazon Web Service (AWS) setup under the Integrations section is up to date.
`Could not start SLS, database missing`	Unable to start Scanning-Less Scanning (SLS), unable to connect to the fingerprint database. See Scanning-Less Scanning.
`Too many applications defined`	This error is related to the consumption of the license and can occur if the license limit is already consumed/reached.
`Scan/IP license limit exceeded`	The amount of targets to be scanned that does not use a license exceeds the number of remaining IPs for the license. See Account Settings and Create Targets.
`No seed URLs found`	None of the provided seed URLs are reachable from the scanner. A URL seed is a point from which a crawler begins to traverse a target.
`Seed URL is blacklisted`	The given URL is blacklisted and may not be scanned.
`No reachable seed URL`	None of the provided seed URLs are reachable from the scanner.
`Scan terminated`	The scan has terminated due to internal constraints. This happens when the scan times out or is being manually interrupted.
`Scan timeout`	Could not connect to the scanner. The Distribution section provides different levels of information about the scanner.
`Scan timeout`	Maximum duration reached, terminated scan.
`Scan warning`	The discovery scan did not find any assets.
`Scan failed`	Failed to run scan.
`Scan failed`	Failed to start scan.
`Scan failed`	Given target (<Selected target>) is not allowed to be scanned on selected scanner.
`Scan failed`	Failed to lookup IP for hostname.
`Scan Failed. Invalid Credentials`	The scanner lacks the correct credentials to access instance. Revisit settings and verify the credentials.
`Authentication failed (SSH)`	The authentication to the SSH service was unsuccessful. Either the username, password, or the key failed.
`Authentication failure`	error-message: `side auth setup timed out`
`Authentication failure`	error-message: `failed to wait for selenium-side-runner`
`Authentication failure`	error-message: `exit status 1 output: \| stdin:9: attempt to concatenate a nil value (local 'loginFormUrl')`
`No open ports found`	Scanned TCP range: def Scanned UDP range: def

This is a "FAST PUBLISH" article created directly from within the Outpost24 support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice.

_Copyright

_{© 2025 Outpost24® All rights reserved.}_{This document may only be redistributed unedited and unaltered. This document may be cited and referenced only if clearly crediting Outpost24® and this document as the source. Any other reproduction and redistribution in print or electronically is strictly prohibited without explicit permission.}

_Trademark

_{Outpost24® and OUTSCAN™ are trademarks of Outpost24® and its affiliated companies. All other brand names, product names or trademarks belong to their respective owners.}