Všechna vydání

1.0.0-beta.2

This release brings 2 improvements and 21 fixes.

Beta kanál WHost

Vylepšení

  • File Manager upload limit can be set in Settings > General. The largest file one File Manager upload may carry is now a setting (Settings > General > File Manager, 1-10240 MB, default 256 MB) for the admin and the client panel. Saving it also updates the panel's nginx body limit and the agent's limits for the File Manager upload routes, so no web server file needs editing; a file above the limit is refused when it is added, before anything is sent. Other upload routes keep their 300 MB ceiling.
  • The feedback entry is named "Report a bug", the same as in WISECP. The admin footer link, the command palette action and the report window now read "Report a bug" ("Hata bildir" in Turkish) in every panel language; searching the palette for the old name still finds it.

Opravy chyb

  • Server migration scan no longer sits at Scanning 0 / 0. The scan now runs in the background and the wizard and History tab count the scanned accounts; a scan that cannot connect, cannot detect the panel or stops on a remote command ends as Failed with the reason instead of staying at Scanning.
  • Server migration accepts an SSH key again. Scanning a source server with an Ed25519, ECDSA or RSA key no longer fails with a paramiko DSSKey error on current paramiko releases.
  • Firewall security log loads on older SQLite (AlmaLinux 9). The Firewall Security Logs tab no longer fails with an error on servers whose system SQLite rejects row-value lists (AlmaLinux 9 ships 3.34).
  • Server migration scans large servers several times faster. The scan asks the source server for each account's details in one remote run instead of about ten separate SSH commands, and sends small requests without waiting for delayed acknowledgements: a 300-account cPanel source over the internet went from about 14 minutes to under 1.5 minutes with the same result. A source that cannot run the batch is scanned the old way.
  • Server migration creates the migrated accounts again. Every account selected for migration failed at its first step with "Invalid email address: ''". The migrated account now gets the e-mail address the source panel records for it (cPanel, DirectAdmin, HestiaCP, CWP, WHost), or the administrator's address when the source has none; with neither it fails with that reason.
  • Server migration marks a partly copied account as Failed. When the source server's archive or database dump stops with an error, when an archive does not unpack or a database does not import, the account is marked Failed with the reason (for example "tar exit 2" or the database name) instead of Completed with data missing. Files that change while they are read and folders the source does not have are still accepted.
  • Server migration continues from a scan in History. A finished scan's History row now has an action: Select Accounts opens that scan's account selection while its SSH credentials are still kept (30 minutes after the scan, until the agent restarts); after that it offers Scan Again with the connection form filled in. Starting a migration whose credentials have expired leads to the same form instead of a bare Migration failed, and scan, connection and retry errors show the agent's reason.
  • Server migration names its steps in the panel's language. The per-account progress line and the Failed Accounts dialog name the migration step in the panel's language (for example Transferring files) instead of internal names such as transferring_files.
  • Server migration History columns line up with their headings. In Server Migration, History, the Accounts heading now stands above the account count and the progress bar has its own heading; the Panel heading that stood above the count is gone (the panel is shown under the server name).
  • Plans and accounts take CPU limits above 800 %. A plan, account or reseller CPU limit (100 = one core) now takes any value up to 102400 (1024 cores), so a 16-core plan with 1600 % can be created; before, the panel and the API stopped at 800 % (eight cores) and refused the plan with a validation error. A limit above the server's cores lets the account use all of them.
  • Server migration finds the databases of cPanel and CWP accounts. The scan counts a cPanel or CWP account's databases with the source server's MySQL, and the transfer lists them the same way. Before, that query always failed: cPanel counts and the transfer fell back to the folders under /var/lib/mysql (a source that keeps its databases elsewhere showed 0 and those databases were not copied), and CWP accounts always showed 0 databases.
  • Server migration counts cPanel addon domains and subdomains separately. The scan reads each cPanel account's domains from cPanel's own record, so addon domains and subdomains are counted apart. Before, every subdomain was counted as an addon domain and the subdomain count was always 0.
  • Server migration lists CWP accounts when CWP's database cannot be read. When the scan cannot read the account list from CWP's database, it lists the source server's home folders that hold a public_html folder. Before, that fallback checked the folders on this server instead of the source, so it found no accounts (or only names that also exist here).
  • phpMyAdmin imports SQL files up to 256 MB. phpMyAdmin's Import takes a file of up to 256 MB and may run for up to ten minutes. Before, any file above 1 MB was refused with "Request body too large" (the web server's default limit) and PHP allowed 2 MB, so raising the server's php.ini changed nothing. Existing servers get the new limits when the agent starts after the update.
  • File Manager names the 256 MB upload limit. A file larger than 256 MB is marked failed in the upload list as soon as it is added, with the limit and a pointer to FTP or SFTP, and nothing is sent; the upload panel shows refused or failed uploads in red instead of a green tick. Before, the browser sent the file and the upload stopped with "Request body too large" in English.
  • Webmail takes attachments up to the server's maximum email size. Webmail (Roundcube) accepts an attachment up to the server maximum email size instead of stopping at 1 MB; the compose screen shows that limit. Saving a new maximum email size in Settings > General updates the webmail limit with it, and existing servers get the limit when the agent starts after the update.
  • Disk Usage window waits longer for a slow system folder and no longer logs it as an error. The dashboard Disk Usage window now waits up to 30 seconds for each folder size instead of 10, so a large /usr is listed instead of left out, and a folder that still takes longer is left out without an error line in the agent log, which used to show up in error reports.
  • The panel starts the maximum email size at 50 MB, the size the installer gives Postfix. On a new server, Settings > General shows a maximum email size of 50 MB, the size Postfix already accepts after installation; before, it showed 25 MB while Postfix took 50 MB. A size saved earlier is kept.
  • New installs on an XFS root (AlmaLinux, Rocky Linux) enforce account disk limits. On an XFS root filesystem the installer now turns disk quota on: it adds rootflags=uquota to the kernel command line and names the restart it needs, after which each plan's disk limit is enforced. Existing servers are not changed by the update; the installation guide gives the steps to turn quota on later and to apply the limit to existing accounts.
  • Unlimited disk now lifts the account's disk quota on the server. An account moved to an unlimited disk plan, or set to unlimited disk on the edit form, kept its previous disk quota on the server and stopped writing at the old limit; an account created with unlimited disk could also inherit the quota of a deleted account. Both now end up with no disk limit.
  • Choosing Custom on the account edit form now takes the account off its plan. Saving the account edit form with Custom selected applied the limits but kept the account on its previous plan, so the plan name stayed on the account and came back in the form. The account now has no plan, and the client dashboard shows a dash for an account without one.

V tomto vydání

Číst průvodce instalací Odeslat zpětnou vazbu