Error Codes
When using Pages to develop projects, you may encounter various errors. When there is a problem accessing your site, the page will display error codes and brief descriptions. These errors may involve project-level access issues or deployment-level status exceptions. This chapter will provide specific solutions for common error situations.
Error Code List
Status Code | Error Codes | Description |
401 | UNAUTHORIZED | Preview URL authentication information expired |
404 | NOT_FOUND | The site does not exist |
410 | DELETED | The deployment has been deleted |
413 | NODE_FUNCTION_PAYLOAD_TOO_LARGE | Node Functions request size exceeds limit |
423 | DEPLOYING | The project is being deployed |
424 | FAILED | Project deployment failed |
451 | UNAVAILABLE | Project has been banned |
500 | NODE_FUNCTION_RESPONSE_PAYLOAD_TOO_LARGE | Node Functions response size exceeds limit |
| INTERNAL_NODE_FUNCTION_ERROR | Internal Error in Node Functions |
| INTERNAL_NODE_FUNCTION_INVOCATION_FAILED | Internal invocation failure in Node Functions |
| INTERNAL_NODE_FUNCTION_NOT_READY | Node Functions initialization failed |
502 | NODE_FUNCTION_INVOCATION_FAILED | Node Functions call failed |
503 | NODE_FUNCTION_SERVICE_UNAVAILABLE | Node Functions service unavailable |
504 | NODE_FUNCTION_INVOCATION_TIMEOUT | Node Functions call timeout |
Error Code Details
401 - Authentication Information Expired UNAUTHORIZED
To ensure content compliance, accessing Pages sites via project domain name and deployment domain needs to follow the following rules:
1. The acceleration region of the project is set to "Chinese mainland availability zone" or "global availability zone (including Chinese mainland)".
1.1 Use the system-generated preview URL for access. The link validity period is 3 hours. A 401 error will be returned after timeout.
1.2 Regularly update the valid link via the "Preview" button in the upper right corner of the "Project Overview" interface on the console.
2. The acceleration region of the project is set to "global availability zone (excluding Chinese mainland)".
2.1 Non-Chinese mainland network environments can directly access it. A 401 error will be returned in Chinese mainland network environments.
It is recommended to bind Custom Domain to establish a stable access channel. No record filing is required in global availability zones (excluding Chinese mainland).
404 - Site Not Found NOT_FOUND
Please confirm whether the project domain or deployment domain you are accessing is correct.
410 - Deployment Deleted DELETED
When you delete a deployment record and then try again to access the deployment domain, a 410 error will be returned. The deployment may be deleted due to version update, resource optimization or management need. The deleted deployment cannot be recovered. You can choose to create a new deployment.
413 - Request Size Exceeds Limit NODE_FUNCTION_PAYLOAD_TOO_LARGE
Node Functions request event size exceeds limit. Try simplifying function input parameters. If related files are involved, upload files to Tencent Cloud COS.
423 - Project Is Being Deployed DEPLOYING
If the project is undergoing first deployment, wait patiently until after deployment is completed and then visit again. If it is not the first deployment, you can still access the project, but you will see the old version. After the new deployment is completed, the latest version can be accessed.
424 - Deployment Failed FAILED
A 424 error will occur if there are errors or other reasons during the project build process that cause deployment failure.
Common failure reasons include:
Build script error
Dependency miss or version incompatibility
Resource limits (such as insufficient memory)
Please view the detailed deployment record of the corresponding project in the console to obtain logs and understand the specific reason for failure. After fixing issues, you can recreate the deployment.
451 - Project Has Been Banned UNAVAILABLE
The project has been banned and cannot be accessed due to violation of platform rules, such as involving illegal content (involving pornography, politics, etc.). Please ensure that your content complies with laws and regulations and platform regulations. If you consider this a misjudgment, please contact us through the community or customer service to get more information.
500
Response Size Exceeds Limit NODE_FUNCTION_RESPONSE_PAYLOAD_TOO_LARGE
Node Functions response size exceeds limit. Adjust the function return value and try again after.
Internal Error INTERNAL_NODE_FUNCTION_ERROR
Internal error in Node Functions. Please retry later. If the issue remains unresolved, contact us or submit a ticket.
Function Internal Invocation Failed INTERNAL_NODE_FUNCTION_INVOCATION_FAILED
Node Functions execution failed. Please retry later. If the issue remains unresolved, contact us or submit a ticket.
Function Not Ready INTERNAL_NODE_FUNCTION_NOT_READY
Node Functions is not ready. Please retry later. If the issue remains unresolved, contact us or submit a ticket.
502 - Function Call Failed NODE_FUNCTION_INVOCATION_FAILED
Node Functions call failed, usually returned when your code execution encounters an error. Check the code according to the error information. For more information, view the function log in the console.
503 - Function Service Unavailable NODE_FUNCTION_SERVICE_UNAVAILABLE
Node Functions service unavailable. Check business code logic for memory leak.
504 - Function Call Timeout NODE_FUNCTION_INVOCATION_TIMEOUT
Node Functions call timeout. Check whether the execution duration of the business code exceeds the platform limit.
FAQs
Q: I encountered error codes not mentioned above. What should I do?
A: If you encounter error codes not covered in the document, record the error code and your steps, then contact us for help.
Q: How to prevent 401 errors caused by the expiration of the preview URL?
A: The best method is to add a custom domain to your project. This way, you can ensure you can always access your project through that domain, independent of the timeliness of the preview URL.
Q: My project has been displaying a 423 error (being deployed), but it seems to have lasted for a long time. Is this normal?
A: Normally, the deployment process should be completed within minutes. If you find the deployment time unusually long, suggest checking your deployment log to see if there is any error information. If the problem persists, contact us.
- Error Code List
- Error Code Details
- FAQs