جميع الإصدارات

1.0.0-beta.4

This release brings 1 improvement, 1 security fix and 7 fixes.

قناة الإصدارات التجريبية WHost

تحسينات

  • Migration scans of large cPanel servers finish much faster. Scanning a cPanel server for migration used to measure every account's home folder one by one, which took many minutes on servers with hundreds of sites. The scan now reads every account's disk usage from cPanel's own account list (the figure WHM shows) and every account's database count in one query, and asks the source server about many accounts per round trip; an account cPanel reports no usage for is still measured as before. On our own cPanel server the scan went from 115 to 31 seconds for 50 accounts.

الأمان

  • On LiteSpeed servers, accounts can no longer read each other's site files. On OpenLiteSpeed and LiteSpeed Enterprise the account homes were open for other accounts to pass through, so another account on the server could read a site file whose name it knew - a migrated WordPress's wp-config.php included. Homes and web roots are now closed the way nginx and Apache keep them (0750 with the web group, which the LiteSpeed worker runs with); a server already on LiteSpeed closes them once at the agent's first start after the update. The same change makes the images WordPress uploads load again where the File Manager made the folders.

إصلاحات الأخطاء

  • WordPress media uploads and imported images no longer return 403 on Nginx / Apache sites. On Nginx and Nginx + Apache sites the folders the File Manager creates or extracts are now 755, so the files a site writes below them later (WordPress media uploads and demo-import images) are served instead of answering 403. A site installed through the File Manager earlier is repaired by setting wp-content/uploads to 755 with its sub-items (Permissions).
  • The installer retries package downloads when a repository answers with a temporary error. A package repository that answers 503 or times out no longer stops a new installation at once: apt tries the download again up to ten times, over about three minutes. The setting stays in place, so the panel's package work and OS updates retry the same way.
  • The installer says why a Python version was not installed and how to add it later. When a Python runtime for Python hosting cannot be downloaded because of a temporary repository error, the installer says so together with the command that installs it later, instead of reporting it as not available on the OS; the post-install check counts it as a warning and the closing screen names it.
  • LiteSpeed Enterprise activation explains IPv6-only resolvers and license errors. On a server whose resolver lists only IPv6 nameservers, activating LiteSpeed Enterprise now stops before anything is downloaded and says what to change, instead of installing the server and rolling it back without a reason. When LiteSpeed refuses to start for another reason, the activation error shows LiteSpeed's own license messages.
  • Migrated sites keep their databases, home page, PHP version and WAF exclusions. A migration now carries the account's database users with their passwords (as the source's password hash, never in clear) and their grants, so a migrated WordPress connects to its database. From cPanel it also carries the databases cPanel named with its short 8-character prefix for accounts with longer names, which were skipped without a word: they get the account's name as their prefix here, together with their users, the site's wp-config.php is pointed at the new names, and the scan counts them. It puts the web root back to the group nginx and Apache read it with; removes the account's default page when the site brings its own index (Apache served it in front of the site); keeps the source's PHP version on AlmaLinux, Rocky Linux and CentOS Stream too; applies the WAF's WordPress exclusions to the migrated sites at once, so editor saves are not refused in the first minutes; and the migration page now shows each account's migration warnings (a renamed database, .htaccess rules that were not converted) while the job runs, when it completes and in the history.
  • Resetting the admin password with whost-admin also lifts a sign-in lock-out. After five wrong passwords the admin sign-in is locked for 15 minutes, and that lock used to outlast a password reset: the new password from 'whost-admin reset-password' was refused until the lock ran out. The command now lifts the admin's lock-out as well, so the new password signs in at once; other users' counters are untouched.
  • OpenLiteSpeed and LiteSpeed activations show why a site's configuration was refused. When OpenLiteSpeed or LiteSpeed Enterprise refuses a site's configuration while the web server is switched, the activation dialog now quotes the lines that refused it (at most five), and the agent log starts the refusal with those lines and keeps the configuration test's whole output from both its streams. Before, the dialog only named the site and the log could miss the refusing line altogether. An account's own requests answer as before and never quote the test's output.

في هذا الإصدار

قراءة دليل التثبيت إرسال الملاحظات
تاريخ الإصدار
إعادة التشغيل
مطلوبة بعد التحديث