# After the update, Chinese management interface is bad

**URL:** <https://meta.discourse.org/t/after-the-update-chinese-management-interface-is-bad/363862>\
**Category:** Product Support\
**Created:** [April 28, 2025, 7:43pm UTC](https://meta.discourse.org/t/after-the-update-chinese-management-interface-is-bad/363862 "2025-04-28T19:43:33Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![co\_choa](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/co_choa/32/456777_2.png) [@co\_choa](https://meta.discourse.org/u/co_choa)\
**Post date:** [April 29, 2025, 4:15am UTC](https://meta.discourse.org/t/after-the-update-chinese-management-interface-is-bad/363862/10 "2025-04-29T04:15:14Z")

</div>

The underlying cause of this issue is as follows:

Within the administrator’s simplified Chinese link, there exists an instance of “aaa.”

Consequently, my Cloudflare WAF (Web Application Firewall) rule set includes a restriction that blocks “aaa.”

![image](https://global.discourse-cdn.com/meta/optimized/4X/1/e/1/1e1ac3f58c5f791736ce96a4c6ade96027d822cc_2_690x69.png)

 ![The image shows a user interface for creating a filter in a web traffic analysis tool, where you can specify a URI path and select options to include or exclude data based on its contents. (由 AI 生成标题)](https://global.discourse-cdn.com/meta/original/4X/f/e/0/fe079bbbeff8c57b224af7a7dd7130c0aeaae83b.png)

As a result, Cloudflare’s security measures are triggered, leading to the frontend requests being outright blocked before reaching the backend.

Although it may seem quite peculiar, this is essentially the situation: 😦

---

_[View the full topic](https://meta.discourse.org/t/after-the-update-chinese-management-interface-is-bad/363862)._