v1.0.33

• Improved Docker support
• Improve installers and add unified upgrade framework
• Add unattended installer support and unified provisioning variables

v1.0.32

• Added Revolut and Revolut Pay gateways support
• Dockerized Namingo Registry
• Speed optimizations in CP and EPP
• Code cleanup in various locations
• Improved error log noise reduction
• Improved registrar management forms and IP whitelisting
• Improved sections of documentation
• Improved atomicity of financial operations
• Fixed rare domain create EPP issue
• Fixed potential password create bug during installation
• Fixed SMD validation
• Fixed authorizations
• Fixed transaction cleanup
• Fixed internal IP checks
• Panel price estimation fixes

After upgrade, logout from panel and login again.

v1.0.31

• Added support for FreeBSD 15.1
• Improved domain validation
• Fixed session issues
• Fix email sending after message queue refactor
• Breadcrumb fix
• Fixed failing support for Sumsub
• Fixed disabled allocation tokens notification

v1.0.30

Namingo Registry 1.0.30 introduces several major platform updates, including PostgreSQL production support, Ubuntu 26.04 and PHP 8.5 support, significant EPP and payment-system refactoring, improved access controls, and a number of security and usability improvements.

Added

• Added support for Ubuntu 26.04 and PHP 8.5 as the default PHP version.
• Added production support for PostgreSQL.
• Added the ability for administrators to transfer domains between registrars. Fixes #245.
• Added support for a configurable list of domains that never expire. Fixes #244.
• Added differentiated user-level access controls for the Control Panel. Fixes #221.
• Added full support for RFC 9154. Fixes #224.
• Added ALTCHA CAPTCHA support, replacing the legacy CAPTCHA implementation. Fixes #235.
• Added the option to skip installation of the WHOIS port 43 server. Fixes #246.
• Added balance display to the Control Panel.

Improved

• Aligned the Control Panel with the Foundry framework.
• Refactored the payment system.
• Refactored the EPP server.
• Improved data export functionality. Fixes #247.
• Improved the NIS2 contact validation flow.
• Improved Redis-backed session storage support in the Control Panel.
• Updated the mailer system.
• Updated Content Security Policy configuration.
• Improved the installer.
• Improved various parts of the user interface.
• Updated documentation.
• Improved date formatting.
• Added numerous smaller fixes, reliability improvements, and code cleanups throughout the platform.

Changed

• Updated the installer and installation workflow.
• Updated dependencies and platform integration where required for PHP 8.5 and Ubuntu 26.04 support.

Removed

• Removed Alpine Linux support, as the implementation was incomplete.
• Removed SQLite support.

Upgrading from Namingo Registry 1.0.29

Start the upgrade using the standard Namingo Registry upgrade script:

bash <(wget -qO- https://namingo.org/upgrade.sh)

After the automated upgrade completes, a few manual configuration changes are required.

1. Configure the Message Broker API token

Generate a new random token:

php -r 'echo bin2hex(random_bytes(32)), PHP_EOL;'

Keep the generated value and use the same token in both the Registry automation configuration and the Control Panel.

Registry configuration

Open:

/opt/registry/automation/config.php

Copy the complete:

// Message Broker Configuration

block from:

/opt/registry/automation/config.php.dist

into your existing config.php, while retaining your existing configuration values.

Set msg_api_token to the token generated above:

'msg_api_token' => 'THE_GENERATED_VALUE',

Control Panel configuration

Add the same token to:

/var/www/cp/.env

MSG_API_TOKEN=THE_GENERATED_VALUE

After updating .env, clear the Control Panel application cache and restart the 2 msg_ services.

---

2. Update Caddy security headers

Edit:

/etc/caddy/Caddyfile

The obsolete Features-Policy header should be removed from the RDAP, WHOIS, and Control Panel blocks.

RDAP block

Remove the existing Features-Policy, Content-Security-Policy, and Permissions-Policy lines and replace them with:

Content-Security-Policy "default-src 'none'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; img-src https:; font-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'none'; form-action 'self'; worker-src 'none'; frame-src 'none';"
Permissions-Policy "accelerometer=(), autoplay=(), camera=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(self), usb=()"

WHOIS block

Remove the existing Features-Policy, Content-Security-Policy, and Permissions-Policy lines and replace them with:

Content-Security-Policy "default-src 'none'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; img-src https:; font-src 'self'; style-src 'self' 'unsafe-inline' https://cdnjs.cloudflare.com; script-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net; connect-src 'self' https:; form-action 'self'; worker-src 'self' blob:; frame-src 'none';"
Permissions-Policy "accelerometer=(), autoplay=(), camera=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(self), usb=()"

Control Panel block

Remove the existing Features-Policy, Content-Security-Policy, and Permissions-Policy lines and replace them with:

Content-Security-Policy "default-src 'none'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; connect-src 'self'; img-src https: data:; font-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; form-action 'self'; worker-src 'none'; frame-src 'none';"
Permissions-Policy "accelerometer=(), autoplay=(), camera=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(self), usb=()"

After changing the Caddy configuration, validate it and reload Caddy:

caddy validate --config /etc/caddy/Caddyfile
systemctl reload caddy

---

3. Review the new settings

Log in to the Namingo Registry administration interface and review the newly added and updated settings pages.

Some new options require an administrator to explicitly choose the desired behavior after upgrading.

---

4. Migrate WHOIS CAPTCHA to ALTCHA

Namingo Registry 1.0.30 replaces the previous CAPTCHA implementation with ALTCHA.

Open:

/var/www/whois/config.php

Remove the following configuration option:

'ignore_case_captcha' => ...,

After the existing ignore_captcha setting, add:

'altcha_hmac_secret' => '',
'altcha_cost' => 10000,

Then update the WHOIS Composer dependencies:

cd /var/www/whois
composer remove gregwar/captcha
composer require altcha-org/altcha:^2.1

Generate a secure ALTCHA HMAC secret:

openssl rand -hex 32

Place the generated value in /var/www/whois/config.php:

'altcha_hmac_secret' => 'THE_GENERATED_VALUE',
'altcha_cost' => 10000,

The upgrade to Namingo Registry 1.0.30 is complete once these configuration changes have been applied.

v1.0.29

• Added support for BIND 9.20, Knot 3.5, offline zone signing; fixed #228
• Add production-ready WebAuthn Level 2 passkey support
• Redesigned panel front page, settings, reserved names, registrar management, and hosts pages
• Default currency is now EUR; fixed #242
• Improvements to the zone generator
• Improved translations, logout flow, and layout
• Fixed error when audit table is not active
• Updated Tabulator to v6.5

** OpenDNSSEC is now removed ahead of project closure, will be replaced with Cascade once production-ready**

v1.0.28

Upgrade to this version is recommended as it has important third party package upgrades.

• Added ability to disable WHOIS check in web whois
• Add configurable DNS reload control
• Fixed application approval issue in some cases
• Improved get_client_location
• Improve DNSSEC dropdown labels with numeric prefixes
• Third party package upgrades.
• Improved documentation
• Fixed various issues

v1.0.27

This is a stability and hotfix release issued shortly after v1.0.26 to address several critical issues affecting production environments. We recommend all users upgrade immediately.

Critical Fixes

• Registrar Sessions: Fixed incorrect registrar session initialization during login, which would lead to HTTP 500 errors.
• Installer (PHP/PPA): Resolved failures during PHP installation caused by PPA setup inconsistencies across providers.
• Domain Lifecycle: Fixed domain lifecycle script issues and incorrect domain deletion behavior.
• Cron Automation: Fixed cases where cron automation could fail with errors.

Improvements

• Installer Reliability: Improved installer robustness to prevent failures across different environments and hosting providers, with better handling of edge cases and dependencies.

v1.0.26

• ui: unify interface across Namingo
• Centralize cron configuration and improve update safety
• Align CDS scanner with RFC 7344, RFC 9615, and DS automation operational guidance (still some testing needed)
• Improve DNS zone generation by adding validation checks
• Documentation update
• Contact interface improvement
• Several bugs fixed

Post-update: cron_config.php is deprecated. Review /opt/registry/automation/config.php and move existing settings from /opt/registry/automation/cron_config.php into this main config file.

v1.0.25

• Added full Debian 13 support.
• EPP Poll interface improvement.
• Documentation improvement.
• IPv6 fix for whitelisted IPs.
• Fixed bug in EPP host update.
• Fixed IDN script tag in escrow.
• Fixed issue with reserved names not being checked.
• Fixed #230.
• Fix sed password replacement escaping in installer
• refactor(installer): migrate mysql commands to mariadb tools

v1.0.24.1

Update only for gTLDs. If you are a ccTLD, you can skip it.

• Fixes in EPP server for keyData mode and minimum data set.