Skip to main content

HTTP Access Service Error Codes

tip

🌟 Are you experiencing HTTP access issues? Click here to consult Cloud Development Copilot for answers to your questions anytime. 📱 WeChat Cloud Development users, please choose the Mini Program Official Account to log in.

General Errors​

BAD_REQUEST​

The request data or parameter format is invalid. Please check whether the access domain name or Host is correctly filled, and whether the request headers and request body are properly configured.

INVALID_REQUEST​

The HTTP request does not conform to protocol specifications, or the request parameters are abnormal. Please check the request format.

ENV_ABNORMAL​

The environment status is abnormal. Please go to the console to check the environment status. If accessing CloudBase Run services, check whether the CloudBase Run service and version status are normal, and try creating a new service version.

INVALID_ENV​

Environment ID is invalid or the corresponding CloudBase environment was not found. Please check whether the access domain name is correct.

ENV_NOT_READY​

Environment resources are not ready yet. Please go to the console to check whether the environment initialization is complete, or wait a moment and try again.

ENV_FEATURE_NOT_CONFIGURED​

The target resource being accessed does not exist in the environment. Please check on the console whether the target resource exists, or wait a moment and try again.

INVALID_HOST​

Invalid or invalid hostname. Possible reasons include:

  1. The access domain name or Host is not correctly filled in;
  2. The requested domain name is neither a valid CloudBase default domain nor a bound custom domain;
  3. The requested domain is a custom domain, but it has not been configured with correct DNS resolution;
  4. The requested domain is a custom domain, but the modified DNS resolution has not yet taken effect.

You can check whether the domain name is filled in correctly and whether the correct DNS resolution is configured. If you have modified the DNS resolution, please check with your domain registrar whether the resolution has taken effect, or wait a moment and try again.

INVALID_PATH​

No matching forwarding rules were found. Please check the configuration of the HTTP access service forwarding rules.

SERVICE_FORBIDDEN​

The service is disabled. Possible reasons include:

  1. HTTP access path permissions are disabled, and service access is prohibited. If you want to enable the relevant permissions, please go to the CloudBase platform to configure;
  2. The service or environment status is abnormal. Please check whether the environment is in arrears or frozen;
  3. When using WeChat Cloud Run, there is a startup time of 1-3 minutes after the initial successful deployment of the service. You can wait and try again.
  4. When using WeChat Cloud Run Resource Reuse, it is carrying incorrect signature information.

HTTPSERVICE_NONACTIVATED​

The HTTP access service is not enabled. Please go to the CloudBase platform to enable the service. If the service is already enabled, please try again later.

EXCEED_RATELIMIT​

The request rate exceeds the QPS quota of your purchased plan. You can upgrade your plan to increase the QPS quota.

EXCEED_MAX_PAYLOAD_SIZE​

The request body size exceeds the limit. The request body size limits are as follows:

  1. The maximum request body size limit for Cloud Functions: 100KB for text-type request bodies, 6MB for other types;
  2. The maximum request body size for other requests is 100MB.

BAD_GATEWAY​

Gateway transmission error occurred. The request failed during forwarding to the target service or receiving a response from it. Please try again later. If this error occurs while accessing CloudBase Run services, check whether the CloudBase Run service is operating normally, or inspect the client or service logs.

ERR_ABORT_HANDLER​

This error can occur for various reasons. If it occurs during the invocation of a large model, try the following solutions:

  1. Ensure that requests using streaming output (Server-sent Event) include text/event-stream in the Accept header; otherwise, the request will time out after 60 seconds;
  2. Ensure that SSE (Server-sent Event) responses continuously return data to prevent the connection from being closed due to prolonged idleness (exceeding 60 seconds). You can maintain a heartbeat by sending comment lines (e.g., : ping) periodically over the SSE connection. For details, see: Event Stream Format.

If this error occurs in the response of CloudBase Run (Function-as-a-Service), try redeploying the hosted service to upgrade to the latest framework version with built-in SSE keepalive.

DEFAULT_DOMAIN_EXPIRED​

Due to security and compliance requirements, the default domain name is only available for development and testing purposes. The current default domain name has expired. Please click Renew on the CloudBase platform. The renewal is expected to take effect within 5 minutes. It is recommended to bind a custom domain name to avoid service availability risks caused by reduced accessibility of the platform's default domain name.

Authorization and Authentication Errors​

MISSING_CREDENTIALS​

The request header lacks the necessary authentication credentials. Possible reasons include:

  1. HTTP access authentication is enabled, but the request headers lack authentication credentials. See HTTP Access Authentication.
  2. Accessing via Open API without authentication credentials in the request headers. See Getting Started Guide.

INVALID_CREDENTIALS​

Authentication failed. Possible reasons include:

  1. With HTTP access authentication enabled, the user information in the request headers failed verification. See HTTP Access Authentication.
  2. When accessing via Open API, the user information in the request headers failed verification. See Getting Started Guide.

ACCESS_TOKEN_EXPIRED​

The authentication credentials in the request headers have expired. Please obtain new authentication credentials again.

ACCESS_TOKEN_INVALID​

The authentication credentials in the request headers are invalid. Please check the format of the authentication credentials or obtain new credentials again.

ACTION_FORBIDDEN​

The identity in the request headers lacks permission to perform the current operation. Please check whether the current identity has permission to execute this operation, or update the access policy associated with the current role in Cloud Development Platform - Extension Capabilities - Cloud Background Management - Permission Control - Policy Management.

UNSUPPORTED_AUTH_TYPE​

The request uses an unsupported authentication type. If accessing the HTTP API, check whether you are using AccessToken or Tencent Cloud Signature V3 authentication.

AUTHENTICATION_FAILED​

Authentication failed for the request. Please wait a moment and try again, or submit a ticket to us.

SERVICE_NOT_FOUND​

No corresponding Cloud Run service is found. Please check whether the service exists. For newly created services, you can wait 2 minutes and try again.

SERVICE_RESOURCE_NOT_FOUND​

No corresponding resources are found. Please check whether the service and version statuses are normal, or create a new version.

SERVICE_VERSION_NOT_FOUND​

No matching Cloud Run service version is found. The possible reasons are that no version has been created for the Cloud Run service, or the newly created version has not taken effect yet. You can wait a moment and try again.

SERVICE_ENDPOINT_NOT_FOUND​

No available upstream address is found for the Cloud Run service. The possible reason is that traffic for all versions of the Cloud Run service has been set to zero.

SERVICE_LB_STATUS_ABNORMAL​

The Cloud Run load balancer status is abnormal. Try creating a new version.

SERVICE_CHARGE_OVERDUE​

Service suspended due to overdue payment. Please top up promptly.

SERVICE_NOT_READY​

The Cloud Run service is in a not-ready state. Service instances may have been scaled down to 0 or the service version is undergoing cold start, preventing normal access. You can wait a moment and try again. To ensure the Cloud Run service maintains at least one instance, see Cloud Run Service Operation Modes and Scaling to adjust the service operation configuration.

SERVICE_TIMEOUT​

The Cloud Run service response timed out. You can check the Cloud Run service logs for troubleshooting, add latency log printing in critical code paths, and optimize time-consuming steps.

FUNCTION_NOT_FOUND​

No corresponding Cloud Function is found. Please check whether the Cloud Function exists.

FUNCTION_INVOCATION_FAILED​

The call to the Cloud Function has timed out or failed. Please verify whether the Cloud Function's logic has any issues.

Error messages may include the stack trace of the Cloud Function error. You can also query error messages via Cloud Function logs.

FUNCTION_QUALIFIER_NOT_FOUND​

The function version specified for access does not exist. Please check on the console whether the function version exists, or verify if the version specified in the request is correct.

FUNCTION_STATUS_ABNORMAL​

The function status is abnormal. Please check the function status on the console.

FUNCTION_TIME_LIMIT_EXCEEDED​

The function execution timed out. Please check whether the function contains time-consuming logic or adjust the function timeout setting on the console.

FUNCTION_MEMORY_LIMIT_EXCEEDED​

The function execution memory exceeds the limit. Please check the relevant logic in the function code or adjust the function memory configuration on the console.

FUNCTION_EXECUTE_FAIL​

Execution of the function failed. Please check whether the parameters for invoking the function are correct, troubleshoot the function logic, or query the error messages via Cloud Function logs.

FUNCTION_PARAM_INVALID​

An exception occurred with the function call parameters. Please check the function call parameters.

FUNCTION_EXCEED_RESOURCE_LIMIT​

The request frequency exceeds the provisioned concurrency of the function. Please reduce the request frequency or increase the provisioned concurrency of the function on the console.

STATIC_RESOURCE_NONACTIVATED​

Static website hosting service is not enabled. Please enable the service on the console.

STATIC_RESOURCE_TOO_MANY_REDIRECTS​

The request has been redirected too many times. Please check whether there is a redirect loop in the Static Hosting service configuration.

STATIC_RESOURCE_REQUESTS_FAILED​

Failed to access static hosting resources. Please try again later or submit a ticket to us.

STORAGE_EXCEED_AUTHORITY​

The user does not have permission to perform the corresponding operation on this object. Please check the bucket permission settings and whether the user identity associated with the current request has the required permissions.

OBJECT_NOT_EXIST​

The requested object does not exist, and the specified operation cannot be performed.

OBJECT_ALREADY_EXIST​

The object already exists, and the specified operation cannot be performed.

COS_ACTION_FAILED​

The object storage operation failed to execute. Please wait a moment and try again.

CDN_SIGNATURE_MISSING​

The signature for the current access URL is missing. Please check whether the URL carries the correct signature parameters.

CDN_INVALID_SIGNATURE​

The signature for the current access URL is incorrect. Please check whether the signature parameters carried by the URL are correct.

CDN_SIGNATURE_EXPIRED​

The signature for the current access URL has expired. Please regenerate the signature.

AI_MODEL_NOT_FOUND​

The specified model group was not found. Please check the request parameters and verify whether the corresponding group exists on the console. If it is a newly created group, please wait a moment and try again.

AI_MODEL_CONFIG_MISSING​

The required configurations for model invocation, such as the API Key, are missing. Please add the configurations on the console. After adding the configurations, please wait a moment and try again.

AI_MODEL_REQUEST_FAILED​

The large model invocation failed. See the target large model documentation to check whether the model invocation parameters are correct, or see Log Monitoring to query the details of the corresponding invocation.

AI_MODEL_DISABLED​

The model has been deactivated. Please check on the console whether the model is activated, or wait 2 minutes and try again.

EXCEED_CONCURRENT_REQUEST_LIMIT​

The large model invocation has exceeded the concurrency limit. Please wait a moment and try again, or submit a ticket to request a higher concurrency limit.

EXCEED_TOKEN_QUOTA_LIMIT​

The large model Token usage has exceeded the quota. Please purchase resource packages to increase the quota.

System Errors​

INTERNAL_REQUEST_FAIL​

Internal system request error. Please try again later or submit a ticket to us.

SYS_ERR​

Internal system error. Please submit a ticket to us.