One of the linux Virtual host server wdcp series tutorials

After we have installed the network service management system wdcp, there may be a lot of questions and problems arising during use. The following are some common examples. if you have other questions, go to the wdlinux forum to find related tutorials. 1. how to migrate servers or websites is the best and fastest... after we have installed the network service management system wdcp, there may be a lot of questions and problems arising during use. The following are some common examples. if you have other questions, go to the wdlinux forum to find related tutorials.
1 , How to migrate servers or websites the best and fastest
Classification
1. migrate data from another environment to the wdcp environment
2. migrate data 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 details
1. install a new environment on the new server, that is, one-click package and wdcp.
2. package the website directory/www/web, Database Directory/www/wdlinux/mysql/var/on the original server/
3. use scp or download to download the data to the new server and decompress it to the corresponding directory.
4. restart the web service and mysql service
5. log on to the backend, choose website management> "update all site configurations" in the site list"
Under normal circumstances
Notes:
1/www/web is the default website directory. if you have made any changes, you can modify the directory based on the actual modification.
2/www/wdlinux/mysql/var/Database Directory, which is also the default directory. if you have modified the Directory, modify it based on the actual directory.
3. if mysql is packaged in the entire var directory, the user password of the relevant database also changes. 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, manually add them to the new background.
5. if you have optimized or adjusted the WEB environment, you can back up the corresponding configuration file.
Mysql database user password modification
The wdcp database cannot be connected. if you log on to the background and prompt "cannot connect to mysql, check whether mysql is started and the user password is set correctly"
Force modify the mysql root password, which is useful when you forget the mysql password
Sh/www/wdlinux/tools/mysql_root_chg.sh
Run the following command to modify the database password of wdcp:
Sh/www/wdlinux/tools/mysql_wdcp_chg.sh
2 After background upgrade , The website cannot be opened.
Some people may encounter this problem from time to time, that is, after upgrading in the background, and then restarting, the website cannot be opened. this problem is not caused by the upgrade, but has been said many times.
Here is another example.
Upgrading wdcp in the background will not affect the access and operation of the front-end website. This upgrade is only an upgrade in the background and is not associated with the front-end website.
Why?
The possible cause is that you have previously operated sites (new | edit) and other operations on the site, but the restart service does not take effect, so no problems are found.
But after the machine is restarted, the problem is found.
How can this problem be solved?
In the background process, there are no ports 80. in the case of N + A, there are no ports 80 and 88.
You can run
Service nginxd restart
Service httpd restart
If there are no prompts, you can modify them as prompted.
But run the above Command in ssh to connect to the server.
Note:
This problem occurs because 99% of the reasons are due to incorrect operations on the site's pseudo-static rules, or the pseudo-rule file does not exist.
Therefore, check that
3 , New site or bound domain name cannot be opened or cannot be accessed
If the newly opened website or bound domain name cannot be opened or cannot be accessed, you can check the problem as follows or in sequence:
The following situations
An IP address can be used to open the website, but the default page is displayed when you use a domain name to open the website.
1. is there any website information in the site list?
2. check whether there are any site configuration files in the background-> System Management-> File Manager-> virtual host site files (nginx, apache) click in to enter the vhost directory, check whether the corresponding configuration file exists.
When the file name is used to create a site, the domain name is suffixed with. conf, for example, wdlinux. conf.
3. check whether there are any files in the website directory. choose "back-end"> "website management"> "file management" on the right of the website list. click "Go in" to check whether there are files in the public_html directory and the public_html directory.
You have uploaded your website files or programs to the directory of public_html.
4. Back-> System Management-> restart web services
Or
System Management-> command execution
Service nginxd restart
Service httpd restart
If not, paste the error message
Note: It may not take effect. Generally, you can restart the service.
The default homepage cannot be opened with the IP address.
1. check whether the installation is successful, mainly because there is an interruption or error message during the installation process.
2. check whether Port 80 exists.
Choose System Management> Port Management to check whether Port 80 exists.
If there is no port 80, find the corresponding nginxd or httpd in the startup service list page, and click Start
Or
System Management-> command execution
Service nginxd restart
Service httpd restart
Check the prompt.
Or use ssh to connect to the server and run service nginxd restart.
Service httpd restart
Paste the error message
Note:
1. if the installation is complete, the installation is not completed.
2. if the website cannot be opened after the website is created or operated, 99% is a pseudo static rule problem, that is, the pseudo static rule causes nginx or apache to fail to start.
In this case, you can cancel the pseudo-static state of the newly added site, restart the service, and then further check the pseudo-static rules.
This document is taken from the wdlinux Forum. For more information, see!