WP Panel v1.4.0 is officially released.
The focus of this release is „visibility“: a newLog Analysispage turns everyday access logs into analyzable, traceable operational evidence; it also upgrades the AI diagnostics experience, strengthens third-party AI privacy protection, and makes the Fail2ban banning process more transparent.
The clues to many operational issues are actually hidden in access logs—whether it's scanning, brute-force attacks, or an endpoint throwing a large number of errors. But log files are long, scattered, and rotated and deleted over time, so by the time a real problem occurs, they are often no longer available. The log analysis page in v1.4.0 is designed to make this step simple.
New Log Analysis Page
The panel adds a standalone „Log Analysis“ page that supports analyzing a site„s current logs and rotated logs by the last 1 hour, 24 hours, 7 days, or a custom time range, summarizing in a single page:
- Request volume and status code distribution;
- Popular access paths;
- Visitor IPs and crawler sources;
- Security events and current ban status.
Every statistic can be drilled down to traceable log details, so you no longer need to manually log in to the server to dig through log files.
Log Reports Support In-Depth AI Diagnostics
Log reports can directly initiate in-depth AI diagnostics and continue follow-up questions based on the same session.
General site diagnostics and log diagnostics now share a unified session context, enabling focused analysis based on the status code, path, crawler, or IP you select, rather than rescanning the full context each time.
Strengthened Third-Party AI Privacy Protection
When handing logs to third-party AI for analysis, privacy is an unavoidable issue. This release adds multiple layers of sanitization before sending:
- Sanitize passwords, tokens, cookies, API keys, and site absolute paths;
- Convert IPv4/IPv6 into stable aliases within the session, and restore the real IP locally in the panel only after the AI returns;
- If sanitization fails, the original content will not be sent.
Access Logs Add Real Connection Source
Site access logs now include actual connection source information, making it easier to distinguish the client address declared in the CDN header from the real origin connection; log analysis will flag obvious address attribution anomalies. The existing CDN strict mode, general compatibility mode, and ESA mutual exclusion rules remain unchanged.
More Reliable Googlebot Official IP Range Verification
Googlebot official IP ranges support relay caching, manual import, and recent refresh status, reducing the risk of verification failures when the server cannot directly access official sources; User-Agent alone will still not be recognized as an official crawler.
More Transparent Fail2ban Incremental Bans
Automatic bans increment independently by the same IP and the same rule, with the following tiers:
| Trigger Count | Ban Duration |
|---|---|
| 1st Time | 10 minutes |
| 2nd Time | 1 hour |
| 3rd Time | 6 hours |
| 4th Time | 24 hours |
| 5th Time | 7 days |
The panel records the actual ban duration, cumulative count, recovery, and unban status. Automatic rules will not escalate to permanent bans; permanent bans are still confirmed by the administrator.
Fixed WordPress Login Protection Detection
Successful logins, as well as clearly legitimate actions such as password recovery, password reset, and registration, are no longer counted toward login failure bans. The security page has also been updated with explanations of rate limiting, ban cycles, and burst buffering.
Other Improvements
- The default maximum wait time for AI diagnostics has been increased to 180 seconds (connection tests still use a shorter wait), reducing the likelihood of complex log diagnostics being interrupted prematurely.
Upgrade and compatibility
- This release includes a panel SQLite database upgrade, with the schema upgrading sequentially from 1.0.43 to 1.0.48;
- Installed servers can be upgraded directly, and the upgrade will not delete or rebuild existing website files, website databases, WordPress configurations, SSL certificates, or backups;
- This release does not modify the installation script, panel signature verification, or update rollback mechanism;
- After the upgrade, the panel will synchronize the Fail2ban configuration and reload the relevant rules. The existing compatibility mode, whitelist, and administrator manual permanent ban policies remain unchanged;
- Log analysis processes a maximum of 7 days and 512MB of data per run; when a report indicates that data has been truncated, please continue to verify against the original logs.
Upgrade now
WP Panel v1.4.0 has been officially released: Viewv1.4.0 Release Page。
After upgrading, you can start analyzing your site access logs on the „Log Analysis“ page.
