Solutions to common issues such as website not opening and database errors

1. "Hosting setup successful!" After uploading data, this content is displayed because our company has placed index.htm by default. You need to verify whether there are your own program files in the wwwroot directory; you can delete index.htm.

2. Congratulations, lanmp installed successfully! This page is the default page of wdcp. If accessing a domain displays this page, it means the accessed domain has not been bound to the site. This reminder will appear on vps cloud hosts.

3. Directory Listing Denied The problem is the error prompt that there is no default homepage in the root directory of the 2003 virtual host. Default homepages are generally index.htm index.php index.php default.aspx, etc. You need to check whether the website root directory wwwroot contains these default homepage documents. If your homepage has another name, you can go to the hosting control panel, find the homepage settings, and add your own homepage file name. Also note whether the website is stored in a subdirectory.

4. This problem is caused by the lack of a default homepage in the root directory of the 2008 virtual host. The problem is the same as above.

5. The Discuz!Database Error (1045)notconnect problem is a database connection failure in discuz. First, you can check whether the database can be logged in separately. If it can be logged in, check whether the configuration in your own program files is correct. If it cannot be logged in, go to the database management in the hosting control panel, directly click "Change mysql password", then try to click manage to see whether it can connect. If it still cannot be connected separately, please promptly submit a ticket for feedback.

Discuz!Database Error (1036) error "Table ‘common_syscache' is read only": the database table common_syscache is read-only. For the virtual host database, check whether the database exceeds the limit.

6. Unable to connect to the database Access denied for…… and Can’t Connect MySQL Server — the problems in the following two screenshots are both errors indicating the database cannot be connected. If the error message contains "Can’t Connect MySQL Server", it means the database cannot be connected. Check and analyze as in 5.

7. The error prompt Incompatible file format (incompatible file format) is caused by the PHP version. This problem occurs because shopex and phpweb, etc. require zend encryption. Adjusting the PHP version to 5.2 in the virtual host control panel can solve this problem.

8. In windows2008  iis7, the Not Found error means the domain is not bound, or the site is stopped and not started. You need to verify the binding or whether the site starts normally.

9. In windows2003 iis6, the Bad Request prompt appears; it means the domain is not bound. Check and verify the binding.

10. In iis7, when this display IIS7 welcome image screen prompt appears, it means the domain is not bound or the site is closed, so the default site page was accessed. You need to verify whether it is bound or whether the site starts normally.

11. For a virtual host of the linux system, the following error generally means there is no homepage file. When this error occurs, please check whether there is a homepage file under linux's wwwroot, or check whether the website is stored in a subdirectory. wwwroot is the program root directory; files must all be stored in the wwwroot directory.  

12. windows2003+iis6.0 website shows an unauthorized error.

401.3 You are not authorized to view this page

HTTP Error 401.3 - Unauthorized: Access is denied due to ACL settings on the requested resource.

Reference tutorial: http://www.west.cn/faq/list.asp?unid=596

13. Error caused by improper website permission settings in windows2008+iis7.

HTTP Error 401.3 - Unauthorized

Symptom 2:

HTTP Error 500.19 - Internal Server Error

Reference tutorial: http://www.west.cn/faq/list.asp?unid=847

14. Occurs in an apache environment

Internal Server Error

This is generally caused by a problem in the .htaccess configuration. Renaming or deleting .htaccess can usually restore it. You need to check and verify the .htaccess rule syntax and file format.

15. windows2008+iis7 system website shows a 404.17 - Not Found error

HTTP Error 404.17 - Not Found

The requested content appears to be a script, so it cannot be processed by the static file handler.

This is a problem of not having corresponding script execution permissions. If it is a virtual host, check and verify whether the asp.net program has not enabled script permissions. In the virtual host control panel, click asp.net version and select a version to enable support. Check whether directory protection is set; after directory protection, the directory no longer has script execution permissions. It may also be a compatibility problem; switch the program compatibility mode in the hosting control panel to 32-bit and try. For servers, check whether the corresponding script permissions were set when creating the site.

16. Occurs on windows2008+iis7 server

   HTTP Error 403.19 - Forbidden    

   The user configured for this application pool does not have sufficient permissions to run CGI applications.

Virtual hosts are generally already configured, so this error usually does not occur. For server users, the solution is: open the site, click "CGI", and change Impersonate user in Security to false. http://www.west.cn/faq/list.asp?unid=873 has instructions. Microsoft official instructions: http://support.microsoft.com/kb/942048/zh-cn. If virtual host users encounter it, please promptly submit a ticket.

17. ASP.NT program prompts: A potentially dangerous Request.Form value was detected from the client (xxxx).

This is a security feature of ASP.NET. Solution: modify the web.config configuration file to disable validateRequest

In the pages node of the web.config file, specify <pages validateRequest="false"/> or add it in the executing page.

If you are using asp.net4.0 version, you also need to add

<httpRuntime requestValidationMode="2.0" />

Since this is a security feature of ASP.NET, to reduce risk, it is recommended to contact the program provider to change the program code. Reference: http://www.360doc.com/content/10/0521/15/466494_28756529.shtml