DirectAdmin 1.54.0 has been released

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
9,158
Hello,

We're very pleased to announce the release of DirectAdmin 1.54.0.
This release has many new features and bug fixes.

All changes listed here:
https://www.directadmin.com/versions.php?version=1.540000

New Features:

Bug Fixes:

Update:
As usual, to update DirectAdmin, go to:
Code:
Admin Level -> Licenses/Updates -> Update DirectAdmin

or with the Evolution skin:
Code:
Support & Help -> Licenses/Updates -> Update DirectAdmin

Evolution Skin:
We're pleased to finally include the new Evolution into the update.tar.gz pack.
Please note that the skin is now in RC1 phase of testing, and although it should be fine to use, there could still be bugs, although we're not aware of any.
If you do find any Evolution bugs, please report them to the forum:
https://forum.directadmin.com/forumdisplay.php?f=96

John
 
Last edited by a moderator:
Regarding this feature: https://www.directadmin.com/features.php?id=2175 and regarding the option "letsencrypt_account_email=" you mention in reply #14 https://forum.directadmin.com/showthread.php?t=56852&p=290919#post290919 and your reply #9 in https://forum.directadmin.com/showthread.php?t=56852

We now have a situation where the new DirectAdmin version was released without any information and answers as to what have been done or not? We need answers on these:

1: Does letsencrypt.sh 1.1.11 include support for letsencrypt_account_email= option?

2: The email field is now removed from the SSL page https://www.directadmin.com/features.php?id=2175 - is it now needed to do a conversions for existing certificates?
 
@ditto,

I see a new default letsencrypt_account_email=0

Code:
# /usr/local/directadmin/directadmin c | grep letsencrypt_account_email=
letsencrypt_account_email=0

with DirectAdmin v.1.54.0

and

Code:
# grep letsencrypt_account_email /usr/local/directadmin/scripts/letsencrypt.sh -c
0

with letsencrypt VERSION=1.1.11
 
@zEitEr, Thank you. But it is kind of confusing, because letsencrypt.sh 1.1.11 was released long before reply #9 at https://forum.directadmin.com/showthread.php?t=56852

But I would be happy to not use that option. However I would need DirectAdmin support to answer what the consequences is? What happens with existing lets encrypt certificates, would they continue to renew with the users email address? If not, is it needed to do any conversion for existing certificates? Would it be possible to let them automatically be converted whenever they was up for renewal? (that for be the best)
 
@Erulezz, But we still need information now _before_ we upgrade DirectAdmin. We need to know what happens to existing certificates, and we need to know if it is needed to do a conversion, or if they are converted to admin email automatically when they are renewed next time?
 
Nice work on the skin!

To enable it i go to reseller level -> skin manager. Why issn't there an skin manager on admin level?
I would like to enable the skin server wide. there for i push "Set Global". But afther that. I go to admin level -> list of resellers -> just an reseller -> login. But then the old skin loads. How to fix?

Jordi
 
Just to be sure:
Code:
letsencrypt_account_email=X
does not do anything yet? LE just gets defaulted to admin email at this moment?
 
Nice work on the skin!

To enable it i go to reseller level -> skin manager. Why issn't there an skin manager on admin level?
I would like to enable the skin server wide. there for i push "Set Global". But afther that. I go to admin level -> list of resellers -> just an reseller -> login. But then the old skin loads. How to fix?

Jordi

Just select "Apply to All Users". Skin is also set in user packages, so, I'd suggest changing it there so that when you create a new user, it would use Evolution instead of the other skin.
 
Regarding this feature: https://www.directadmin.com/features.php?id=2175 and regarding the option "letsencrypt_account_email=" you mention in reply #14 https://forum.directadmin.com/showthread.php?t=56852&p=290919#post290919 and your reply #9 in https://forum.directadmin.com/showthread.php?t=56852

We now have a situation where the new DirectAdmin version was released without any information and answers as to what have been done or not? We need answers on these:

1: Does letsencrypt.sh 1.1.11 include support for letsencrypt_account_email= option?

2: The email field is now removed from the SSL page https://www.directadmin.com/features.php?id=2175 - is it now needed to do a conversions for existing certificates?
1) No, it was just added so that once we get the next LE version, it's ready to go without having to re-release DA. That's why there is no versions entry yet :)

2) Ever since LE 1.1.11 came out, it was using a single key anyway, so clearing the email is more of a bug-fix to avoid confusion. There shouldn't have been an email field since then, as it didn't work as intended. The 1.1.11 came out to address the single-key functionality confusion (shouldn't have been the email field).
Then the new letsencrypt_account_email option will eventually be added to the letsencrypt.sh to allow for the 3 scenarios described, but it's not done yet.
 
@DirectAdmin Support, Thank you for the information. We did not upgrade to letsencrypt.sh 1.1.11, but are still on 1.1.10. We wanted to wait for the next DA version to be released, to be on the safe side.

But we still need to know what happens to existing certificates installed before letsencrypt.sh 1.1.11 and before DirectAdmin 1.54? We need to know if they are going to be renewed with the users email, or if they are converted to a admin email automatically when they are renewed the next time? And will the old certificate expire if they are converted automatically? Also, if existing certificates are not automatically converted when they are up for renewal, how should be convert them manually?
 
Last edited:
1.54.0 not working!

It just freezes with the text Updating Directadmin and nothing is happening.

The same issue with my 2 Debian 7 boxes!

The update script should be more verbose, telling what its doing. And some kinf of progress bar would be nice.
 
Last edited:
1.54.0 not working!

It just freezes with the text Updating Directadmin and nothing is happening.

The same issue with my 2 Debian 7 boxes!

The update script should be more verbose, telling what its doing. And some kinf of progress bar would be nice.

Please check /var/log/directadmin/error.log, I guess it might be a license-related issue. If you're unable to sort it out, just create a ticket at tickets.directadmin.com and it will be fixed free of charge :)
 
Hi.

It started to work.

I assume it was caused by high trafic on update servers.
 
Unfortunately feature extended=yes for CMD_API_FTP doesn't work correctly.

If by CMD_FTP I set ftp account suspended, CMD_FTP shows the ftp account is suspended and ftp account is really suspended but CMD_API_FTP (using extended=yes) returns suspended=no for this account.

CMD_API_FTP returns suspended=no for all ftp accounts regardless if they are suspended or not.
 
Unfortunately feature extended=yes for CMD_API_FTP doesn't work correctly.

If by CMD_FTP I set ftp account suspended, CMD_FTP shows the ftp account is suspended and ftp account is really suspended but CMD_API_FTP (using extended=yes) returns suspended=no for this account.

CMD_API_FTP returns suspended=no for all ftp accounts regardless if they are suspended or not.
Terribly sorry about that.
Bug found/fixed. It's now in the pre-release binaries, uploading now.
Fix entry here:
https://www.directadmin.com/features.php?id=2192

John
 
Back
Top