2.1.2

Added​

• Publish what the panel needs, so nothing is fetched from a private repository.
• Publish the releases feed the dashboard reads.
• A reinstall that can be pointed at a server with customers on it.
• Request inspection with a rotating challenge, in front of every WebEngine.
• The pages an account and an administrator actually use.
• Let a rule through, per site, and fix what the reinstall would have hit.
• Pick the PHP version when installing a website.
• Sign outgoing mail, which the server was not doing at all.
• MailFlow, served natively, replacing the Roundcube container.
• Install MailFlow from the source this release ships.
• The panel creates the first account; registration is closed.
• One line, at the address the documentation already gives.
• The runtime bundle is built by CI, not by the mirror.
• The panel had no certificate of its own, and nothing to issue one.
• The Settings and Updates tabs answered 501.

Fixed​

• An install stopped over a file nginx does not read.
• Install the systemd units a release ships.
• Do not install a unit template as a unit.
• The Containers menu is gone; the terminal moved to Advanced.
• The page names the account's own directory.
• Wp-config named a database that would never exist.
• A request over HTTPS was redirected to http on a TLS-only port.
• Wp-config named a database with capitals that MySQL never made.
• The installer required public DNS to already point here.
• Default hosting plans grant only what an account can actually use.
• Installing an application onto a recorded site, and the scan that found nothing.
• Probe a binary for its version under a timeout, and gate obfuscation on the tests.
• A let-through rule no longer writes a line per request.
• One stray site record no longer fails every deploy.
• The firewall was never shipped, and the SSL page showed no certificate.
• A database password was typed into a plain-HTTP form.
• The firewall read no site's settings, so every site was off.
• PHP was never told the visitor's request was HTTPS.
• DNS Visualizer appeared twice and Traceroute did not line up.
• A stale features.json deleted modules from a running server.
• The firewall deleted the front-end's forwarding headers.
• A nested tar member failed the whole archive.
• A deploy never re-rendered the WebEngine master configs.
• Installing a language did nothing and said it worked.
• The browser gave up two seconds into a render.
• The default node was read in a way that could not work.
• The page blamed a docker file for a role that was never created.
• The link went to a plain-HTTP bare IP that nothing kept current.
• The page typed a container path into its own directory box.
• The page said it edits a file it does not.
• The panel called itself HiTechCloud, not HiTechCloud Panel.
• The ClamAV scan-root tests assumed a native stack.
• The panel's name vanished from the sidebar.
• Security Measures and Debugging were Caddy-only or absent.
• Sourcing os-release overwrote the release version.
• The installer waited for a password nobody could type.
• The installer could not get the panel from the mirror at all.
• The bundle was missing the CLI, and warned about a submodule it had.
• A new server came up with half a hosting stack.
• A fresh install stopped short of a working panel.
• Every system backup failed, and blamed it on a licence.
• Mail served a self-signed certificate while a real one sat unused.
• Four failures a fresh AlmaLinux install reported as success.
• Single sign-on was registered with a mode the backend rejects.
• A system backup was 823MB of downloadable software.
• The bundle check killed tar with SIGPIPE and failed a correct bundle.
• An account was put on a plan that did not exist.