Website is inaccessible and displays an error message

Error message

Cause

Solution

The web server is configured to not list the contents of this directory

A valid default index page is not configured in the website root directory of the Cloud Web Hosting instance that runs Windows.

To resolve this issue, configure a valid index page. For more information, see Set a default index page for a website.

The requested URL /xxx.html was not found on this server

The pseudo-static settings are incorrect.

For more information, see Configure pseudo-static settings on virtual hosts or lightweight cloud servers.

Cannot find <handler>scriptProcessor in <fastCGI> application

Cloud Web Hosting instances that run Windows do not support PHP programs.

Change the operating system or upgrade the Cloud Web Hosting instance. You can use one of the following solutions:

• Change the operating system to Linux. Changing the OS does not trigger data migration. Before you change the OS, you must back up your site and database data. For more information, see Change the operating system of a host and Back up and restore data.

• Upgrade the Cloud Web Hosting instance to a lightweight cloud server Elite Edition instance, which supports PHP frameworks. For more information, see Upgrade a Cloud Web Hosting instance.

The page cannot be accessed because the related configuration data for the page is invalid

The index.asp file specified in the web.config file of the website program is the same as the default index page set in the Cloud Web Hosting console.

Keep only one index page file.

Internal Server Error

• The .htaccess file contains incorrect code.

• File permissions are incorrect.

• The PHP file configuration is incorrect.

• The PHP version is too low.

• Server resources are overloaded.

The solution varies based on the cause. For more information, see "Internal Server Error" is reported when you access a website on a Cloud Web Hosting instance.

500 - Internal Server Error

• Cause 1: The program has an error.

• Cause 2: The index.asp file specified in the web.config file of the website program is the same as the default index page set in the Cloud Web Hosting console.

• Cause 3: Cloud Web Hosting does not support a specific feature of the program.

• For Cause 1, enable the ASP error troubleshooting feature. For more information, see Enable detailed ASP error messages.

• For Cause 2, keep only one index page file.

• For Cause 3, change your Cloud Web Hosting instance or purchase a different cloud server that supports the required feature.

HTTP Error 500.19 - Internal Server Error. The requested page cannot be accessed because the related configuration data for the page is invalid.

Cannot add duplicate collection entry of type 'add' with unique key attribute 'value' set to 'index.asp'

The default index page is already set to index.asp in the Cloud Web Hosting console. Internet Information Services (IIS) receives the same value from the web.config file of the remote site, which causes a conflict.

Based on the content displayed in the configuration source, identify the line number that causes the error in the web.config file. Then, delete the corresponding line of code from the web.config file.

The page cannot be displayed because an internal program error occurred

The web.config file is a site-level file. Cloud Web Hosting does not support virtual subdirectories. If a web.config file exists in a nested subdirectory on a Cloud Web Hosting instance that runs Windows, an error is reported when you access the website.

Rename or delete the web.config file in the nested subdirectory on the Cloud Web Hosting instance that runs Windows. Then, access the website again. The website should function as expected.

Forbidden or HTTP Error 403.14 - Forbidden

• The default index page file, such as index.php, is not uploaded to the website root directory. For security reasons, Cloud Web Hosting does not allow directory listing. As a result, a 403 error is reported when you access the website.

• Access is denied in the website program settings. This also causes a 403 error when you access the website.

Solutions to the "403 Forbidden" error when you access a Cloud Web Hosting website

This website is temporarily inaccessible because the host has expired

• The Cloud Web Hosting instance has expired.

• You recently performed one of the following operations but did not resolve the domain name to the new host's IP address, or you resolved the domain name to the IP addresses of both the old and new hosts:

  • Upgraded the Cloud Web Hosting instance.

  • Changed the operating system of the Cloud Web Hosting instance.

  • Migrated the website to a newly purchased Cloud Web Hosting instance.

"The website is temporarily inaccessible because the host has expired" error is reported when you access the website

Sorry! This website may be inaccessible for the following reasons

• Cause 1: The domain name resolution is incorrect.

• Cause 2: Duplicate domain name resolution settings exist.

• Cause 3: The domain name is not attached to the host.

• Cause 4: You are using the host's IP address to access the site.

• Cause 5: The site is stopped.

• For Cause 1, check whether the domain name is resolved to the IP address of the host.

• For Cause 2, check whether the same domain name is resolved to two host IP addresses.

• For Cause 3, the website administrator must log on to the HiChina host control panel to attach the domain name. If you have an Alibaba Cloud account, you can log on to the Cloud Web Hosting console to attach the domain name. For more information, see Attach a domain name.

• For Cause 4, Cloud Web Hosting does not support site access using the host's IP address. You must use the domain name to access the site. 

• For Cause 5, the website administrator must log on to the HiChina host control panel to start the site. If you have an Alibaba Cloud account, you can log on to the Cloud Web Hosting console to start the site. For more information, see Start a site.

This page is temporarily inaccessible. To find the cause and solution, you can submit a ticket.

This issue usually occurs because the site status is Stopped.

Start the site. Wait 2 to 5 minutes, and then confirm that the site is accessible.

Friendly reminder: This website is temporarily inaccessible

The domain name has not completed its ICP filing, or the domain name is not managed by Alibaba Cloud.

• Complete the ICP filing for the domain name or transfer the ICP filing to Alibaba Cloud. For more information, see ICP filing process.

  Important

  After the ICP filing is successful, the system requires up to 6 hours to refresh. If you have just received a notification from the Ministry of Industry and Information Technology (MIIT) that your ICP filing is successful but the block page is still displayed, wait 6 hours and try again.

• If your top-level domain has an ICP filing with another hosting provider and you use a second-level domain to point to a HiChina or Alibaba Cloud host, you must also transfer the ICP filing information of your top-level domain to Alibaba Cloud for the site to be accessible.

has more than 'max_user_connections' active connections

The MySQL database of a Cloud Web Hosting instance allows a maximum of 80 connections per user. If this limit is exceeded, an error similar to this one is reported.

• Temporary solution: Shut down the site. Wait for a period of time, and then start the site and check whether it is accessible.

• Permanent solution:

  • Optimize your program. Database sessions that are invoked in the program must be closed promptly.

  • If this connection limit does not meet your needs, consider using Elastic Compute Service (ECS) and ApsaraDB RDS to resolve the issue.

Fatal error:class "Model" not found in ~runtime.php

The website program has an abnormal file named ~runtime.php. This file is a cache file that is compiled from the templates of many third-party PHP website programs. It is automatically created by the website program and stored in the `Runtime` directory by default. If you use a pattern extension, the name of the compiled cache file may change.

For example, if you are using the REST pattern, the generated compiled cache file is named ~rest_runtime.php.

Rename the ~runtime.php file to ~runtime.php.bak and then delete the file. Then, confirm that the website is accessible.

The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, *** and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log

• The PHP version is incorrect.

• The permissions are incorrect.

• The .htaccess file has a syntax error.

• The program has an error or is missing files.

"Internal Server Error" is reported when you access a website on a Cloud Web Hosting instance that runs Linux

Fatal error: Incompatible file format: The encoded file has format major ID 1, whereas the Loader expects

When you access a PHP site on a Cloud Web Hosting instance that runs Linux, this error occurs because the Zend Optimizer encryption component is configured only for PHP 5.2. If your program requires the Zend Optimizer encryption component, using a PHP version other than 5.2 causes this error. For more information, see What common extension components are configured by default for hosts that run Linux?.

In the host management console, change the current PHP version to 5.2. For more information, see Change the PHP version.

Warning: chmod() has been disabled for security reasons

The chmod function is disabled on the Cloud Web Hosting instance or lightweight cloud server.

Enable the PHP function chmod setting. For more information, see Set PHP.INI parameters.

An error occurred on the server when processing the URL. Please contact the system administrator.

If you are the system administrator please click here to find out more about this error.

When you access an ASP page on a Cloud Web Hosting instance, the instance can send detailed ASP errors to the browser. This feature is controlled by the ASP debugging properties of the IIS site and is disabled by default.

Enable the Send detailed ASP error messages to client feature. Then, refresh the browser to view the website program's error message. Adjust the program based on the error message. For more information, see Enable detailed ASP error messages.

class not found Runtime/~runtime.php

The cache directory for a ThinkPHP site is Runtime. If the site is migrated from another server to a Cloud Web Hosting instance, the original directory information may be retained, which can cause access exceptions.

Delete or rename this directory and then access the website again. The Runtime directory is regenerated, and access returns to normal.