Configure the handling actions following the interception of hacker attacks.

1. Return Settings

Set the return status and content after an attack is intercepted.

It is recommended to set the return status to: 403, and the return content to: standard error message.

Friendly Reminder: When "Custom Content" is selected, if you need to display an authorization password input box, please include {{secretrkey}} in the custom content.

Special Note:

On IIS, if the return status is not set to "200," no information will be returned because IIS enforces handling unless the IIS configuration is changed.

How to Change: IIS -> Error Pages -> Edit Feature Settings -> Change Error Response to "Detailed Errors."

2. Intelligent Blocking

Intelligently intercept frequent hacker attacks. During the blocking period, the IP will be unable to access the server.

Recommended Settings: 

Attack Freq: 30 attempts/60 seconds

Block Time: 30 minutes

Firewall Block: Enable

3. Authorization Password

After interception, entering this password will add the user's IP to the authorization list, preventing further interception for a specified period.

4. CDN Penetration

Bypass CDN to obtain the client's real IP address. Addresses the issue of being unable to retrieve the client's real IP when a website uses CDN.

By default, when a website uses CDN, the real client IP cannot be obtained, and only the CDN node's IP is visible. Enabling this option allows obtaining the client's real IP.

Friendly Reminder: Some high-anonymity proxies may not reveal the real client IP. Due to their technical principles, no company can obtain the real client IP for such proxies.

5. Disable Web Compression

Send a notification to the administrator upon interception.

Disable web page compression functions (such as gzip, deflate, br, etc.). Resolves the issue where PHP independently enables web page compression, preventing effective filtering of output data.

6. Notification

Send a notification to the administrator upon interception.