This Black Friday was originally planned to get on the cars of Sparta and HostHatch, but after paying the bills for the previous two years of Black Friday, I found that there are too many chickens who are eating gray, except for a few hosts built by Tencent Cloud Hong Kong. In order to serve the station stably, the other 20 or so Taiwan basically only installed a SOCKS5 proxy server, which is really a waste..

I happened to see this post: Gullo 128M set of CF is very cool to make a website, is there a cheaper NAT VPS? The total price of 6 NAT hosts in different regions is 12 dollars per year, which is equivalent to only 2 dollars per machine, although each host Only 20 IPv4 ports are provided, and the IP is likely to be blocked, but it is cheap, so start playing decisively, and record some troubles in the Gullo control panel by the way

**1. Power on and obtain SSH login information**
The primary key of each Gullo NAT host is its internal network address, and the network segment is
10.10.10.1 to
10.10.255.255, SSH login information can be obtained through this intranet address, but it is rather convoluted. I will record the operations of each stage after buying the machine below, please refer to it yourself

① Wait for boot
A large part of Gullo’s machines are turned on manually by the boss (outrageous). I waited for nearly 30 hours for the NAT IPv4 128MB Bundle on Black Friday to be reviewed and turned on. After the boot is successful, you will receive an email like this in your registered mailbox:
Once you receive the login information, you can skip directly to the later part of the gameplay, but if you did not receive it or missed it, then follow me to the next step to investigate the SSH login information

② Log in to the VPS control panel
Address: httpssolusvm.gullo.me/
I found the username in the few SSH login information I sent (if you haven’t received any login information for a NAT machine, send a ticket), and the password needs to be retrieved by yourself to reset:
Return to the email to get the new password to log in:
③ Obtain the external network IPv4 address of the NAT machine (for NAT machines that have not received SSH login information)
Tool provided by Gullo: NAT IPv4 Port Calculator

Select the machine in the control panel, and use the above tools to query the IPv4 address of the external network, the 20 available ports and the SSH connection port through the internal network address:
④ Reset the password of the NAT machine (for the NAT machine that has not received the SSH login information)
Use the Serial Console to temporarily connect to the machine and choose a duration of 1 hour:
Get a temporary SSH login:
If you can’t connect here, try reinstalling the system of the NAT machine. If it still doesn’t work, send a work order. I have a German machine and the password is always wrong There are indeed many problems with cheap machines, but they are normal

After logging in, install it
passwd and reset the password:
yum -y install passwd # reset root user password passwd root
Then you can connect on other machines, take Linux as an example:
ssh -p $port[email protected]$host
**2. Hang a probe**
The NAT machine is not suitable for connecting to Zabbix. The Nezha probe is used here. For the construction tutorial, please refer to: The installation of the monitoring terminal built by the Nezha monitoring panel under CentOS7
Create a new machine in the background of the panel, copy the one-click installation command and execute it directly on the NAT host:
**3. Set up a SOCKS5 proxy server**
One-click script: CentOS7 installs GOST and starts HTTP and SOCKS5 proxy services with one click
Note that the port here must be one of your 20 available ports:
curl -s httpsgitee.com/senjianlu/one-click-scripts/raw/main/CentOS7%20 Next click to install %20GOST%20 and start %20HTTP%20 and %20SOCKS5%20 proxy services/install.| bash -s $proxy_port $proxy_username $proxy_password
Change the server to test whether the proxy is effective:
curl -x socks5username:[email protected]$host:$port httpip-api.com/json/?lang=zh-CN
Although the shared IPv4 address is sothat it can't be any moreit's okay for crawlers to use

**4. Build a website with Cloudflare**
Gullo provides each NAT host with a full-port IPv6 address. It is very convenient to build a website, just resolve the AAAA record in DNS directly. However, considering that some users do not have IPv6 addresses, if you really want to build a website, you need to set up a Cloudflare CDN for downlink

Here we take the default page of Nginx as an example. Since Nginx has enabled monitoring of IPv6 address access by default in a version after 1.3, it can be installed directly on the NAT machine without additional configuration:
yum -y install epel-release # Install Nginx yum -y install nginx # Start Nginx service nginx start
Get the IPv6 address of your NAT machine:

Resolved at Cloudflare's DNS, type
AAAA, SSL/TLS option
Flexible Let CF provide SSL certificates:
After a while, visit the page to test:
Then use a host with only an IPv4 address to access it:
IPv4 is supported, let alone IPv6, test it with ipv6-test:
Some computer rooms in Gullo have the problem of blocking the source of Cloudflare traffic (after practice, I found that at least the New York computer room is blocked), which will cause you to access the website using IPv6 without CF, but a 522 error will appear after setting it up. See this: Gullos hosting in NY blocking cloudflare?
You can also run the following command on the server to check whether the Cloudflare traffic is successfully returned to the source:
cat /var/log/nginx/access.log
The IPv6 address above belongs to Cloudflare, which means that the back-to-origin is successful

Finish.