Version 1.63.1

Released: 2021-11-07

Add CLI for backuping new

Due to dataskq requiring active license in order to run, a couple of new CLI options are introduced to provide the ability for creating backups on a server with a license of any state.

To create all backups in /home/admin/admin_backups:

/usr/local/directadmin/directadmin admin-backup --destination=/home/admin/admin_backups

To create backups for specific user(s):

/usr/local/directadmin/directadmin admin-backup --destination=/home/admin/admin_backups --user=username1 --user=username2

Extend dataskq logging to file improved

When dataskq is executed by a cron job all errors are encountered during the execution are logged in /var/log/directadmin/errortaskq.log file.

Some errors were omitted from this file and visible only when running dataskq manually with debug flag turned on.

This issue is addressed and now all error messages are captured in the /var/log/directadmin/errortaskq.log file.

Use more secure DNSSEC key types by default improved

Starting this release we will try using ECDSAP256SHA256 type keys if the system supports it. Oder system will continue using RSASHA256 keys.

This follows RFC 8624open in new window recommendation.

Extend dataskq to only work with a valid license improved

From now on, in order to run dataskq, it is required that Directadmin control panel is running with a currently active license.

Fix DNSSEC support for Debian 11 fixed

Latest version of dnssec tools from bind package no longer supports -r parameter. This caused DNSSEC helper shell script to fail on Debian 11 systems.

Helper script is updated to detect -r flag availability.

Fix "session_minute" config setting validator fixed

Validator for session_minutes config parameter used to have bug. Trying to change this variable using command line used to result in:

> /usr/local/directadmin/directadmin set session_minutes 600
Error with the current values:
Unknown type ir1:35791 when verifying session_minutes=600

This issue is fixed and session_minutes can now be changed using CLI.

Exclude non-domain files when simple_disk_usage=1 fixed

The purpose of the simple_disk_usage=1 feature is to reduce file/folder traversal to get disk usage on a per-domain basis, which includes all files, owned by apache or the User.

It thus relies on the system quotas for immediate usage numbers, at the expense of knowing the per-domain usage.

This change also excludes non-domain files inside ~/ (outside of ~/domains, ~/imap, etc) as traversal there too was not required.

Ticket: 36091

Remove SSLCACertificateFile if SSLCertificateFile is cert.combined (TOKENS) fixed

For all webservers, if the certificate used points to a cert.combined file, there is no need to also load in the CA variant file, as it's already part of the combined file.

For User httpd.conf, nginx.conf, openlightspeed.conf files, if the CERT token ends with .combined, the CAROOT token will remain blank.

For IPs files:

  • /usr/local/lsws/conf/ips.conf
  • /usr/local/lsws/conf/listeners.conf
  • /etc/httpd/conf/ips.conf
  • etc

the same applies, but would set CACERT to be blank, if CERT ends with .cert.combined.

Database "all user list" empty if "mysql_detect_correct_methods=0" fixed

Changed to how the listing of all Users uses information_schema.schema_privileges when mysql_detect_correct_methods=1 caused a but for the "all databases" case with mysql_detect_correct_methods=0.

The per-DB list of all Users was not affected.

The mainly just affects the "Use existing User" option for database creation where the list was empty for mysql_detect_correct_methods=0 case.

Ticket: 35227

Fix E-mail Tracking parsing resulting in Directadmin crash fixed

E-mail Tracking parsing used to have a bug which caused Directadmin to crash when presented with specific email log which is shorter than most. E. g.:

2021-01-01 03:00:00 XXXXXX-XXXXXX-XX ** root@server.com <master@server.com>: retry timeout exceeded

The issue is fixed, parsing itself is made more robust and less prone to error in the future.

Ticket: 36003

Allow underscore in python module name for Nginx Unit app fixed

When creating python application for Nginx Unit, input validation did not allow underscores in applictaion module name.

This release fixes this issue.

Ticket: 36008

Change su location from /usr/bin/su to /bin/su for Userd and terminal in linux systems fixed

On older systems (CentOS 6 and Debian 9) did not have /usr/bin/su needed for Userd and terminal features.

su exectution path has been changed to /bin/su to better conform to filesystem hierarchy standard.

Last Updated: