Let the non-filing website run first.

Let the non-filing website run first.

Tian Yi ( [email protected] )

People in the technical innovation ability is not good, but in the setting of obstacles, tossing their own aspects of creativity but the pinnacle, such as the website record. To record is not a problem, after all, we are honest to do content. Anyone who has handled the record of the website is regarded as perilous undertaking: the filing process is complex, the requirements are cumbersome, and the approval time is long. The internet itself is won by speed, because there is no efficient approval, many opportunities are delayed.

website for the first time to record, server relocation room to record, change IP address also to record, prepare your sister Ah!

server put into the room, the system installed, the environment is also deployed, the hosting service fee also began to calculate, really can't wait for this damn record, then on the side of the record, while the station running it ! how to avoid being checked by the relevant departments to pull the cable? Here is a practical case to explain, for your reference and further improvement.

before you do the domain name resolution, bind the hosts file, test the site is normal, if there is no problem, change the port number of the Web service, such as from the default port to change to 8181. After you restart the Web, it is normal to use your browser to access the site. In general, we use nginx to do Web services, as to how to change the port, it is not difficult, here no longer verbose. Because the web port has changed, the scanning of the relevant agencies is not so sure that this is a Web.

renting a foreign VPS, the actual use of Hong Kong room good choice: faster than other places faster, and do not have to record. After purchasing a good VPS, Select the system for CentOS, connect to the system remotely, and then install the software haproxy. The installation process is easy and beginners can view the relevant documentation themselves.

Here's a basic idea to do this:

◎ Domain name resolution to a system that does not require filing

◎ agent turned to request to the system not filed

◎ non-filing system only accepts HTTP access requests from VPS

◎ users get data from VPS End

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/30/8A/wKiom1OoXTCxOLffAACdhidY-8Y667.jpg "title=" Beian.jpg "alt=" Wkiom1ooxtcxolffaacdhidy-8y667.jpg "/>

The complete configuration of one of my haproxy is as follows:

Global Log 127.0.0.1 Local3 Maxconn 65535 Chroot/usr/local/haproxy UID Nobody GID Nobody Daemon Nbproc 1 Pidfile/usr/local/haproxy/haproxy.pid Defaults Log 127.0.0.1 Local3 Mode http Option Httplog Option Httpclose Option Dontlognull Option Forwardfor Option Redispatch Retries 2 Maxconn 2000 Contimeout 5000 Clitimeout 50000 Srvtimeout 50000 Listen Web_ha Bind 0.0.0.0:9999 Mode http Transparent Stats Refresh 30s Stats Uri/haproxy-stats Stats Hide-version Stats Realm Haproxy\statistics Stats Auth Admin:sbbeian Frontend server_port80 Bind *:80 Mode http Option Httplog Log Global ACL www_namii Hdr_beg (host)-I www.namii.com #--------------------------------------------------------------------------------------# Use_backend www_namii_com If Www_namii #--------------------------------------------------------------------------------------# Backend www_namii_com Mode http Balance Source Cookie namii_www Insert Indirect nocache Option Httpchk HEAD http://www.namii.com/check.jsp http/1.0 Server s90-www 210.68.71.90:8181 weight 1 cookie s90-www check Inter rise 2 Fall 3

start The Haproxy service, and then the local hosts file to the VPS IP and website domain name, if access is not a problem, you can formally perform DNS resolution.

To further avoid being scanned by the relevant department's tools, you can restrict the source station to more stringent access. This allows only VPS and a small number of IPs to have direct access. Implementation in the configuration, is the nginx allow command. is limited to space and is no longer listed.

after making the above restrictions, find a machine that is not in the Nginx allow range to directly access the source station with the browser port, if access is forbidden, basically is what we expect. Then test allow allowed to test the machine, the normal appearance of the page content, is normal. Unblock the local hosts all relevant bindings, determine the domain name is correctly resolved to the VPS IP address, and then use any network of machines, in the browser input site URL , if the page display is normal, That will be able to withstand a temporary period of time.

This article is from the "Sery" blog, make sure to keep this source http://sery.blog.51cto.com/10037/1429986