Repository navigation
Releases
HostZit 0.10.4
HostZit 0.10.4 — domains work like in cPanel: a customer proves that a domain is theirs, and the server's own domain stays the administrator's.
Changed
- The domain ownership check is on by default, like in cPanel, where domains that point at other servers are off by default. A customer adds a website, an alias or a DNS zone only when DNS shows that the domain is theirs: it points at this server, its name servers are this server's, or the TXT record
_hostzit-verify.DOMAINholds the value the panel shows. A server that never saved Settings → Sign-in and security gets the check with this version; a server where it was saved off keeps it off. - The server's own domain belongs to the administrator. Customers cannot add the registered domain of the server name and of the name servers (for example
example.comforhost1.example.com), or any name below it, even with the check off. Before, an old record that still pointed at the server, or a delegation to its name servers, let any customer take such a name over, and the ownership check even passed.
Fixed
- An administrator working in the customer's panel (Open the customer panel) can add any free domain for the customer, as the guide always said. Names of the server itself and names below another customer's zone stay refused for everybody.
- Deleting a customer also forgets which EmailZit server the customer's mail was on, including the customer list of a link that serves only chosen customers. Entries left by customers deleted earlier are dropped within the hour. The delete form says that the mail stays in EmailZit, so the administrator ends the customer there too.
Updating
Settings → Updates installs 0.10.4. New servers:
curl -fsSL https://github.com/Max-Zit/hostzit/releases/latest/download/install.sh | sudo bash
Appliance images: hostzit-appliance.ova, .qcow2, -vhdx.zip, .iso (checksums in SHA256SUMS-appliance).
HostZit 0.10.3
HostZit 0.10.3 — an update or a restart of the server no longer cuts a change in half, and updated dependencies.
Fixed
- A stop of the root helper waits for the change in flight. An update restarts the helper, and a reboot stops it. Before, it stopped at once, and systemd also stopped the programs of the operation that was running. A change could be cut between writing its files, testing them (
nginx -t) and reloading the service; it then counted as failed and was rolled back. Now the helper takes nothing new and lets a running change finish, for up to 20 seconds. A longer operation (a malware scan, a backup) is still cancelled when that time is up. - Network of the appliance: when a change of the address was interrupted, the previous settings now really come back. Before, the old file came back while the server kept the new address until the next restart.
Changed
- Dependencies: pgx 5.13.0, maxminddb-golang 2.9.1.
- Administrator guide: Updates says that a change the panel is making at that moment is finished first.
Updating
Settings → Updates installs 0.10.3. New servers:
curl -fsSL https://github.com/Max-Zit/hostzit/releases/latest/download/install.sh | sudo bash
Appliance images: hostzit-appliance.ova, .qcow2, -vhdx.zip, .iso (checksums in SHA256SUMS-appliance).
HostZit 0.10.2
HostZit 0.10.2 — fixes from the joint tests with EmailZit on real servers, and updated dependencies.
Fixed
- EmailZit's relay proof: when EmailZit asks again for the same proof record while it waits for the public DNS, HostZit no longer writes the zone again. Before, every repeat raised the zone's serial and made the secondary name servers transfer the zone at the moment EmailZit looked the record up.
- EmailZit's SPF record no longer counts as a conflict when the zone's own SPF record already names everything it asks for. HostZit keeps the zone's SPF and adds EmailZit's mail server to it itself, so EmailZit no longer shows "HostZit kept some own records of the customer" for a domain that works.
- Settings → EmailZit: "—" for cPanel imports stays "—" with a single EmailZit link. Before, saving put the link back. Choosing a package with a single EmailZit still picks it.
Changed
- Dependencies: golang.org/x/crypto 0.59.0 (clears GO-2026-5932; HostZit never used the affected openpgp package), go-jose 4.1.9, pgx 5.12.0, x/oauth2 0.38.0, x/sys 0.50.0, x/term 0.48.0.
- Administrator guide:
- It points to the list in EmailZit 0.11.2 (Settings → HostZit) of the record that a domain whose DNS is elsewhere must show.
- It says what "—" for cPanel imports means.
- It explains why EmailZit's own SPF record is not needed in a zone here.
Updating
Settings → Updates installs 0.10.2. New servers:
curl -fsSL https://github.com/Max-Zit/hostzit/releases/latest/download/install.sh | sudo bash
Appliance images: hostzit-appliance.ova, .qcow2, -vhdx.zip, .iso (checksums in SHA256SUMS-appliance).
HostZit 0.10.1
HostZit 0.10.1 — fixes for the links with EmailZit, found on the first real pair of servers and in the lab tests with several HostZit and EmailZit servers.
Fixed
- Works with EmailZit 0.11.1. EmailZit 0.11.1 adds an
_emailzitrecord to a domain's mail records and trusts a domain only once the public DNS shows it. HostZit refused that record, so every DNS write of EmailZit 0.11.1 failed and no MX, DKIM or SPF record of its domains was published. HostZit now takes it. It also publishes the_emailzit.<domain>record that EmailZit's relay asks for before it takes the website mail of a domain without mail there: for the EmailZit that relays the website mail of the customers without EmailZit, for a zone or any name in it. These records have their own owner (emailzit-proofon the zone page), never replace EmailZit's mail records, and are removed when another relay is chosen. - Website mail through an EmailZit with its own certificate. The relay of EmailZit for website mail is now checked like its API: a certificate the system trusts, or the key from the pairing code. Before, an EmailZit with a self-signed certificate made every website message wait in the queue (nothing was lost).
- A customer found through EmailZit's DNS records sends through EmailZit at once. When an EmailZit writes the mail records of a customer HostZit did not know on it yet, the customer's website mail and the SPF record of its zones follow at once instead of after the next resync (up to 10 minutes).
- A link whose HostZit token was revoked shows it. Revoking the token of an EmailZit link under My account → API tokens now marks the link as not working at once and sends a notice; the link check finds it too. Before, the link still read Linked while EmailZit's calls were refused.
- The token list marks the tokens of EmailZit links and asks before revoking one; to end a link, use Settings → EmailZit → Unlink.
- Pairing again lifts a sign-in block of EmailZit's addresses. Calls of an EmailZit with a revoked token could get its address blocked by the sign-in protection, which then also stopped the new pairing.
- A test of the EmailZit links could fail now and then under the race detector (no change to the program).
Updating
Settings → Updates installs 0.10.1. New servers:
curl -fsSL https://github.com/Max-Zit/hostzit/releases/latest/download/install.sh | sudo bash
Appliance images: hostzit-appliance.ova, .qcow2, -vhdx.zip, .iso (checksums in SHA256SUMS-appliance).
HostZit 0.10.0
HostZit 0.10.0 — HostZit and EmailZit are linked with one pairing code, customers open EmailZit with one click, and websites send their mail through EmailZit or, without it, HostZit delivers it itself with DKIM.
New
- Link with EmailZit by one pairing code. In EmailZit 0.10.0 or newer, Settings → HostZit → Make a pairing code; paste it under Settings → EmailZit and press Link. The two servers make each other's tokens with the least rights (EmailZit's for HostZit: customers and one-time sign-in links; HostZit's for EmailZit: only the mail records of the zones), each limited to the other server's IPv4 and IPv6 addresses. EmailZit's certificate is checked the usual way or against the fingerprint in the code. Unlink on either side revokes both tokens. Nobody copies a token by hand any more; links typed in by hand keep working until they are unlinked.
- Several HostZit and EmailZit servers in any combination. A HostZit server can be linked with several EmailZit servers and each EmailZit with several HostZit servers. A customer's mail is on one of them; HostZit finds which and uses that one for the customer's one-click entry, DNS records and website mail. A link can serve all customers or only the customers assigned to it (an EmailZit of one client, which then learns nothing about the others). A link that stops working is shown and told; website mail waits instead of being lost.
- Customers open EmailZit with one click from the switch in their panel (a one-time sign-in link of EmailZit). Without mail in EmailZit, or without a switched-on sign-in there, the panel says so. The OpenID Connect client part of Settings → EmailZit is gone.
- Mail from websites without EmailZit is delivered by HostZit itself: to the mail servers of the recipients, with STARTTLS when they offer it, signed with a DKIM key per domain. Zones on the server get the DKIM record automatically; for domains whose DNS is elsewhere the customer sees the record to set. Settings → Notifications checks outgoing port 25 and the reverse DNS of the server, and the overview warns when direct sending cannot work. An SMTP server for websites stays possible.
- Customers with mail in an EmailZit on another server send their website mail through its relay (the login comes with the pairing), signed with HostZit's DKIM key of the domain, and the default SPF record of their zones also names EmailZit's mail host. The websites of other customers can go through one EmailZit's relay too (Settings → EmailZit → For all links). EmailZit shows the mail to the customer. With EmailZit on the same server, customers without mail in EmailZit keep HostZit's own sending.
- Only the account's own domains can send: the From address must be on a website, alias or zone of the account.
- Customers see their website mail: under Security the queue, every sent, refused and failed message of the last 30 days and the DKIM records; undelivered mail is also a notice.
- API tokens can be limited to addresses (IPv4 and IPv6); from any other address the token is refused.
- Website page warnings: a name that points at a proxy (for example Cloudflare's orange cloud) instead of the server, and a domain whose mail does not go to the linked EmailZit.
Fixed
- A panel job that ran out of time stayed "running" until the next restart.
- The nightly panel backup failed when a certificate file was replaced while it was read.
- Deleting a customer left an empty systemd slice of the account running.
- web-uids were sent to an EmailZit on another server (they matter only on the same server), and every customer without mail was logged as a warning.
Updating
Settings → Updates installs 0.10.0. New servers:
curl -fsSL https://github.com/Max-Zit/hostzit/releases/latest/download/install.sh | sudo bash
After the update, website mail of servers without EmailZit and without an SMTP server for websites is delivered by HostZit itself: check Settings → Notifications → Mail from websites (outgoing port 25 and reverse DNS). Servers linked to EmailZit by hand: link again with a pairing code to get the relay and the one-click switch.
Appliance images: hostzit-appliance.ova, .qcow2, -vhdx.zip, .iso (checksums in SHA256SUMS-appliance).
HostZit 0.9.5
HostZit 0.9.5 — fixes from a full production test on real servers (h1.maxzit.com with two DNS-only servers): DNSSEC with DNS-only servers, buttons that did nothing in Chrome, SSH algorithms on servers installed by script, long malware scans and more.
Fixed
- DNSSEC with DNS-only or other secondary servers: a signed zone was never transferred to them again (NSEC3 "narrow" cannot be transferred), and with the DS record at the registrar validating resolvers rejected their answers. Zones are now signed with plain NSEC3 (RFC 9276) and reach the secondaries already signed; switching DNSSEC on or off tells them at once. Zones signed by older versions are changed by the update itself.
- "Open the customer panel" and "Open" of a restore point in the admin panel did nothing in Chrome, and so would the EmailZit sign-in through HostZit for a customer who still had to sign in (the browser blocked the redirect after the form).
- SSH and SFTP on servers installed by the install script offered weak algorithms (NIST curves, ECDSA host keys, SHA-1 and 64-bit MACs). Every server now uses the same strong set as the appliance.
- Malware scan of a large account was stopped after 30 minutes. A scan may now run up to 6 hours at the lowest priority.
- Log rotation: the package installed its files writable by the group, and logrotate refused HostZit's file, so website logs were never rotated. All files have proper permissions; the update fixes the installed file.
- DNS-only servers: change notices went to their IPv6 addresses too, and the transfer that followed was refused when only their IPv4 addresses were entered; only the entered servers are notified now. Running the DNS-only installer a second time (e.g. to add the primary's IPv6 address) stopped half-way; it now finishes and updates the zones it already follows.
- Mail from websites without a mail server stayed in the queue for ever without a word. The admin overview now says that websites cannot send mail, and waiting messages are dropped after 48 hours.
- REST API: a customer created with a domain below another customer's DNS zone got that website; the API answers 409
domain_takennow, like the customer panel. - WordPress staging: deleting a staging copy left its DNS record behind.
- Restore points in a folder of the server: every customer's restore point page showed the error "choose SFTP or S3".
- Certificates: the check whether a name points to the server read /etc/hosts first, where Debian (and cloud-init at every boot) maps the server's own name to 127.0.1.1, and could block the panel certificate.
- Address lists (website access, blocked addresses, DNS secondaries) accepted IPv6 addresses with a zone such as
fe80::1%eth0.
Updating
Settings → Updates installs 0.9.5. New servers:
curl -fsSL https://github.com/Max-Zit/hostzit/releases/latest/download/install.sh | sudo bash
DNS-only servers set up with an older installer: run the command shown under Settings → Hosting again (it lists both addresses of the HostZit server) and enter the DNS-only servers' IPv4 and IPv6 addresses under Secondary name servers.
Appliance images: hostzit-appliance.ova, .qcow2, -vhdx.zip, .iso (checksums in SHA256SUMS-appliance).
HostZit 0.9.4
HostZit 0.9.4 — fixes from the first production servers: Let's Encrypt, fail2ban, DNS-only servers and the cPanel import, all found while moving a real website from cPanel.
Fixed
- Let's Encrypt: no certificate was issued for the panels or for websites on a fresh server (the challenge answer was not readable for nginx).
- Certificates: when a renewal failed, a still valid certificate was marked as failed and the next change of the website switched HTTPS off. It now stays in use, the reason shows on the website page and the request is repeated every six hours. Names that do not point to the server yet are left out instead of blocking the certificate.
- fail2ban: on a server without websites fail2ban refused HostZit's settings and would not start after a restart (not even for SSH).
- DNS-only servers saw only the zones that existed when they were set up: new and deleted zones never reached them. The command for a DNS-only server now lists both addresses of the HostZit server (IPv4,IPv6), so its change notices from IPv6 are accepted too.
- PHP of an account stayed off after several package saves in a row.
- Installer: PowerDNS no longer fails once on a fresh server.
- Tables: error texts (Jobs, Websites) no longer push the row out of line.
- API:
POST /api/v1/customersanswers 400 for a password that is too short instead of a failed job.
cPanel import
- Backups made with Backup → Download a Full Account Backup (
backup-DATE_USER.tar.gz) are imported likecpmove-USER.tar.gz, and the archive is recognised at once instead of after reading all of it. - Each website keeps its PHP version from cPanel when it is installed, parked domains come with their
wwwnames, and a still valid certificate is moved, so HTTPS works right after the DNS switch. - A failed import removes the account it made; a package with too little disk space for the archive is refused at once; archives that are still being copied are not offered yet.
- Imported customers set their own password without being asked for the random one; an administrator working in the customer panel is not sent to that page.
Changed
- Go 1.27.4 (GO-2026-6859 in net/http).
Updating
Settings → Updates installs 0.9.4. New servers:
curl -fsSL https://github.com/Max-Zit/hostzit/releases/latest/download/install.sh | sudo bash
Appliance images: hostzit-appliance.ova, .qcow2, -vhdx.zip, .iso (checksums in SHA256SUMS-appliance).
HostZit 0.9.3
HostZit 0.9.3 — inbound firewall, domain ownership check, usage graphs, WordPress update rollback, notifications to webhook/Telegram, an overview of several servers and one-click sign-in for EmailZit.
New
- Inbound firewall: only the ports HostZit uses accept connections (SSH and the SSH ports of sshd, DNS, HTTP/HTTPS, both panels, the mail ports when EmailZit is on the server), plus the ports you add under Settings → Security. On for new servers; existing servers show a notice and switch it on with one click.
- Domain ownership check (optional, Settings → Security): a customer proves a domain is theirs (A/AAAA record to this server, this server's name servers, or a TXT record
_hostzit-verify.<domain>) before adding a website, alias or DNS zone. - Two-factor sign-in per package: a package can require it for its customers.
- Websites: own error pages (404, 500 …), folder listings and extra file types per website.
- WordPress: when a site worked before an update and shows a server error or the "critical error" page after it, the snapshot from before is put back automatically and you get a notice.
- Usage graphs: disk, memory, CPU and disk speed over 24 hours, 7, 30 or 90 days with the package limit, in the customer panel and on the customer page of the admin panel.
- Notifications to a webhook (JSON) and a Telegram chat, also without a mail server.
- Servers: one overview of this and your other HostZit servers (version, customers, load, memory, disk, stopped services), read through their REST API; self-signed certificates are pinned by their fingerprint.
- EmailZit: HostZit is an OpenID Connect provider for its customers, so EmailZit can offer one-click sign-in with the same account; a cPanel import hands the mailboxes to EmailZit.
Changed
- HostZit is installed on Debian 13 only (the installer refuses other systems).
- The panel update waits for a running apt/dpkg instead of failing.
/packages/<not a number>answers 404.- Every change is also tested by upgrading the newest release to it on Debian 13.
Fixed (found by the security scans of this release)
- Audit log: a change was not recorded when the client dropped the connection right after sending it. It is now always recorded.
- Scheduled jobs: a change on an account with many jobs took up to a minute and loaded the server (one systemd reload and two file writes per job). It now takes a second or two; scripts of deleted jobs are removed.
Updating
Settings → Updates installs 0.9.3. New servers:
curl -fsSL https://github.com/Max-Zit/hostzit/releases/latest/download/install.sh | sudo bash
Appliance images: hostzit-appliance.ova, .qcow2, -vhdx.zip, .iso (checksums in SHA256SUMS-appliance).
HostZit 0.9.2
HostZit 0.9.2 — backups with restore points, brute-force protection, access by country, and the fixes of a full security review.
New
- Backups with restore points: nightly incremental, deduplicated and encrypted restore points of every account (restic) to a folder of the server, SFTP (key) or S3, with daily/weekly/monthly retention. Customers browse a restore point and put back files or folders (into place or into
~/restored-DATE), databases, DNS records and cron jobs, or make a restore point now. Administrators see the restore points of every account; the backup key is shown for disaster recovery. - Brute-force protection (Settings → Brute-force protection): every blocked address of the panels, SSH/SFTP and WordPress sign-ins (fail2ban jails with the panel's limits) with Unblock, and addresses that are never blocked.
- Access by country: refuse countries and continents, or allow only some, for the sign-in of the panels and SSH/SFTP (administrator) and per website (customers). Uses DB-IP IP to Country Lite (CC BY 4.0), downloaded from the panel and updated monthly.
- Certificates: customers can request a certificate again or renew it now.
- Full PHP versions everywhere; time zone settable on every server; clearer DNS settings (secondary name servers one per line); panels easier to read (spacing, grouped menus, pop-ups for deletions).
Security
- Appliance: SSH sign-in with a password is off for
hzadminuntil its first password (hostzit) has been changed at the console. Before, a newly started appliance reachable from the internet could be taken over over SSH with the default password. Update existing appliances whosehzadminpassword was never changed. - Appliance SSH: only strong algorithms (post-quantum key exchange first, no NIST curves, Ed25519/RSA host keys, encrypt-then-MAC).
- LLMNR and multicast DNS (ports 5355/5353) are switched off on every server; they were reachable from the network.
- Websites over HTTPS: TLS 1.2 only with forward secrecy and AEAD ciphers (no CBC).
- A password of a protected folder longer than 72 characters gives a message instead of an error page; the guide in the customer panel no longer links to admin pages.
- DNS: TXT records that were already quoted are no longer escaped twice; records cannot contain line breaks or control characters. A cron job with an invalid schedule from an import no longer stops the cron jobs of the whole account.
- Every change is now tested with the race detector and by fuzzing every parser of outside data; each release gets code, web (OWASP ZAP), role, TLS, SSH and appliance image scans (see
SECURITY.md).
Fixed
- Imported or moved websites keep all their settings (firewall, IP rules, protected folders, hotlink protection).
Updating
Settings → Updates installs 0.9.2. New servers:
curl -fsSL https://github.com/Max-Zit/hostzit/releases/latest/download/install.sh | sudo bash
Appliance images: hostzit-appliance.ova, .qcow2, -vhdx.zip, .iso (checksums in SHA256SUMS-appliance).
HostZit 0.9.1
HostZit 0.9.1 — fixes from a full lab test of 0.9.0 (all appliance images, a fresh install, a move between two servers, notifications).
Fixed
- Updates from the panel keep configuration files you changed (
dpkg --force-confold). Before, a changed file made the installation stop half-way and leave the package not set up. Settings → Updates now warns when that happened (rundpkg --configure -aas root). - Commands of an account (Git, WP-CLI, applications) no longer appear with their whole command line in the system journal — a Git token in a remote address was visible there to administrators.
- DNS: making a WordPress staging copy again added its DNS record twice, and PowerDNS then refused every change of that zone. The same record can no longer be added twice; the update removes existing duplicates and publishes those zones again.
- Move to another server: the check says right away when the target has no package with the same name or already has the account (before, only after the whole archive was sent).
- Log rotation: nginx kept writing into the rotated website logs (permission of the log folders), and ModSecurity kept writing into the rotated audit log. The firewall's list of blocked requests also shows yesterday's.
- Server page: nginx and PowerDNS were shown as not installed, so no notice was sent when they stopped.
- Usage: the CPU slowdown share is at most 100 %.
- Appliance: the OVA declares a guest OS that ESXi accepts for its hardware version (no warning on import); shorter label in the ISO boot menu.
Updating
Settings → Updates installs 0.9.1. If the installation from 0.9.0 stops (only when you changed /etc/logrotate.d/hostzit), run dpkg --force-confold --configure -a as root. New servers:
curl -fsSL https://github.com/Max-Zit/hostzit/releases/latest/download/install.sh | sudo bash
Appliance images: hostzit-appliance.ova, .qcow2, -vhdx.zip, .iso (checksums in SHA256SUMS-appliance).