Website Service Management System WDCP series of Tutorials (iii)

Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall

We have installed a Web service management system WDCP, in the use of the process may appear in this or that kind of doubt, the following for everyone to organize the time out to facilitate everyone to learn. There are not understand can go to the Wdlinux forum to find relevant tutorials.

1, WDCP background access security settings that restrict domain name/IP access settings and removal methods

WDCP background defaults to 8080-port (can be modified)

But the powerful search engine, some even this also included in the

So, before people feedback, how to limit this backstage access

WDCP starting from 2.4, support this limitation, only need to operate in the background to support the routing of IP restrictions, and service-side domain access restrictions on two ways

Specifically as follows

In the background > system settings

Background access IP, refers to the restrictions can access the background of the routing ip, you can set an IP or IP segment

For example, my IP is fixed, such as 192.168.1.100, which can be set to 192.168.1.100, so that all other IP is not open

It can also be an IP segment

But if you are using ADSL Internet users, it is best not to set this, because the IP is often changed

You can use the background to access the domain name to set, also can achieve the effect

Background access to the domain name, refers to the background can open the domain name, the default is 8080 port, is all the domain name and server IP can be opened

For example, I want to limit to only one domain name that can be opened, such as admin.wdcp.cn

Then fill in the admin,wdcp.cn.

Save it

Later, you can use

http://admin.wdcp.cn:8080

To open, and with IP or other domain name, can not open

Purge method

How can I clear this setting if I set an error or the domain name is not available for some reason?

As long as the SSH login server

Implementation

sh/www/wdlinux/tools/wdcp_login_cbip.sh

Can

2, background upgrade, the site cannot open the solution

Some people encounter this problem, is in the background point upgrade, and then restart, the site will not open, the problem is not because of the upgrade cause, also said many times

Here's another explanation.

Background upgrade WDCP, will not affect the front-end site access and operation, this upgrade is only background upgrades, and the front-end site does not have a connection

What's the reason?

Most likely the reason is that the previous operation of the site (new | edit), such as the operation of the site, but because the service did not take effect, so did not find the problem

But when you reboot the machine, you find the problem.

Here, how to deal with?

Look in the background process, there are no 80 ports, as N+A environment, see there are no 80 and 882 ports

Can run in the background command runtime

Service Nginxd Restart

Service httpd Restart

See if there is no hint, according to the corresponding prompts to modify the

But SSH Rilian to the server to run the above command to see

Notes:

This problem, 99%, is due to the incorrect operation of the site's pseudo static rule reason or the pseudo rule file does not exist, and so on

So, check this out.

3, with IP also can not open the default home page

1 Determine if the installation is successful, mainly during the installation process, whether there are interrupts or error messages

2 Check for 80 ports

Can be system management port management to see if there are 80 ports

If you do not have 80 ports, find the corresponding nginxd or httpd in the Boot Service list page and click on the start of the following

Or

System Management Command Run Execute

Service Nginxd Restart

Service httpd Restart

Watch for tips

or use SSH to connect to the server to perform service nginxd restart

Service httpd Restart

Post the error message.

Description：

1 if the new installation will not open, should be not installed to complete

2 If it is not open after the new site or operation site, 99% is a pseudo static rule problem, that is, pseudo static rules cause nginx or Apache can not start

At this point, you can cancel the pseudo static of the site you just added, restart the service, and then check the pseudo static rule further

This article is excerpted from Wdlinux Forum, reproduced please specify!

Related reading:

Website Service Management System WDCP series of Tutorials (i)

Website Service Management System WDCP series of Tutorials (ii)