Stable releases of July 25, 2026¶

Everything that shipped on the stable channel on July 25, 2026 — v2.6.12 through v2.6.15, newest first. v2.6.15 is what you install; the versions below it are how you get there.

Stable v2.6.15¶

fix(ssl): accept any of the server's public IPs in the DNS preflight

Stable v2.6.14¶

fix(repair): RepairSSL re-renders vhost before re-issue and overrides stale backoff
feat(wp-migrator): bilingual (DE/EN) UI + WordPress.org readme.txt in the plugin ZIP
feat(repair): RepairSSL reconciles TLS intent against on-disk certs
fix(nginx): heal customer vhosts referencing a missing cert on agent startup
fix(ssl): render the vhost before requesting the cert so alias (www) ACME challenges don't 404

Stable v2.6.13¶

docs(wordpress): no size limit — the import streams end-to-end
feat(wp-import): stream the migration end-to-end — no size limit
docs(wordpress): be honest about the 2 GB import limit + large-site options
docs(changelog): headline the wp-admin WordPress migration in stable v2.6.12

Stable v2.6.12¶

New & unique: migrate WordPress with wp-admin only. Take over complete WordPress instances from any host — no FTP, no SSH, no database access. Install the enconf Migrator plugin on the source, pair, done: the panel pulls files and the database automatically, provisions a dedicated MariaDB database and rewrites the URLs. This migration is stable as of v2.6.12 — including the following hardening:

docs(wordpress): document the wp-admin-only WordPress migration
fix(wp-import): don't demand a manual source URL once the plugin has paired
fix(wp-import): accept the pairing job id as a string in source-ready
fix(wp-import): pairing code uses the admin-configured panel_url, not the raw IP
fix(wp-import): idempotent WordPressInstallation registration on re-import
fix(wp-import): chown extracted files + fail loudly when the DB import fails
fix(wp-import): recover imports orphaned by a panel restart