Error Codes
When using Pages to develop projects, you may encounter various errors. If there are issues accessing your site, the page will display error codes and brief descriptions. These errors may involve project-level access issues or deployment-level status anomalies. This chapter provides specific solutions for common error situations.
Error Code List
Error Code | Description |
401 | Authentication information expired, please regenerate the preview link. |
404 | The site does not exist, please check your access address. |
410 | The deployment has been deleted, please redeploy. |
423 | The project is being deployed, please check back later. |
424 | Project deployment failed, please check the deployment log for more information. |
451 | The project has been banned, you cannot access the site temporarily. |
Error Code Details
401 - Authentication Information Expired
In the network environment of the Chinese mainland, when accessing Pages sites through the project domain or deployment domain, the preview link is valid for three hours. After expiration, accessing the link will return a 401 error. Please click the "Preview" button in the upper right corner of the "Project Overview" in the console to regenerate the preview link. It is recommended to add a custom domain for long-term access to the project.
404 - The Site Does Not Exist
Please confirm whether the project domain or deployment domain you are accessing is correct.
410 - The Deployment Has Been Deleted
When you delete a deployment record and then try to access the deployment domain, a 410 error will be returned. The deployment may have been deleted due to version update, resource optimization, or management requirements. Deleted deployments cannot be restored, but you can choose to create a new deployment.
423 - The Project Is Being Deployed
If the project is being deployed for the first time, please wait patiently until the deployment is complete before accessing it again. If it is not the first deployment, you can still access the project but will see the old version. Once the new deployment is complete, you can access the latest version.
424 - Deployment Failure
A 424 error will occur if the project fails to deploy due to errors during the build process or other reasons.
Common failure reasons include:
Build script error
Missing dependencies or version incompatibility
Resource limits (e.g., insufficient memory)
Please check the deployment log details of the corresponding project in the console to understand the specific reasons for failure. After fixing the issues, you can recreate the deployment.
451 - project has been banned
Due to violation of platform rules, such as involving illegal content (pornography, politics, etc.), the project has been banned and is inaccessible. Please ensure your content complies with laws and platform regulations. If you believe this is a misjudgment, please contact us through community or customer service for more information.
FAQs
Q: What should I do if I encountered error codes not mentioned above?
A: If you encounter error codes not covered in the documentation, record the error code and your steps, then contact us for help.
Q: How to prevent a 401 error caused by expired preview links?
A: The best method is to add a custom domain to your project. This ensures you can always access your project through that domain without relying on time-limited preview links.
Q: My project keeps showing a 423 error (deploying), but it seems to have been a long time. Is this normal?
A: Typically, the deployment process should complete within a few minutes. If you find the deployment time unusually long, it is recommended to check your deployment logs to see if there is any error information. If the problem persists, please contact us.