Tutte le versioni

1.0.0-beta.7

This release brings 2 new features, 2 improvements, 1 security fix and 33 fixes.

Canale beta WHost

Nuove funzioni

  • Spam Filter: optional enforcement of the sender domain's DMARC policy. A new switch on the Spam Filter page, off by default. When it is on, mail that fails its sender domain's DMARC policy is rejected (policy reject) or marked as spam (policy quarantine) instead of only scoring higher. Forwarded mail and mailing list mail often fail DMARC although they are genuine, so they are affected too; the help text beside the switch says so. A DMARC settings file kept by hand on the server is never changed.
  • ARC signing for mail that passes through the server. Rspamd now adds an ARC set (ARC-Authentication-Results, ARC-Message-Signature, ARC-Seal) to mail: mail arriving for a hosted domain - including mail a forwarder sends on - is sealed with the recipient domain's key, mail sent by the server's mailboxes and sites with the key of the From domain. A server further down the line can then still see how a forwarded message authenticated. The seal uses each domain's existing DKIM key and selector, so the DKIM record already published verifies it and no new DNS record is needed; a domain without a DKIM key is not sealed. Existing installations switch ARC on at the agent's first start after the update, unless /etc/rspamd/local.d/arc.conf was changed by hand. DKIM signing stays with OpenDKIM.

Miglioramenti

  • Larger ready-made PHP upload sizes: 2048M, 4096M and 8192M. The PHP upload and post size lists of the admin panel, of Default PHP Settings and of the client panel now offer 2048M, 4096M and 8192M beside the earlier values, for applications that take uploads of several gigabytes. The help text of the two fields says that a large upload is written to disk twice while it is sent (the web server's own copy, then PHP's copy in the account's tmp folder), and the account's WAF card says what the WAF mode does to the upload limit.
  • A failed Let's Encrypt validation says what the server itself measured. When Let's Encrypt cannot validate a name, the error now also carries what the server measured for it: whether its own web server serves the validation file for that name, and which addresses the name resolves to - for example that the name resolves to an address that is not this server's, that it also resolves to a second address elsewhere (a leftover IPv6 record), or that it does not resolve at all. A 404 reported by Let's Encrypt can so be told apart: the name leads to another machine, or this server does not serve the file.

Sicurezza

  • WAF: form and JSON bodies are inspected up to 1 MB and refused beyond it while blocking. While the WAF blocked (server mode On, or an account's mode Block), a form or JSON request body above 128 kB reached the site without being inspected, and so did a body the WAF could not parse (plain text under a JSON content type, a multipart body without its closing boundary). The WAF now inspects form and JSON bodies up to 1 MB and refuses a body it could not process with 400 (rule 200002, 'Failed to parse request body.'); in Detect only it is written to the WAF log instead. Uploaded files do not count towards the 1 MB and requests without a body are not affected. A site that legitimately posts more than 1 MB of form or JSON data can be left out of rule 200002 for the account or for one path on the account's WAF tab (a reseller does the same on a sub-account's page), or the rule can be switched off for the server on the WAF page's Rules tab. Existing servers receive the change at the first start after the update; a limit or a 200002 rule you set yourself is kept.

Correzioni di bug

  • Installer adds a missing localhost line to /etc/hosts. On servers whose /etc/hosts had no 127.0.0.1 localhost line (some provider images), OpenDKIM and Rspamd failed to start after installation. The installer now adds the line.
  • Outgoing mail is DKIM-signed even if OpenDKIM was down during installation. If OpenDKIM was not running at the moment the installer set up the spam filter, Postfix was configured without it and outgoing mail left unsigned for good. The installer now always connects OpenDKIM, and its closing check fails when that connection is missing.
  • Installer no longer writes unused single-key lines to opendkim.conf. The installer wrote Domain, Selector and KeyFile lines that OpenDKIM ignores when its key table is set; the KeyFile line pointed to a key that never exists and misled troubleshooting. New installations sign from the key and signing tables only. Signing itself is unchanged.
  • Uploads larger than 256 MB work when the PHP upload size is raised. Raising a site's PHP upload_max_filesize / post_max_size above 256 MB had no effect: the web server refused larger uploads with 413 whatever PHP allowed. The web server's limit now follows the site's PHP sizes (up to 8192 MB) while the account's WAF mode is Off. While the WAF is on, the limit stays at 256 MB and the PHP Configuration dialog says so under the size fields.
  • Client panel no longer offers an "Unlimited" PHP upload size that could not be saved. In the client panel's PHP Configuration, upload_max_filesize and post_max_size offered "Unlimited", a value PHP does not have for these settings; saving it ended with an error. The option is gone from the two size fields; memory_limit keeps it.
  • PHP settings saved in the panel now apply on OpenLiteSpeed / LiteSpeed servers. On a server running OpenLiteSpeed or LiteSpeed Enterprise, PHP settings saved for an account or for one of its sites (upload and post size, memory limit, execution time and the others) never reached PHP: the panel showed the saved values while the sites ran with PHP's package defaults (2 MB uploads, 8 MB post size, 128 MB memory, 30 seconds). The saved values now apply, and a change takes effect at once. Uploads above 2047 MB, which the LiteSpeed server ended with a 502 error, now work up to the size set for the site.
  • PHP memory limit and worker count follow an account's plan and resource limits. When an account moved to another plan, or its memory or process limit was changed on the Edit Account form or the Resource Limits card, its PHP kept the earlier limits: a plan change wrote PHP with the values of the plan before it, the other two did not write it at all. A customer who upgraded stayed on the old PHP memory limit and worker count although the panel and the API reported the change. Every one of these changes now writes the account's PHP at once, on PHP-FPM and on OpenLiteSpeed / LiteSpeed servers alike. At the first start after the update, an account whose plan or limits give more than its PHP has is moved up to them once; the update lowers no account's PHP memory limit or worker count.
  • Nginx comes back by itself after it ends unexpectedly. When Nginx ended other than by a clean stop - the kernel ending one of its workers for lack of memory, or its main process ending on a signal - it stayed down, and the panel and every site on the server with it, until someone started it by hand. It now comes back by itself within about two seconds. A clean stop stays a stop, and an Nginx that cannot start at all (a refused configuration) is given up after five attempts instead of being retried for ever.
  • WAF upload sizes while it blocks are documented; an unread setup line is gone. While the WAF blocks (server mode On, or an account's mode Block), form uploads above 10 MB - and under Nginx any request body above 12.5 MB - are refused with 403 whatever the PHP sizes are. That is unchanged: raising these sizes to the site's limit was measured and makes the web server take several times the upload's size in memory (a 200 MB form upload took 1.9 GB of an Nginx worker and kept it busy for 27 seconds). The admin and client guides now state the sizes, the difference under OpenLiteSpeed and the way out (the account's WAF mode Detect only or Off). The rule setup no longer writes a combined file size line that no rule ever read; requests are treated as before.
  • Saved spam score thresholds now apply, and Rspamd starts again after a restart. Saving the spam scores on the Spam Filter page for the first time left a file Rspamd could not read: the saved scores did not apply, and Rspamd did not start again after its next restart, so mail was delivered unfiltered. The file is now written readable, a save is checked with Rspamd's own configuration test before it is applied, and a file an earlier version left behind is repaired when the agent starts.
  • Spam Filter page shows the saved scores right after a reload. After reloading the Spam Filter page the form showed the default scores until the server's answer arrived, and a Save pressed in that moment wrote those defaults. The form now shows the saved values at once.
  • Notification settings no longer save a made-up sender address. With nothing saved for From Email and From Name, the notification settings page filled the fields with noreply@(server name) and WHost, and any save on the page wrote those values into the settings - while the server itself sends as whost@(server name). The fields now stay empty, show the sender that is really used in their place, and an empty field is saved empty.
  • Changing the server name now changes the mail server's name with it. Renaming the server from the panel (the dashboard or Settings > General) left Postfix greeting and sending under the old name. Postfix's myhostname / mydomain and /etc/mailname now move to the new name with the rename; Postfix tests the change before it reloads, and if it refuses, its previous names stay in force and the save says so. A name you set in Postfix yourself is kept. New installations greet with the server name itself - the name the server's certificate covers - instead of mail.(server name). A server renamed under an earlier release keeps the old name in Postfix until it is set once by hand: the Email table of the Troubleshooting guide has the two commands.
  • IMAP / POP3: mail clients that prefer a DH key exchange can connect over TLS. Dovecot was installed without Diffie-Hellman parameters. A mail client that offered only a DH key exchange, or listed it before ECDHE, could not connect to IMAP / POP3 over TLS, and each attempt wrote "no DH parameters provided" to the mail log; most current clients were not affected. New installations get the parameters (the RFC 7919 ffdhe2048 group in /etc/dovecot/dh.pem). On an existing installation the agent adds them once, at its first start after the update, when Dovecot has no ssl_dh setting of its own, and takes the change back if Dovecot stops answering TLS afterwards.
  • Dovecot no longer logs a permission error for its master-users file. Each time one of Dovecot's auth workers started it wrote "passwd-file /etc/dovecot/master-users ... Permission denied" to the mail log: the file behind the panel's one-click webmail sign-on was closed to the account the workers run as. Mailbox logins and the webmail sign-on worked all along. The agent now gives the file the owner, group and mode both of Dovecot's processes read it with (dovecot:vmail, 640 on a standard installation) each time it starts, and writes it that way.
  • An update is no longer rolled back because the new release takes long to start. After an update the agent used to open its listener only once all of its start-up work had ended. On a server where that work takes long - many sites under OpenLiteSpeed, sites tested one by one after a web application firewall change - the post-update check saw no answer within its 110 seconds, put the previous release back and wrote 'manual recovery is needed' to the agent log although the new release was healthy. The agent now answers its health route after 40 seconds at the latest; until its start-up work has ended every other request is answered 503 AGENT_STARTING with Retry-After, and nobody is signed out. A start that ends in time - the usual case - behaves as before. After a real rollback the restored release is now asked for three minutes before the log calls for manual recovery.
  • Node.js apps: npm installs, deploys and npm scripts find the app's own Node.js. Installing a package, 'Install all', running an npm script and deploying a Node.js project from an archive or a folder failed with "/usr/bin/env: 'node': No such file or directory": the package manager was started with the account's plain PATH, which does not hold the panel's own Node.js. No app with dependencies could be installed. The package manager now runs with the app's Node.js version first on its PATH, so npm, pnpm and yarn, the scripts they run and a package's own install step all use the version the app is set to - also on a server that has another Node.js installed system-wide, where they used to run with that one.
  • Two Let's Encrypt requests at the same moment no longer fail one of them. A certificate request made while another one was running ended at once with "Another instance of Certbot is already running" - in a panel as an error, and silently when it was the automatic request of a new account or addon domain, which then stayed without a certificate. The agent's requests now take turns, and a request that meets certbot's own renewal run waits for it (up to two minutes) before it says that certbot is busy.
  • Auto SSL now puts the certificate it gets into the site. With Auto SSL on, a new account, an addon domain, an account whose Auto SSL was switched on and a changed primary domain got their Let's Encrypt certificate, and the SSL page listed it as active, but the site was never set up for HTTPS: it did not serve the certificate until it was requested again from the SSL page. These four requests now install the certificate into the site and reload its web servers. A certificate an earlier release fetched and left out is installed by Renew Certificate on the SSL page.
  • A certificate is issued when only the www form of a name cannot be validated. A Let's Encrypt request names the domain and its www form, and it failed as a whole when the www form had no DNS record - always so for a subdomain added in the panel, which gets a record for itself only. When only the www form fails, the certificate is now issued for the name alone and a warning names the form that was left out; once its record exists, requesting the certificate again includes it.
  • OpenLiteSpeed: a missing WAF module file is brought back and the rule set loads again. On an OpenLiteSpeed server whose ModSecurity module file was gone while its package was still registered - a state a LiteSpeed Enterprise attempt on 1.0.0-beta.4 could leave - the agent kept logging "ols-modsecurity installed but ... mod_security.so is missing", the WAF page said the rule set was not loaded, and no request was checked even with the WAF set to block. The agent now installs the package again over its files, loads the rule set and puts the sites' WAF back by itself, within 30 minutes of the update.
  • Create Database: a long name no longer leaves a database without its user. In the client panel, Create Database fills the user name from the database name; with a name longer than 15 characters the database was created, the user was refused with an English validation message, and the window stayed on the form. Both panels' forms now keep names within the server's rules as you type (15 characters for a user, cut from the database name), say the rule in your language, and when the server refuses the user after the database was created, the result window says so beside the created database.
  • whost-admin ip-allowlist: a way back in when the admin IP whitelist keeps you out. When the admin IP whitelist no longer covered the administrator's address, the admin pages answered 404 and nothing on the server undid it: emptying the list in agent.conf by hand lifted only the agent's own check while nginx kept answering 404. As root on the server, 'whost-admin ip-allowlist show' now prints the list and what nginx enforces, 'add ADDRESS' lets an address or a network in and 'clear' empties the list - written to agent.conf and to nginx together, after nginx has accepted the change.
  • Site certificates work when only the administrator's own e-mail address is set. On a server whose Let's Encrypt e-mail (Settings > General) was empty, every site certificate request was refused with SSL_EMAIL_REQUIRED even when the administrator's own e-mail address (Settings > Profile) was set, while the server name's certificate used that address. A site certificate now uses it too. When neither address is set the request is still refused: the admin panel names the two places to set one, and the client panel tells the customer to contact the hosting provider instead of pointing at a setting the customer does not have.
  • The installer's result screen says when root still signs in over SSH with a password. When root had no SSH key, the installer left root's password sign-in as the system set it and said so only in a line in the middle of the install. The result screen now reads sshd's own setting and, when a password still works for root, says so with the way to keys only: add your key with ssh-copy-id, then restart the agent, which limits root to keys at its start. The documented host hardening command now carries the agent's path, without which it stopped with 'No module named whost_agent'.
  • Client panel: a subdomain and a redirect can be edited. On the client panel's Domains page a subdomain or a redirect could only be deleted; changing a document root, a name or a redirect's destination meant deleting the entry and creating it again (the API and the admin panel could edit). Both rows now have a menu with Edit: a subdomain's name and document root, and a redirect's source path, destination and kind (301 / 302), are changed in a dialog. Delete is in the same menu.
  • Admin SSL page: the install dialog offers the account's subdomains too. In the admin panel, SSL > Install SSL listed only the chosen account's primary and addon domains, so a certificate for a subdomain could not be requested there (the client panel and the API could). The dialog's domain picker now lists the account's subdomains as well.
  • Per-domain PHP settings take effect at once on OpenLiteSpeed / LiteSpeed servers. On a server running OpenLiteSpeed or LiteSpeed Enterprise, a PHP value saved for a domain in the panel (memory limit, execution time, upload size and the others) applies from the site's next request, and a value set back to the account's, or Reset to Defaults, takes effect the same way. Servers running PHP-FPM are unchanged.
  • The File Manager applies a raised upload limit at once. After the File Manager's upload limit was raised in Settings > General, a File Manager page that was already open kept refusing files with the earlier limit, in the admin and the client panel, and an upload started within about a minute of the change could be refused with the earlier limit as well. The File Manager now checks the limit in force before it refuses a file, and a file the new limit allows is sent again on its own when the web server still answers with the earlier one.
  • A new account's PHP starts with its plan's memory limit and worker count. A newly created account's PHP did not start with the values its plan gives: under PHP-FPM it was written with the server's defaults (256M memory, 10 workers), and on OpenLiteSpeed and LiteSpeed servers it ran with 10 workers and PHP's package defaults while the panel showed 256M. A new account now starts with its plan's memory limit and worker count in every web server mode, and the panel shows the value the site runs with; creating an account takes as long as before.
  • The File Manager's "file too large" message shows in full and says where the limit is set. When the File Manager refused a file above its upload limit, the message was cut to a single line in the upload dialog, so only its first words could be read. The message is now shown in full under the file's name. In the admin panel it says where the limit is changed (Settings > General > Maximum Upload Size); in the client panel it says to upload the file over FTP or SFTP or to ask the hosting provider to raise the limit. The message is in the panel's language whichever part of the server refused the file.
  • Existing accounts keep their PHP memory limit and worker count through the update. For accounts created on earlier releases the panel shows the server's default PHP memory limit (256M) whatever their plan gives, and their PHP runs with 10 workers. From this release PHP follows the account's plan; for an existing account the update only ever raises the two values. Where the plan gives more, the account moves up to it at the first start. Where it gives less (a plan with less than 1024 MB of memory, or fewer than 20 processes), the account keeps the memory limit the panel shows and the workers it has, and a memory limit saved for one of its domains stays in force without saving it again. A kept value gives way to the plan's once the limit it is taken from changes: the account's memory limit for the PHP memory limit, its process limit for the worker count. An account with a PHP value saved as its own is not touched.
  • ARC signing switches on at the first start on a server with saved spam scores too. On a server whose Spam Filter scores were saved on an earlier release, the file that save left behind cannot be read by Rspamd, and Rspamd's own configuration test then refuses every new setting, ARC's included. The agent's first start after the update repairs that file before it writes the ARC settings, so ARC signing is switched on at that first start on these servers too.

In questa versione

Data di rilascio
Riavvio
Necessario dopo l'aggiornamento