Application Real-Time Monitoring Service:Error codes for file transfer and CDN network speed test tasks

600

DNS resolution failed

The DNS query for the target domain failed. Possible causes: network connectivity issues, an invalid DNS server name, or an incorrect domain name. Verify the domain name and DNS server configuration.

601

Server connection failed

The TCP connection to the server timed out or failed. File transfer tasks support HTTP and FTP. Verify that the server is reachable and the port is open.

603

Unsupported protocol

A protocol other than HTTP or FTP was specified. File transfer tasks support only HTTP and FTP.

608

Server disconnected

The server terminated the connection unexpectedly, likely due to a server-side error or network interruption.

609

Connection reset

The connection was reset, typically due to poor quality and transmission rate of connections to the local Internet service provider (ISP). Check the network conditions between the monitoring node and the target server.

610

SSL certificate expired

The server SSL certificate has expired. Renew the certificate to restore HTTPS access. System error code: 12037.

611

SSL certificate domain mismatch

The domain in the SSL certificate does not match the requested domain. For example, the request targets www.123.com, but the certificate is issued for www.124.com. System error code: 12038.

612

Client certificate required

The server requires a client SSL certificate, but none is installed on the monitoring node. System error code: 12044.

623

Untrusted CA

The SSL certificate was not issued by a trusted certificate authority (CA). System error code: 12045.

624

SSL certificate error

A general SSL certificate error occurred. System error code: 12055.

625

Invalid SSL certificate

The SSL certificate is invalid. System error code: 12169.

634

SSL algorithm mismatch

The client and server could not agree on an SSL protocol version. This can occur when the SSL protocol version was not selected, or when Windows XP does not support the required SSL/TLS version.

639

SSL certificate not revoked

The SSL certificate revocation check returned an inconclusive result. System error code: 12056.

640

SSL certificate canceled

The SSL certificate has been canceled. System error code: 12170.

641

Client authorization not configured

Client authorization is required but not configured. System error code: 12046.

642

Fortezza authentication required

The server requires Fortezza authentication. System error code: 12054.

643

Security check failure

A function call failed due to a security check. System error code: 12171.

644

Insecure SSL content

The response contains a mix of secure and insecure content. System error code: 12041.

645

SSL certificate revoked

The SSL certificate has been revoked by the issuing CA. System error code: 12057.

646

SSL library load failure

The SSL library failed to load. System error code: 12157.

647

SSL connection failed

The SSL/TLS handshake failed during connection setup. Check the server SSL configuration and supported protocol versions. cURL error code: 35 (CURLE_SSL_CONNECT_ERROR).

648

Remote SSL certificate invalid

The remote server SSL certificate failed verification. The certificate may be self-signed, expired, or issued for a different domain. cURL error code: 51 (CURLE_PEER_FAILED_VERIFICATION).

649

SSL encryption engine not found

The specified SSL encryption engine was not found. cURL error code: 53 (CURLE_SSL_ENGINE_NOTFOUND).

650

SSL engine default failure

The SSL engine could not be set as the default. cURL error code: 54 (CURLE_SSL_ENGINE_SETFAILED).

651

Local client certificate error

An error occurred with the local client certificate. The certificate file may be missing, unreadable, or in an unsupported format. cURL error code: 58 (CURLE_SSL_CERTPROBLEM).

652

Unavailable key

The specified SSL key is unavailable or cannot be read. cURL error code: 59 (CURLE_SSL_CIPHER).

653

CA certificate cannot be used as peer certificate

The peer certificate could not be verified with the provided CA certificate. Make sure the CA certificate bundle is up to date. cURL error code: 60 (CURLE_SSL_CACERT).

654

Unrecognizable transfer code

The server returned a response with an unrecognizable transfer code. cURL error code: 61 (CURLE_BAD_CONTENT_ENCODING).

655

FTP SSL request error

An error occurred while requesting SSL for the FTP connection. cURL error code: 64 (CURLE_USE_SSL_FAILED).

656

SSL engine initialization failed

The SSL engine failed to initialize. cURL error code: 66 (CURLE_SSL_ENGINE_INITFAILED).

657

SSL certificate read error

The SSL certificate file could not be read. Verify the file path and permissions. cURL error code: 77 (CURLE_SSL_CACERT_BADFILE).

658

SSL connection shutdown failed

The SSL connection could not be terminated cleanly. cURL error code: 80 (CURLE_SSL_SHUTDOWN_FAILED).

659

CRL load failure

The certificate revocation list (CRL) could not be loaded. cURL error code: 82 (CURLE_SSL_CRL_BADFILE).

660

Certificate issuer check failed

The issuer of the SSL certificate could not be verified. cURL error code: 83 (CURLE_SSL_ISSUER_ERROR).

661

Key mismatch

The SSL pinned public key did not match. cURL error code: 90 (CURLE_SSL_PINNEDPUBKEYNOTMATCH).

662

Invalid CA

The CA certificate is not valid for this connection. cURL error code: 91 (CURLE_SSL_INVALIDCERTSTATUS).

602

FTP logon denied

During an FTP-based download test, the FTP server did not return the 230 status code (successful login) after receiving the username and password. Verify the credentials and check that the FTP account is active.

604

Passive FTP not supported

The FTP server does not support passive mode. File transfer tasks use only passive FTP. Contact the server administrator to enable passive mode.

614

File does not exist

The specified file does not exist on the FTP server. Verify the file path.

615

File open failure

The file on the FTP server could not be opened. Check file permissions.

616

File not found

The specified file was not found on the FTP server. Verify the file path and name.

617

Working path error

The working directory for the upload or download task could not be set. Verify the directory path and permissions on the FTP server.

618

Invalid password

The FTP logon password is incorrect. Verify the password.

619

Invalid username

The FTP logon username is incorrect. Verify the username.

620

Operation incomplete

The FTP session ended before the operation completed, possibly due to a server-side timeout or network interruption.

621

File upload failed

The file could not be uploaded to the FTP server. Check write permissions and available disk space on the server.

622

FTP logon failed

The FTP logon request was rejected. Verify the username, password, and server access policy.

605

Redirection failed (TCP error)

Before downloading, Synthetic Monitoring checks whether the URL is configured for redirection. If redirection is configured, the destination URL is first parsed and then threads are enabled. A TCP error occurred while resolving the redirect destination, possibly due to DNS resolution failure or a TCP connection issue.

606

Invalid URL

The specified URL is malformed. Verify the URL syntax.

626

Redirection disabled

The server attempted a redirect, but redirection is disabled in the task configuration. Enable redirection or update the URL to point directly to the target resource.

631

HTTP to HTTPS redirect failed

The redirect from HTTP to HTTPS failed. This is a known issue on Windows Server 2012.

633

Too many redirects

The number of redirects exceeded the default limit of 10. The system stopped following redirects to prevent an infinite loop. Reduce the redirect chain or update the URL to point to the final destination.

635

Redirect confirmation required

The redirect requires user confirmation. This corresponds to the WinINet error ERROR_HTTP_REDIRECT_NEEDS_CONFIRMATION (12168).

607

Protocol not supported

The HTTP protocol is not supported by this test type. For example, the URL http://www.baidu.com/ uses the HTTP protocol. Verify that the URL uses the correct protocol.

627

String verification failed

The expected string was not found in the response header after the download completed. Verify that the server returns the expected header values.

628

Invalid response data

The response data from the server could not be parsed. The response may be corrupted or in an unexpected format.

629

Incomplete download

The downloaded file is smaller than expected. If the response includes a Content-Length header, the actual file size is less than the declared size. If no Content-Length header is present, the file size is less than the size specified in the task configuration.

630

Download timeout

The download did not complete within the allowed time. This may indicate insufficient bandwidth or a slow server response.

632

MD5 hash mismatch

The MD5 hash of the downloaded file does not match the expected hash configured for the test. The file may have been altered or corrupted during transfer.

613

Request timeout

The server did not respond after the client sent a request. Check the server availability and response time.

636

Server response timeout (upload)

After a file was uploaded over HTTP, the server did not return a response. The upload may have succeeded, but the server failed to acknowledge it.

637

Request data send failure

The HTTP connection was established, but the request data could not be sent, likely due to a network interruption after the TCP handshake.

638

SSL handshake failed (HTTPS)

For HTTPS connections, the SSL handshake failed and the request data was not sent. Verify the server SSL configuration and certificate validity.