Linux virtual host server wdcp system tutorial

After we have installed the network service management system wdcp in the wdcp system tutorial of the linux virtual host server, there may be a lot of questions about the problems encountered during use. The following are some of the common examples, if you have other questions, go to the wdlinux forum to find relevant tutorials. 1. How to migrate servers or websites? The best way is to shard the most quickly. 1. migrate from another environment to the wdcp environment. 2. migrate from the old wdcp to the new wdcp environment. There is no good way for the first one, basically, you need to manually create websites one by one (if there are many websites, you can also write a small program to import them). For the second one, the following describes how to install a new environment on the new server, that is, 2 such as one-click package and wdcp are packed on the original server, and the website directory/www/web, database directory/www/wdlinux/mysql/var/3 are downloaded through scp or, download the data to the new server, decompress it to the corresponding directory 4, and restart web service and mysql Service 5 to log on to the background, website Management> "update all site configurations" in the site list under normal circumstances, you can pay attention to the following points: 1/www/web is the default website directory, if you have to make changes, modify the 2/www/wdlinux/mysql/var/database directory according to the actual modification, which is also the default. If you have modified the directory, modify it according to the actual modification. 3. If mysql is packaged as the entire var directory The password of the database user has also changed. You need to use a small tool to forcibly change the password of wdcp and root. Otherwise, you cannot log on to the background or create a database 4. If there are static rules, this should be manually added to the new backend. If you have optimized or adjusted the WEB environment, you can back up the corresponding configuration file. mysql Database User Password Change wdcp database cannot be connected, if the system prompts "cannot connect to mysql, check whether mysql has been started and whether the user password is set correctly" forcibly modify the root password of mysql, when you forget the mysql password, run sh/www/wdlinux/tools/mysql_root_chg.sh and modify the Database Password sh/www/wdlinux/tools/mysql_wdcp_chg.sh2 of wdcp. After the background upgrade, when the website cannot be opened, someone may encounter this problem from time to time. After the website is upgraded in the background and restarted, the website cannot be opened. This problem is not caused by the upgrade, I have also said it many times. Here I will describe whether or not to upgrade wdcp in the background. It will affect the access and operation of the front-end website. This upgrade is only a background upgrade. What is the reason why it is not associated with the front-end website? The possible cause is that you have previously operated sites (New | edit) and other sites, but the Restart service does not take effect, so no problems are found, but after you restart the machine, the problem is found. How can this problem be solved? In the background process, there are no ports 80, such as N +, if there are no ports 80 and 88, you can run service nginxd restartservice httpd restart in the background command runner to see if there are any prompts, you can modify the settings as prompted, but you can connect to the server through ssh and run the above command. Note: The problem is caused by 99%, because the site's pseudo-static rules are operated incorrectly or the pseudo-Rule file does not exist, check whether the website is opened or the bound domain name cannot be opened or cannot be accessed, you can check the following methods or sequence. an IP address can be used to enable the following conditions, however, if you use a domain name to open the website, the default page is displayed. 1. Whether the site list contains the corresponding website information. 2. check whether there is any site configuration file in the background.-> System Management-> File Manager-> VM site. file (nginx, apache) Click in To Go To The vhost directory to see if there is a corresponding configuration file name. conf, such as wdlinux. conf3: check whether there are any files in the website directory. Choose "website management"> "website management"> "File Management" on the right of the corresponding website in the site list ", click to check whether the public_html directory and the public_html directory contain files. If you have uploaded your website files or programs to the public_html directory, go to the left-side Navigation Pane and choose System Management> restart web Services. or System Management-> execute service nginxd restartservice httpd restart in Command run. If not, the error message is pasted to indicate that it may not take effect. Generally, after restarting the service, you can use the IP address or fail to access the default homepage. 1. Check whether the installation is successful, check whether there are any interruptions or errors during the installation process. 2. Check whether port 80 exists. Choose System Management> port management. Check whether port 80 exists. If no port 80 exists, find the nginxd or httpd on the startup service list page, click Start or system management-> run the command to run the service nginxd restartservice httpd restart command. Check the prompt information or use ssh to connect to the server and run the service nginxd restartservice httpd restart command to describe the error message.: 1. If the website cannot be installed, it should not be installed. 2. If the website cannot be opened after the website is created or operated, 99% is a pseudo-static rule problem, that is, if the pseudo-static rules make nginx or apache unable to start, you can cancel the pseudo-static rules of the newly added site, restart the service, and then check the pseudo-static rules.