Avoiding Pitfalls in Building Your Own CDN

Feb 21, 202266

AI Translation

This post is translated from Chinese into English through AI.View Original

AI-generated summary

Recently, the server logs showed more 502 errors than 200, possibly due to blocking a large number of spiders and non-browser access. During the testing phase of adding a new node today, the CDN service was found to have abnormal status. It was discovered that the firewall had blocked the server IP and the non-browser interception of the Baota firewall. Since my IP has always been on the firewall whitelist, I didn't notice it. The solution is to add the server IP to the firewall whitelist, disable the non-browser interception of the Baota firewall, and check the ping latency between the node server and the source server.

Recently, I found that the server logs had more 502 status codes than 200. I think it may be because I have blocked a large number of spiders and non-browser accesses.

Then today, during the testing phase of adding a new node, I found that the CDN service was in an abnormal state. After investigation, I discovered that the firewall had blocked the server IP and the non-browser interception of the Baota firewall.

Since my IP has always been in the firewall whitelist, I didn't notice it.

Add the server IP to the firewall whitelist.
Disable the non-browser interception of the Baota firewall.
Check the ping latency between the node server and the origin server.