WP Panel v1.7.0 Officially Released: Simpler Auto-Updates, Clearer Settings Page

WP Panel v1.7.0 is officially released.

This update mainly does two things:Make panel auto-updates easier to understand, andmake the settings page more compact and easier to use. Auto-updates no longer require administrators to choose between „patch releases only“ and „all official releases“; root password recovery is also changed to an on-demand modal and adds the ability to generate a strong password locally in the browser.

The security boundary has not been lowered as a result: auto-updates remain off by default, pre-release versions are not installed automatically, and signatures, digests, backups, health checks, and failure rollback are all retained.

Auto-updates no longer distinguish between patch releases and other official releases

Older versions allowed choosing „patch releases only“ or „all official releases“. This option looks more cautious, but in practice it is easy to misunderstand: the panel only queries GitHub for the latest official release, and when the latest release has already moved to a new minor version, servers staying on an older branch will not continue looking for an older-branch patch that does not exist in the „latest release“ endpoint.

Starting from v1.7.0, auto-updates have only one clear rule:

• Auto-updates remainoff by default；
• Once an administrator enables it, the panel will install anystable official release；
• higher than the current version. Beta, RC, and other pre-release versions will not be installed automatically;
• manual checks and manual updates remain available at any time.

Existing servers will not have their update scope silently expanded

If a server previously had „patch releases only“ enabled, after upgrading to v1.7.0 the panel will first safely turn off auto-updates and prompt the administrator in the settings page to reconfirm. Auto-updates will only resume after the administrator accepts the new stable release scope and enables it again.

If a server has never enabled auto-updates before, it will remain off after the upgrade, and no prompt to re-enable it will appear. Servers that had already selected „all official releases“ keep their current state.

New versions are observed for 24 hours by default

After the panel first detects a new stable release, it waits at least 24 hours by default before attempting installation within the configured update time window. The 24 hours are counted fromthe panel first detecting that versionnot from the GitHub release time.

• If the GitHub version check fails, the latest status is shown on the settings page instead of silently waiting a full day;
• after a failed check, it retries within the update time window after about 30 minutes;
• a brief network failure or waiting for a signature will not cause the elapsed observation period to restart from the beginning;
• the settings page shows the latest check, latest result, and estimated check time, and reminds you that the estimated time is still subject to the update window based on server time.

Update protection has not been reduced

A simpler version policy does not mean the installation process becomes aggressive. Automatic and manual updates still use the same protections:

• verify the Ed25519 release signature and SHA256 digest;
• back up the panel program and panel database before replacing the program;
• after the new version starts, check the database, core tables, health endpoint, and actual running version;
• if the health check fails, attempt to restore the old program and retain the failure stage for troubleshooting.

Settings page reorganized

The settings page is regrouped by usage relationships to reduce large blank areas caused by inconsistent content heights:

• First row: Panel and Account / Server Basic Settings;
• Second row: Update Management / WordPress Installation Package;
• Panel database backup and operation logs continue to use full-width areas.

Panel updates and Debian system updates are now in the same „Update Management“ card, but they remain two independent operations: updating the panel will not also update system packages, and updating system packages will not change the panel version.

Root password recovery changed to a modal with support for generating a strong password

„Change server root password“ no longer permanently occupies space on the settings page. When needed, click the button in „Server Basic Settings“ to open a pop-up and re-enter the current panel login password.

• You can use the browser Web Crypto to generate a 24-character strong password locally;
• supports display and copy, making it easy to save to a trusted password manager;
• the generation process does not request the backend, and the panel will not save or record the generated password;
• the operation only modifies the Linuxrootpassword, does not enable or disable SSH password login, and does not modifysshd_config, firewall, or root SSH login policy.

Upgrade and compatibility

• The database version is upgraded to1.0.67, and the migration is completed automatically by the panel;
• the old default 15-minute observation period is adjusted to 24 hours, while other observation periods customized by the administrator remain unchanged;
• the upgrade will not modify existing websites, WordPress data, Nginx, PHP-FPM, MariaDB, Redis, or SSH configurations;
• during the panel upgrade, the WP Panel service will be restarted according to the existing process.

FAQ

Will auto-updates turn themselves on after upgrading to v1.7.0?

No. Automatic updates remain disabled by default, and servers that were originally disabled will remain disabled after the upgrade.

Will beta versions be installed after enabling auto-updates?

No. Automatic updates only accept stable official releases; pre-release versions will be skipped.

After setting the root password, can I log in to SSH with the password?

Not necessarily. If the server originally allowed root password login, the new password can be used according to the existing SSH policy; if the server originally prohibited password login or prohibited root login, this operation will not lift those restrictions.

Upgrade now

WP Panel v1.7.0 has been officially released: Viewv1.7.0 release page。

For more complete operating instructions, seeInstallation, login, and panel updates和Software, Scheduled Tasks, Alerts, and Settings。