Version 1.59.4

Released: 2019-10-23

Default change: login_history_include_login_as=0 new

Relating to the option to disble logging of "login-as" logins into a Users login.history:

Option to hide login-as in login history

This change will mean the feature is turned off by default internally.

This will affect both new installs and existing installs.


If you do want Users to see the IPs of their creators, then you'd do the inverse and set:

./directadmin set login_history_include_login_as 1
service directadmin restart


Show the included deleted user bandwidth new

The reseller.usage will now log the bandwidth calculated from the Reseller's:


which is used to count the bandwidth used by a User prior to their deletion (so you're not also deleting the bandwidth usage)

This is an existing feature from DA 1.28.2:


There was a fix in 1.59.2 where lines with missing newline character are now correctly read in, causing your Reseller's bandwidth to increase to the correct value, now including the deleted User bandwidth.

This alone could cause confusion, so we've added a new field to the reseller.usage file, so it can be displayed to Admins when viewing the Reseller usage.

This count will be a sub-set of the total bandwidth already shown.

The variable in the reseller.usage file will be:


which, like the bandwidth option, is in Megabytes.

This value is only there for efficiency. It's recounted each night based on the bandwidth.reseller.tally file.

If the value deleted_user_bandwidth= value is missing or 0, then the field will not be shown.

The monthly reset clears the bandwidth.reseller.tally file for anyone who's deletion time is within the previous stats window.

CMD_DNS_MX: cannot delete MX records from MX records page fixed

Relating to the new feature for duplicating values to domain pointers, added in 1.59.2:

Domain Pointers option to receive duplicate dns entries from master domain (SKINS)

fixed to support "select0" format for selection, instead of only "mxrecs0", like the DNS Management page uses for MX records.

FreeBSD: ssh keys: use <<EOL... EOL instead of <<<'...' fixed

When getting the fingerprint of a key, DA was using <<'...' for passing the key to stdin.

FreeBSD's /bin/sh does not like this, so it's been changed to be:




for FreeBSD

Port on referrer check override breaks match fixed

Related to this feature:

Referer check override files (PLUGINS)


where you can have a list of allow referers which are allowed, if the port was added to the end of the string:

the match would have been incorrect, like:

and the "host" check would have been looking at the entire thing "" when it should have just been "".


Ensure curl supports --ftp-ssl-reqd or --ssl-reqd in ftp_upload.php/ftp_list.php fixed

Various versions of curl support various different options to ensure FTPS is using TLS.

Some support one or the other, while some don't support any.

New checks in the scripts:



to use whichever is supported.

if ${CURL} --help | grep -m1 -q 'ftp-ssl-reqd'; then
elif ${CURL} --help | grep -m1 -q 'ssl-reqd'; then
Last Updated: