This section describes only module-specific error codes. For details about universal error codes, please refer to Universal Error Codes.
1007900000 to 1007900200: 1007900000 + curl error codes. For details about curl error codes, please refer to Curl Error Codes.
1007900201 to 1007900999: reserved for RCP-specific error codes.
1007910000 to 1007910999: reserved for URPC-specific error codes.
Message
Unsupported protocol.
Description
The server does not support the protocol version.
Possible causes
The input protocol version is not supported by the server.
Solution
Specify a protocol version supported by the server.
Message
Failed initialization
Description
Initialization failed.
Possible causes
Memory resource allocation failed.
Solution
Release memory resources to ensure that the available memory space is sufficient.
Message
URL using bad/illegal format or missing URL.
Description
Incorrect URL format.
Possible causes
The format of the input URL is incorrect.
Solution
Specify a URL of the correct format.
Message
Couldn't resolve proxy name.
Description
The domain name of the proxy server cannot be resolved.
Possible causes
The URL of the proxy server is incorrect.
Solution
Specify a URL of the correct format.
Message
Couldn't resolve host name.
Description
The domain name of the server cannot be resolved.
Possible causes
The URL of the server is incorrect.
The network is disconnected.
Internal system error.
Abnormal DNS server.
Solution
Specify a URL of the correct format.
Verify that the network is available.
Collect extended fault information fields or logs and check the DNS-related fields dnsSockE, dnsCloseE, dnsConnE, dnsRecvE, and dnsSendE. If any of the preceding fields is not set to 0, an internal error occurs in the system. In this case, check whether the application control is blocked and whether the network is available.
Collect extended fault information fields or logs and check the following key fields:
connDns: If the value is all 0s, the request is sent to an unavailable server over Wi-Fi or cellular network, all DNS servers fail to be connected, and the DNS request cannot be sent.
tryDns: If the value is empty, no DNS server is available.
recvDns: If the DNS server in connDns does not match that in recvDns, no server returns the DNS result.
dnsStatus: The value 1 indicates that an IP address is available and the request is normal. The value 2 indicates that only the CNAME is obtained. The CNAME should be queried recursively or the backup server should be used to retry. The value 3 indicates that the packet is invalid.
If any of the preceding cases occurs, you are advised to check whether the Wi-Fi or cellular network is available and whether the DNS server managed by the network is normal.
Message
Couldn't connect to server.
Description
The server cannot be connected.
Possible causes
The network is disconnected.
Solution
Check the network connection.
Message
Weird server reply.
Description
This error code is reported if the data returned by the server is invalid.
Possible causes
The server encounters an error and returns data in non-HTTP format.
Solution
Check the server implementation.
Message
Access denied to remote resource.
Description
Access to remote resources was rejected.
Possible causes
The access to the specified resource is denied by the server.
Solution
Verify the request content.
Message
Error in the HTTP2 framing layer.
Description
An error occurred on the HTTP2 framing layer.
Possible causes
HTTP2 is not supported by the server.
Solution
Capture and analyze packets to check whether HTTP2 is supported by the server.
Message
Transferred a partial file.
Description
The data returned by the server is incomplete.
Possible causes
This problem is probable due to server implementation.
Solution
Check the server implementation.
Message
Failed writing received data to disk/application.
Description
Received data failed to be written to the disk/app process.
Possible causes
The downloaded data size exceeds the upper limit.
Solution
When the data size is too large, you are advised to call OnDataReceive instead.
Message
Upload failed (at start/before it took off).
Description
Upload failed.
Possible causes
The file is too large or the network is faulty. The server may reject the STOR command if FTP is used. The error buffer usually contains the reason from the server.
Solution
Check the file size and network status.
Message
Failed to open/read local data from file/application.
Description
Failed to open or read local data from a file or app.
Possible causes
The app does not have the data read permission.
Solution
Check the permissions granted to the app.
Message
Out of memory.
Description
The memory is insufficient.
Possible causes
The memory is insufficient.
Solution
Check the system memory.
Message
Timeout was reached.
Description
The operation timed out.
Possible causes
Based on the phase in which the timeout occurs, there are four types of timeouts:
For details, please refer to httpPhase. If the value of dns is 1 and the value of other phases is 0, the DNS phase times out. The possible causes of a timeout in the DNS phase are as follows:
For details, please refer to httpPhase. If the value of tcp is 1 and that of tls is 0, the TCP phase times out. The possible causes of a timeout in the TCP phase are as follows:
For details, please refer to httpPhase. If the value of tls is 1 and that of snd is 0, the TLS phase times out. The TLS phase timeout may be caused by an exception in the TCP flow during the TLS handshake.
For details, please refer to httpPhase. If the value of snd is 1 and that of rcv is 0, the sending phase times out. If the value of rcv is 1 and that of bdy is 0, the response header receiving phase times out. If the value of rcv is 1 and that of bdy is 1, the response body receiving phase times out. The possible causes of a timeout in the transmission phase are as follows:
Solution
Check the Internet connection, switch to a more stable network environment, and check whether the server is blocked. If the error code 1007900028 is displayed for multiple times, you are advised to close the session and create a session again.
Message
SSL connect error.
Description
SSL connection error.
Possible causes
There are two possible scenarios depending on whether an internal error occurs in the system:
An internal system error is reported. In the extended fault information field or log, the value of sslConnE is not 0. The possible cause is that a TCP flow exception (such as network switchover or interruption) occurs during the TLS handshake.
No internal system error is reported. In the extended fault information field or log, the value of sslConnE is 0. The possible cause is that the TCP flow is normal during the TLS handshake, but the cloud side rejects the TLS connection.
Solution
If the TLS connection fails, check whether the TLS configurations (tlsOptions and tlsRange attributes in SecurityConfiguration) of the client match those of the server. For example, check whether the TLS version of the client matches that of the server.
Message
Couldn't read a file:// file.
Description
Failed to read a file.
Possible causes
The file path is incorrect or the file does not exist.
The permission on the file is insufficient.
The path format is incorrect.
Solution
Ensure that the file path is correct and the file exists.
Ensure that the app process has the required operation permission on the file specified by the path.
Ensure that the file path format is correct.
Message
Operation was aborted by an application callback.
Description
The operation was stopped by a callback function of the app.
Possible causes
The callback function contains abnormal logic processing, such as infinite loops, abnormal interruption, and time-consuming synchronous operations.
Solution
Check all callback functions and ensure that they do not contain any abnormal or redundant processing logic.
Message
Failed binding local connection end.
Description
Local end binding failed.
Possible causes
The specified network port or IP address does not exist or is unavailable.
Solution
Ensure that the network port or IP address exist and are available.
Message
Number of redirects hit maximum amount.
Description
The number of redirections has reached the maximum.
Possible causes
Redirections are too frequent.
Solution
Check the server implementation.
Message
Malformed option provided in a setopt.
Description
The option format is incorrect.
Possible causes
The IP address format defined in StaticDnsRule or DynamicDnsRule is incorrect.
Solution
Ensure that the input parameter format of StaticDnsRule and DynamicDnsRule is correct.
Message
Server returned nothing (no headers, no data).
Description
Nothing returned from server.
Possible causes
This problem is due to server implementation.
Solution
Check the server implementation.
Message
Failed sending data to the peer.
Description
An error occurred while sending network data to the peer end.
Possible causes
The network is faulty.
Solution
Rectify the network connection error.
Message
Failure when receiving data from the peer.
Description
An error occurred while receiving network data from the peer end.
Possible causes
The network is faulty.
Solution
Rectify the network connection error.
Message
Problem with the local SSL certificate.
Description
The local SSL certificate is incorrect.
Possible causes
The SSL certificate format is incorrect.
Solution
Check the format of the SSL certificate.
Message
Couldn't use specified SSL cipher.
Description
Cannot use the specified SSL password.
Possible causes
The system does not support the cipher algorithm negotiated between the client and server.
Solution
Capture and analyze packets to check whether the cipher algorithm is supported.
Message
SSL peer certificate or SSH remote key was not OK.
Description
The SSL certificate or SSH key of the remote server is incorrect or invalid.
Possible causes
It is probable that the server identity verification fails because the certificate has expired.
The certificate is abnormal.
The CA set by the caller is abnormal.
Solution
Check the validity period of the certificate. The common causes are as follows: The certificate is a self-signed certificate, or the Portal (portal authentication) website is accessed.
Check the certificate issuer information of the accessed server.
Use a browser to access the IP address of the target server. On the certificate viewing page, check the issuer name in the field about issuers in the certificate details and check whether the issuer is a trusted organization.
Collect extended fault information fields or logs, check the issuers field, and determine whether the certificate issuer is returned by the server based on IssuerName.
Collect extended fault information fields or logs and check the following keywords:
tstGlbUsr and tstCurUsr: Trust the CA certificate by referring to Network Connection Security Configuration.
caFun: If a custom callback function is used, check whether the logic of the callback function is correct.
selfCaPath: If a custom CA folder is used, check whether the certificate in the custom CA folder matches the server certificate.
selfCaFile: If a custom certificate file is used, check the custom certificate file.
selfCaBlob: If the custom certificate content is used, check the custom certificate content.
Message
Unrecognized or bad HTTP Content or Transfer-Encoding.
Description
The HTTP encoding format cannot be identified or is incorrect.
Possible causes
The HTTP encoding format is incorrect.
Solution
Check the server implementation. Currently, only gzip encoding is supported.
Message
Maximum file size exceeded.
Description
The file size exceeded the maximum.
Possible causes
The value of content-length is inconsistent with the actual file size.
Solution
Check the server implementation.
Message
Send failed since rewinding of the data stream failed.
Description
Sending failed because the data flow failed to be rolled back.
Possible causes
Data is retransmitted due to a network exception.
Solution
Ensure that the network connection is normal.
Message
Disk full or allocation exceeded.
Description
The disk space of the server is insufficient.
Possible causes
The server disk is full.
Solution
Check the server disk space.
Message
Remote file already exists.
Description
The server finds that the uploaded file already exists.
Possible causes
The uploaded file already exists.
Solution
Check the server implementation.
Message
Problem with the SSL CA cert (path? access rights?).
Description
The SSL CA certificate does not exist or the access permission is not available.
Possible causes
The certificate does not exist or the access permission is not available.
Solution
Check whether the SSL CA certificate exists or the access permission is granted.
Message
Remote file not found.
Description
The file requested by the specified URL does not exist.
Possible causes
The file requested by the specified URL does not exist.
Solution
Check whether the file requested based on the specified URL exists.
Message
The max connection limit is reached.
Description
The number of connections has reached the upper limit.
Possible causes
The number of session connections has reached the upper limit. No connection is available.
Solution
Limit the number of concurrent requests that can be initiated at the same time, and free up a connection immediately after a request is complete.
Message
SSL public key does not match pinned public key.
Description
The SSL public key does not match the fixed public key.
Possible causes
The server certificate has been changed and no longer matches the client certificate.
The format of the client public key is incorrect.
Solution
Ensure that the public key format is correct.
Ensure that the public key used by the client is the same as that used by the server.
Message
Stream error in the HTTP/2 framing layer.
Description
A stream error occurred at the HTTP/2 layer.
Possible causes
The HTTP/2 stream is closed by the server.
The proxy server or firewall incorrectly intercepts or modifies the HTTP/2 stream.
Solution
Check the reason why the server closes the HTTP/2 stream.
Check the interception rules of the proxy server or firewall.
Message
An authentication function returned an error.
Description
Identity verification failed.
Possible causes
The specified identity verification field does not match that on the server.
Solution
Check whether the specified identity verification field matches that on the server.
Message
HTTP/3 error.
Description
An HTTP/3 error occurred.
Possible causes
The server or network does not support HTTP/3.
Solution
Use the HTTP of an earlier version to initiate the request.
Upgrade the HTTP protocol on the server.
Message
proxy handshake error.
Description
A proxy handshake error occurred.
Possible causes
The proxy server IP address or port number is incorrect.
Proxy authentication failed.
The proxy server rejected the connection.
Solution
Verify the proxy server settings.
Ensure that the proxy is available.
Check the proxy server logs to locate the error cause.
Message
A value or data field grew larger than allowed.
Description
The data length is out of range.
Possible causes
The requested or uploaded data size is too large, exceeding the upper limit of the client or server.
Solution
Use the streaming data transmission API.
Ensure that uploaded or downloaded data size is within the allowed range.
Message
Internal Error.
Description
Internal error.
Possible causes
An unknown error occurs in the system, and the request cannot be processed.
Solution
Restart the app or contact technical support for help.
Message
Method not supported.
Description
The method is not supported.
Possible causes
An unsupported API method or protocol is used.
Solution
Check the code or app to ensure that the method and protocol used are correct.
Message
Invalid content type.
Description
Invalid content type.
Possible causes
The request uses an unsupported data format or content type.
Solution
Ensure that the content type and data format in the request are correct.
Message
Proxy type not supported.
Description
The proxy type is not supported.
Possible causes
An unsupported proxy type is used.
Solution
Change the proxy type or disable the proxy, and try again.
Message
Get system proxy failed.
Description
Failed to obtain the system proxy.
Possible causes
The proxy is not configured correctly.
Solution
Ensure that the proxy is correctly configured.
Message
Sessions number reached limit.
Description
The number of sessions has reached the maximum.
Possible causes
Too many sessions have been created. A maximum of 1024 session instances can be created since version 5.1.0(18).
Solution
Reduce the number of sessions to 1024 or less.
Message
Session is closed.
Description
The session has been closed.
Possible causes
The session has been closed or is expired.
Solution
Open the session or create a new session, and try again.
Message
Request is canceled.
Description
The request has been canceled.
Possible causes
The request timed out or the Internet connection was interrupted.
Solution
Initiate the request again and ensure that the network connection is correct.
Message
The response is invalid.
Description
The response returned by the server does not comply with the expected format or specifications and cannot be properly parsed or processed by the client.
Possible causes
The parameters or format of the request sent by the client does not comply with server requirements. As a result, the server returns an error response.
Solution
Verify that the request sent by the client is correct, with all required parameters set correctly and the format as expected.
Message
Out of memory.
Description
The system cannot allocate memory.
Possible causes
The system memory is insufficient, the app occupies too much memory, or the app has memory leakage.
Solution
Check the memory usage of the app or system, or restart the app or system.
Message
Cannot open file.
Description
The file failed to be opened.
Possible causes
The app does not have the read and write permission on the file specified by the path.
Solution
Check whether the app has the read and write permission on the file specified by the path.
Message
Cannot create directory.
Description
An error occurred during directory creation.
Possible causes
The app does not have the permission to create a directory under this path.
Solution
Check whether the app has the permission to create a directory under this path.
Message
Cannot establish cellular link.
Description
When the cellular data connection is set up in cellular mode specified in PathPreference, the cellular data activation times out because requirements are not met.
Possible causes
A situation where cellular data cannot be activated occurs, for example, the user enables airplane mode or deactivates the SIM card.
Solution
Check the network settings and ensure that the cellular data activation conditions are met.
Message
File system IO error.
Description
File operation failed.
Possible causes
The file failed to be created, accessed, or deleted.
Solution
Check whether the file path is valid and whether the app has the permission to access the file path.
Message
Parameter error.
Description
Invalid parameter.
Possible causes
The input parameter does not meet the API specifications.
Solution
Ensure that the parameter settings are correct.
Message
Plaintext transmission is forbidden.
Description
Plaintext-based transmission is not allowed.
Possible causes
Plaintext-based HTTP transmission is not allowed for Remote Communication Kit.
Solution
Ensure that the plaintext-based HTTP transmission settings in the network_config.json file meets the service requirements.
Message
Urpc some error.
Description
An error occurred during URPC data transmission.
Possible causes
For details, please check URPC logs.
Solution
Check URPC logs for fault locating.
Message
Timeout was reached.
Description
The URPC request duration exceeds the timeout interval set in UrpcConnectConfiguration.
Possible causes
The request sending queue was blocked and the request failed to be sent.
An exception occurred on the server and the response cannot be sent properly.
Solution
For cause 1: Send the request again.
For cause 2: Restart the server.
Message
Request is cancel.
Description
The URPC request was canceled.
Possible causes
A URPC request was canceled because an associated resource was cleared.
Solution
Check whether resources are cleared before the request is completed.
Message
Urpc disconnect.
Description
The URPC was disconnected.
Possible causes
The network is disconnected.
Solution
Rectify the network connection error.
Message
Limit of request number.
Description
The number of URPC requests has reached the upper limit allowed by the server.
Possible causes
A large number of requests are sent without timely processing.
Solution
Check the request processing logic.
Message
Limit of request size.
Description
The URPC request size has reached the upper limit of the system memory.
Possible causes
The size of the request exceeds the upper limit.
Solution
Check the request processing logic.
Message
Resume transmit error.
Description
Data sending failed to be resumed in the resumable transmission scenario.
Possible causes
The transmission link is abnormal when resumable transmission is triggered.
Solution
Check logs on the request sender side.
Message
Urpc stub not found.
Description
No stub information is found when the cancel method is called.
Possible causes
The stub is destroyed too early.
Solution
Check whether the UrpcStub class is correctly declared and used.
Message
Deserialize failed.
Description
Data deserialization failed.
Possible causes
The data content is incorrect for deserialization.
Solution
Check logs on the request sender side.
Message
Function name error.
Description
The requested method name is incorrect.
Possible causes
The requested method name is incorrect.
Solution
Check the method name in the request.
Message
Urpc stub not found.
Description
UrpcStub is not correctly used.
Possible causes
UrpcStub is not correctly used.
Solution
Check whether the UrpcStub class is correctly declared and used.
