Video Tutorial
YouTube playback address: https://youtu.be/NbruiJShUCE
Tools Used
CDN Optimization Tool: https://bulianglin.com/archives/cdn.html
Node Speed Test Tool: https://github.com/bulianglin/demo
Search Engine: https://fofa.info
Temporary Email: http://24mail.chacuo.net
Installing X-UI
bash <(curl -Ls https://raw.githubusercontent.com/vaxilu/x-ui/master/install.sh)
Search Syntax Reference
Domestic Reverse Proxy IP: server=="cloudflare" && port=="80" && header="Forbidden" && country=="CN"
Exclude CF: asn!="13335" && asn!="209242"
Alibaba Cloud: server=="cloudflare" && asn=="45102"
Oracle Korea: server=="cloudflare" && asn=="31898" && country=="KR"
Bandwagon Host: server=="cloudflare" && asn=="25820"
Related Tutorials for this Issue:
https://youtu.be/r2WunEyqMeQ
https://youtu.be/Azj8-1rdF-o
https://youtu.be/x6B5JEwXSEg
https://youtu.be/uKXVXaa5_YI
https://youtu.be/fHJDvJIptts
Video Transcript (Ignore)
In this issue, we will teach you how to obtain an unlimited number of reverse proxy CF IPs for free and optimize the reverse proxy IPs for your junk VPS to improve speed. If you have set up a reality node, you need to be careful to prevent reverse proxy CF and avoid having your traffic stolen. As we all know, WS nodes can use Cloudflare's CDN and optimize your junk nodes with preferred IPs. If you are interested in the specific principles, you can review the eighth episode of the node setup series, which provides detailed explanations. There are some magical IPs that reverse proxy Cloudflare, allowing us to optimize our nodes by selecting these reverse proxy CF IPs, effectively improving our node speed. This is not something new. I explained this type of IP in a video last August. If you are interested, you can review it. As for why they reverse proxy CF, I guess there are certain businesses that require this operation, but they don't know that it can be exploited if proper restrictions are not in place. For example, if you set up a reality node and the destination is a CF-protected website, it may also be exploited and become one of the many reverse proxy CF IPs, resulting in stolen traffic. We will discuss this issue in detail later. First, let's teach you how to obtain reverse proxy CF IPs from any region and optimize them in the fastest way possible to obtain a large number of speed-boosting nodes, giving you the effect of using 1000 nodes with just one node. Note that these are reverse proxy CF IPs that have been optimized. CF IPs are not good for China Telecom users no matter how much you optimize them, and many people are optimizing CF IPs, so the speed is extremely unstable. You will probably agree with me on this. Now let's demonstrate the complete process of optimizing reverse proxy IPs. First, set up a WS node and use this command to install the XUI panel: bash <(curl -Ls https://raw.githubusercontent.com/vaxilu/x-ui/master/install.sh). After the installation is complete, access the panel by entering your IP address followed by port 54321. Use the default username and password "admin" to log in. Create a vmess+ws node, change the port to 80, and set the transmission to WS. Set any path you like. After creating the node, import it into v2rayN. Test the speed by pressing Ctrl+T. If there is a speed indication, it means it can be used normally. Next, apply the CDN. Before that, you need to point your domain to CF. I won't spend time demonstrating these basic operations. Click on your domain to enter the DNS settings. Follow my instructions to add a record. Fill in the name as you like, for example, I filled in "V IP Address" and enter your VPS IP address, which is equivalent to accessing v.huaqianle.cf, which is equivalent to accessing my VPS. Click save. The CF operation is complete. Then change the node address to the website you just set, v.huaqianle.cf, and set any name. Now this node is like a CDN with CF. Test the speed again, and you will see a significant improvement. However, it is still not stable, especially for China Telecom users. Even with optimized IPs, it is difficult to have a stable experience with scientific internet access. So we can optimize the IPs that reverse proxy CF. Before that, let me copy a node. Open it for editing. Apply TLS to the node and change the port to 443. Set the transmission to TLS. Click OK. Test the speed again. It should indicate that it can be used normally. Now we have two nodes with CDN applied. We can proceed to the next step. Let's start by obtaining the IPs that reverse proxy CF. We will use the tool fofa, which has appeared frequently before. With some search syntax, you can find many websites you want. You can find detailed syntax rules at this location. You can refer to the syntax rules I provided to search for IPs that reverse proxy CF. This rule means searching for servers with CF, port 80, HTTP header containing "forbidden", and IP location in China. Paste it into the search box and press enter to search. Under this condition, we found over 2000 independent IPs. Click here to download. It prompts us to log in first. Click on "Register". Registration requires email verification. You can find some temporary email services online. Enter the required information for registration and click "Register". Go to your email to check the activation email. If you haven't received the email after waiting for more than 1 minute, it is recommended to try again with a different node IP. Click on the link to activate. Enter the account and password you just registered to log in. After successful login, click the download button again. Free users have over 2000 export quotas. Enter the quantity you want to export and click "Export". Go to the personal center to download. For CSV format files, it is recommended to open them with Excel for easy copying. These are the IPs we need. Most of them are reverse proxy CF IPs. Now you can optimize them in your preferred way or follow the method I provided to ensure the fastest optimization. First, open this website to access the CDN optimization tool. If it redirects to the homepage, you can search for "CDN" here to enter the best CDN optimization tool. Copy the link of the node with CDN applied. Note that the address bar should be your domain name, not the IP address. Paste the node link here. Select "Custom" as the CDN provider. If there is no response on the webpage after selecting, it may be because the webpage content has not fully loaded. Copy the IPs we just exported and paste them here. Select the number of nodes to extract as needed. We exported 2000 records earlier, but there may be duplicates, which will be automatically removed. If you don't know the exact quantity, you can enter a large number, such as 3000, to ensure that each one will be obtained. Click "Extract Nodes". All the node links of the reverse proxy IPs will be generated below. In addition, this webpage is purely frontend JavaScript scripting. I am not interested in collecting everyone's node information. If you have concerns, you can right-click and view the webpage source code to copy it and use it locally. Now let's follow the video demonstration. Download the node speed test tool I made earlier. I also fixed the 401 unauthorized issue a few days ago. After downloading, extract it and run the nodesCatch executable file in the directory. Copy all the nodes generated by the webpage and paste them into the tool. After deduplication, there are still over 700 nodes with latency indications, which means they can be used and only the speed is a problem. Now let's test the download speed. I won't test all of them in the video demonstration. You can copy the nodes with good speed to other proxy tools for use. You can see that the node address has been changed to the reverse proxy CF IP, and the disguised domain name has been filled in with our CF domain name. The speed test is also successful, indicating that it can be used normally. This is the effect of applying optimized reverse proxy CF IPs to improve node speed. You don't have to focus on optimizing CF's own IPs all the time. Moreover, this optimization method allows you to achieve the effect of using 1000 nodes with just one node. This method can also be used for TLS nodes. First, copy the TLS nodes on port 443 to the web tool. The IPs are still the 2000 IPs we downloaded earlier. Click "Extract Nodes". Copy the generated nodes and paste them into the speed test tool. Although we filtered the IPs in fofa for port 80 reverse proxy, some IPs reverse proxy both port 80 and port 443. This allows us to quickly select IPs with good speed. This is the case when port 443 is available but port 80 is not. Now let's talk about reality nodes set up on port 443. Incorrect reality configurations can cause your VPS to become one of the many public reverse proxy CF IPs, serving as a relay accelerator for others' nodes. These IPs that are not available on port 80 but available on port 443 are likely to be reality nodes. I set up a regular reality node on port 443, and the speed test is successful. I can use it normally. Copy the node's IP address. Open the TLS node with CF applied. Paste the IP into the address bar. Fill in the disguised domain name with the original domain name from the address bar. After modification, you can see that the node's IP and port are the IP and port of our reality node. However, this node is actually a VMESS+WS+TLS node and has nothing to do with reality. Test the speed again, and you will be surprised to find that it has speed. This means the node can be used normally, and the latency is also good. My reality node has become one of the many public reverse proxy CF IPs. This is not what I want. The reason for this problem is that my reality node's destination is a CF-protected website. You can see that the target website of my node is speedtest, which is protected by CF. When reality receives data that is not for reality, it directly forwards the data to the destination. Since speedtest is protected by CF, reality can find the address of our VPS through the domain name we set on CF and forward the vmess data to our VPS. Therefore, if the target website of your reality node is a CF-protected website, it may cause your VPS to be used as a relay accelerator for others' nodes. To check if the target website is protected by CF, you can add this path to the domain name. If you see this page, it means the website is protected by CF. For example, my website is protected by CF, so accessing this URL will also show this page. If the target website of your reality node has this page, it is recommended to change it and avoid becoming a relay accelerator for others.