Edge Developer Platform
  • Pages
    • Product Introduction
    • Quick Start
      • Importing a Git Repository
      • Starting From a Template
      • Direct Upload
    • Framework Guide
    • Project Guide
      • Project Management
      • edgeone.json
      • Configuring Cache
      • Error Codes
    • Build Guide
    • Deployment Guide
      • Overview
      • Create Deploys
      • Manage Deploys
      • Deploy Button
      • Use Github Actions
    • Domain Management
      • Overview
      • Custom Domain Name
      • Configuring an HTTPS Certificate
      • How to Configure a DNS CNAME Record
    • Pages Functions
    • KV Storage
    • Edge AI
    • API Token
    • EdgeOne CLI
    • Pages MCP
    • Integration Guide
      • Database
        • Supabase Integration
        • Pages KV Integration
      • Ecommerce
        • Shopify Integration
        • WooCommerce Integration
      • Payment
        • Stripe Integration
        • Integrating Paddle
      • CMS
        • WordPress Integration
        • Contentful Integration
        • Sanity Integration
      • Authentication
        • Supabase Integration
        • Clerk Integration
    • Best Practices
      • Use the Deepseek-R1 model to quickly build a conversational AI site
      • Building an Ecommerce Platform with WordPress + WooCommerce and GatsbyJS
      • Building a SaaS Site Using Supabase and Stripe
      • Building a Company Brand Site Quickly
      • How to Quickly Build a Blog Site
    • Migration Guides
      • Migrating from Vercel to EdgeOne Pages
      • Migrating from Cloudflare Pages to EdgeOne Pages
      • Migrating from Netlify to EdgeOne Pages
    • Troubleshooting
    • FAQs
    • Contact Us
    • Release Notes
Docs Overview/
Edge Developer Platform/
Pages/
Troubleshooting/

Troubleshooting

When using EdgeOne Pages, you may encounter various errors. This section focuses on the errors that may occur when operating the Pages console and their solutions.


Build and Deploy

Output Directory Exception

If the output directory is missing, empty, or invalid, the build process will raise an error (such as "Output directory build does not exist!"). To resolve this issue, you can try the following steps:
- Underwrite to set the correct output directory in "Project Setting - Build Deployment Configuration".
If the output directory is unclear, you can run the build command locally and view the output location of the build artifacts.


Build Log Shows "File Count Exceeds Project Limit"

The Pages project has a limit of 20,000 files. Please troubleshoot and try again after deploying.


Build Log Shows "File Size Exceeds the Limit"

Pages Project has a 25 MB size limit for single files. Please troubleshoot and try deploying again.


Direct Upload. after Successful Deployment, the Page Shows 404

Check if there is an index.html file in the root directory of the uploaded folder.



Domain Management

Incorrect DNS Record

After adding a DNS record with your domain provider, click "Verify" and see "Your record configuration is incorrect. Please ensure it points to the correct address." Since it takes time for DNS records to take effect, wait a few minutes and then verify again.
Note:
If the domain is hosted on Cloudflare, its root domain (such as example.com) cannot be added as a custom domain to Pages temporarily. It is recommend using a subdomain (such as sub.example.com).


Domain Name Already Exists on Other Platforms

When adding a domain, the message "The domain name already exists on other Tencent Cloud acceleration platforms. Delete it and then retry." appears. You can try to delete the domain on other platforms (Tencent Cloud CDN or EdgeOne), or switch to another second-level domain.


Platform Default Certificate Deployment Timeout

When generating the default certificate, the certificate status shows "deployment timeout". Troubleshoot whether there is a CAA record for the root domain of the added domain. Temporarily remove this record and re-add the CAA record after the certificate is generated.


How to Achieve Automatic Redirection From Non-Www to Www

You can configure the redirects field in edgeone.json. For details, see the Project Guide - edgeone.json.



Pages MCP

Deploy_html Tool Not Found

An error occurred after adding the MCP Server: {"error": "MCP error -32602: MCP error -32602: Tool deploy_html not found"}. Try restarting the editor.


MCP Server Status Exception: "Client Closed" Displayed

1.Try restarting the editor.
2.If it is the Windows system, run as administrator: Right-click the editor icon, select "Run as administrator" to exclude problems caused by insufficient permissions.



Technical Support

If the issue you encountered has no corresponding solution or you need more technical guidance about Pages, you can join our server EdgeOne Developers on Discord.