Skip to main content

HTTP Access Service Error Codes

tip

🌟 Experiencing HTTP access issues? Click here to consult Cloud Development Copilot, which is ready to answer your questions anytime. 📱 WeChat CloudBase users please log in via Mini Program Official Account.

General Errors​

BAD_REQUEST​

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

ENV_ABNORMAL​

The environment is in an abnormal state. Try creating a new service version.

INVALID_ENV_ID​

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

INVALID_HOST​

Invalid or illegal 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 the correct DNS resolution is not configured;
  4. The requested domain is a custom domain, but the modified DNS resolution has not taken effect yet.

You can check whether the domain name is correctly filled in and whether the correct DNS resolution is configured. If you have modified the DNS resolution, please check with your domain registrar to see if 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. To enable the relevant permissions, please go to the CloudBase Platform to operate;
  2. The service or environment is in an abnormal state; please check whether the environment has overdue payments or is frozen;
  3. When using WeChat Cloud Run, after the initial successful deployment of the service, there is a startup time of 1-3 minutes; you can wait and try again.
  4. When using WeChat Cloud Run Resource Reuse, incorrect signature information was carried.

HTTPSERVICE_NONACTIVATED​

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

EXCEED_RATELIMIT​

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

EXCEED_MAX_PAYLOAD_SIZE​

The request body size exceeds the limit. The cloud function request body has exceeded the maximum size limit (100 KB for text, 6 MB for other types).

BAD_GATEWAY​

An error occurred during gateway transmission. Currently, this error code only occurs in WeChat Cloud Run scenarios. The request failed while being forwarded to the WeChat Cloud Run service or while receiving a response from it. Please check whether the WeChat Cloud Run service load is normal, or check the client or service logs.

EXCEED_CONCURRENT_REQUEST_LIMIT​

API calls exceed the concurrency limit. Please wait a moment and try again, or submit a ticket to request an increase in concurrency.

EXCEED_TOKEN_QUOTA_LIMIT​

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

ERR_ABORT_HANDLER​

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

  1. Ensure that requests using streaming output (Server-sent Events) include text/event-stream in the Accept request header; otherwise, the request will time out after 60 seconds;
  2. Ensure that the SSE (Server-sent Events) response continuously returns data to prevent the connection from being closed due to prolonged idleness (exceeding 60 seconds). You can implement regular heartbeat keep-alive in the SSE connection using comment lines, such as : ping. For details, see: Event stream format.

If this error occurs in the response of Cloud Run (Function-based), try re-deploying the hosted service to upgrade to the latest framework version with built-in SSE keep-alive.

Authentication and Authorization Errors​

MISSING_CREDENTIALS​

The request header lacks necessary authentication information. Possible reasons include:

  1. HTTP access authentication is enabled, but the request header lacks authentication information. Please refer to HTTP Access Authentication.
  2. Using Open API access, but the request header lacks authentication information. Please refer to the Access Guide.

INVALID_CREDENTIALS​

Authentication failed. Possible reasons include:

  1. When HTTP access authentication is enabled, the user information in the request header failed verification. Please refer to HTTP Access Authentication.
  2. Using Open API access, the user information in the request header failed verification. Please refer to the Access Guide.

ACCESS_TOKEN_EXPIRED​

The authentication information in the request header has expired. Please obtain new authentication credentials.

ACCESS_TOKEN_INVALID​

The authentication information in the request header is invalid. Please check the format of the authentication credentials or obtain new authentication information.

ACTION_FORBIDDEN​

The corresponding identity in the request header does not have permission to perform the current operation. Please check whether the current identity has permission to perform this operation, or update the access policy associated with the current role in Cloud Development Platform - Extension Capabilities - Cloud Backend Management - Permission Control - Policy Management.

AUTHENTICATION_FAILED​

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

SERVICE_NOT_FOUND​

No corresponding cloud hosting service was found. Please verify whether the service exists.

SERVICE_RESOURCE_NOT_FOUND​

The corresponding resource was not found. Please check whether the service and version status are normal, or create a new version.

SERVICE_VERSION_NOT_FOUND​

No matching cloud hosting service version was found. Possible reasons include that no version of the cloud hosting service has been created, or the newly created version has not yet taken effect. Please wait a moment and try again.

SERVICE_ENDPOINT_NOT_FOUND​

No available upstream address was found for the cloud hosting service. This may be because the traffic for all versions of the cloud hosting service has been set to zero.

SERVICE_LB_STATUS_ABNORMAL​

The load balancing status of the cloud hosting service is abnormal. You can try creating a new version.

SERVICE_CHARGE_OVERDUE​

Service suspended due to overdue payment. Please recharge promptly.

SERVICE_NOT_READY​

The upstream cloud hosting service is not ready. Service nodes may have been scaled down to 0, or the service version is in the cold start phase and cannot provide normal access yet. Please wait a moment and try again.

SERVICE_TIMEOUT​

The call to the cloud hosting service timed out. You can check the cloud hosting service logs to troubleshoot.

FUNCTION_NOT_FOUND​

No corresponding cloud function was found. Please check whether the cloud function exists.

FUNCTION_INVOCATION_FAILED​

The call to the cloud function timed out or failed. Please check whether there is an issue with the cloud function's own logic.

Error messages may contain the stack trace of cloud function errors. You can also check error information via Cloud Function Logs.

STATIC_RESOURCE_NONACTIVATED​

The static website hosting service is not enabled. Please go to the CloudBase Console to enable the service.

STATIC_RESOURCE_TOO_MANY_REDIRECTS​

Too many redirects. Please check the static hosting service configuration for redirect loops.

STATIC_RESOURCE_REQUESTS_FAILED​

Request for static hosting resources failed. Please try again later or submit a support ticket to us.

System Errors​

INTERNAL_REQUEST_FAIL​

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

SYS_ERR​

Internal system error. Please submit a support ticket to us.