WordPress's CDN automatically blocks traffic from China, causing our WordPress websites on domestic servers to be unable to install and update Themes and Plugins normally. Previously, we introduced using kill 429 to solve this. Today, we recommend a plugin with a higher success rate:
WP-China-Yes 
WP China Yes Plugin Introduction
WP China Yes is also a plugin developed by a Chinese developer, open-source and free. Its function is the same as kill 429, used to solve the pain point of domestic servers being unable to update and install WordPress Plugins and Themes normally. kill 429 is based on a forward proxy for WordPress resources, while WP-China-Yes is based on a reverse proxy for WordPress resources and uses Baidu Cloud CDN service, making it relatively more stable. The acceleration node set by WP China Yes directly accelerates all communication between your site and the WordPress headquarters server. The acceleration scope includes but is not limited to: resource downloads from the Plugin and Theme stores, product images, author avatars, Theme previews, etc...
WP China Yes Usage Method
1. Download from
WP official websiteor go to
GitHubdownload, then upload and install it in the website Admin Dashboard. 2. Activate the Plugin and use it normally. Because it uses CDN caching, you will see that some images in the Admin Dashboard cannot be displayed. When a user requests them, the CDN server starts requesting from the WP server, and then they will appear on the CDN server.
By inspecting with F12, it is found that the addresses of these images have been changed to the CDN address provided by the author.
Frequently Asked Questions
- Why is the speed so slow? – The acceleration node uses CDN cached data. For less popular resources with fewer visitors, the access speed will be much slower. If you encounter a timeout, please wait 10 minutes and try again. During this time, the CDN will automatically pull resources from the WordPress official server for use.
Author's release address: https://www.ibadboy.net/archives/3204.html
By inspecting with F12, it is found that the addresses of these images have been changed to the CDN address provided by the author.
Comments are closed
The comment function for this article is closed. If you have any questions, please feel free to contact us through other channels.