Skip to main content
Supported Regions:上海

FAQ

Access Issues​

What causes the 514 error when accessing static resources?​

Reason

The IP access frequency limit has been triggered. IP access frequency limiting is a total request count limit for static hosting resources, not a per-file request limit. When users access a webpage, the browser simultaneously requests all static resources on the page (HTML, CSS, JS, images, etc.), and each resource is counted in the IP's access frequency statistics.

For example, suppose your webpage contains:

  • 1 HTML file
  • 3 CSS files
  • 5 JS files
  • 10 image files

When users access it, 19 concurrent requests will be generated. If the IP access frequency limit is set to 2 QPS, then 17 requests will be rejected, returning a 514 error.

Solution

  1. Check the number of page resources

    • Use browser developer tools to view the number of network requests
    • Count the total number of resources loaded on the page

  2. Adjust QPS settings

    • Go to CloudBase Console → Environment Configuration → Security Management → Static Hosting Security Configuration
    • Set the QPS threshold to 1.5-2 times the number of page resources
    • For example: if a page has 20 resources, it is recommended to set QPS to 30-40

  3. Set by page type

    • Simple pages (5-10 resources): recommended QPS 20-30
    • Regular websites (15-30 resources): recommended QPS 50-80
    • Rich media pages (50+ resources): recommended QPS 100-200
Note

Setting too low a QPS limit will affect normal users' page loading experience. Please configure it reasonably according to actual business needs.

Build Issues​

Build fails with "command not found" error​

Reason

Missing necessary build tools or command spelling errors.

Solution

  • Check if the corresponding script is defined in package.json
  • Confirm that the build command is spelled correctly
  • Check if the required dependencies are installed

Build timeout​

Reason

Too many project dependencies or complex build process.

Solution

  • Enable build caching
  • Optimize dependencies and remove unnecessary packages
  • Use a faster package manager (such as pnpm)

Deployment Path Issues​

Page is blank or shows 404 after deployment​

Reason

Incorrect path configuration or routing mode issues.

Solution

  • Check if the base / publicPath configuration is correct
  • Single Page Applications (SPA) need to configure route redirection
  • Confirm that the output directory is configured correctly

Static resources 404​

Reason

Incorrect resource path reference.

Solution

  • Use relative paths to reference resources
  • Check if the base configuration matches the actual deployment path
  • Confirm that resource files have been correctly built to the output directory