DirectAdmin 1.63.0 has been released

fln

Administrator
Staff member
Joined
Aug 30, 2021
Messages
1,124
Hi everyone!

We're happy to announce the release of v1.63.0.

This version includes a series of bug-fixes and a couple of new features, change-log can be found here:

DirectAdmin 1.63.0

The most notable feature is user web Terminal (Pro Pack feature). The update should be automatically available for all installations subscribed to the current release channel.

We appreciate all the feedback on forums and issues reported in the ticketing system.

Thanks!
 
Hi everyone!

We're happy to announce the release of v1.63.0.

This version includes a series of bug-fixes and a couple of new features, change-log can be found here:

DirectAdmin 1.63.0

The most notable feature is user web Terminal (Pro Pack feature). The update should be automatically available for all installations subscribed to the current release channel.

We appreciate all the feedback on forums and issues reported in the ticketing system.

Thanks!

With regard to "Domain cert/key/cacert/combined to be 640 diradmin:access" bugfix in 1.63.0, what should the permissions be for the server-wide certificate files in /etc/httpd/conf/ssl.crt, /etc/httpd/conf/ssl.key and /usr/local/directadmin/conf?
 
Something that you don't tell in the documentation if the new DA installation mode is important to get the latest version 1.63.0. For example, I made reinstallation for 2 servers right now currently running DA. The first server on the left picture, I installed using auto mode and it already has version 1.63.0, the second server on the right picture I installed just 2 hours after the first server but without using auto mode and it still has an old version 1.62.9. Is there a technical reason behind this?

auto_mode_and_not.JPG

EDIT after above post:


I think this might be an issue with a mirror but I want to understand specific to this part:

The left server with the latest version 1.63.0 is using this mirror (set automatically by DA because using auto installation):

Code:
downloadserver=files-sg.directadmin.com


The right server with an old version 1.62.9 is using this predefined mirror in options.conf

Code:
downloadserver=files.directadmin.com


I thought that the files.directadmin.com should be always up to date compared to other mirrors. So, which mirror that I must use to get the latest version of DA for a new installation? Does DA randomly select a mirror for the newest build?
 
Last edited:
@fln It's ok from the previous post I already have the latest version when I redo again reinstallation just now (maybe it would take few hours to have the mirror for files.directadmin.com updated, just that I wonder which mirror would receive the update first and I would like to use that mirror permanently, in my case, files.directadmin.com is late receiving update compared to files-sg.directadmin.com)

With regard to "Domain cert/key/cacert/combined to be 640 diradmin:access" bugfix in 1.63.0, what should the permissions be for the server-wide certificate files in /etc/httpd/conf/ssl.crt, /etc/httpd/conf/ssl.key and /usr/local/directadmin/conf?

@dafang If I look at the new install they are still using old root:root permission for (/etc/httpd/conf/ssl.crt, /etc/httpd/conf/ssl.key) and for mail certificate (/etc/exim.key and /etc/exim.cert) they are using mail:mail permission.

This bug fixed might be only affected SSL for the user domains.
 
Last edited:
I got this in CB2:

DirectAdmin 1.63.0 build 6f7ee16b88a4b28517d202f826e7e348de8973d1 downgrade to 1.63.0 build a8ac330b60c49665f1df6d0e8229fa15127e04c9 is available

And think that happens several times in the last few months. Can I know why, and where to see the difference between these builds (not version 1.63.0, but builds!)? The Update Channel is still Current, no change for a while.
 
I see the same:

Server Version 1.63.0
Current Available Version 1.63.0
Update Channel Current - Default release schedule

Commit SHA 6f7ee16b88a4b28517d202f826e7e348de8973d1
Latest Commit SHA a8ac330b60c49665f1df6d0e8229fa15127e04c9
 
DirectAdmin 1.63.0 build 6f7ee16b88a4b28517d202f826e7e348de8973d1 downgrade to 1.63.0 build a8ac330b60c49665f1df6d0e8229fa15127e04c9 is available
Guys, it hot fix from DA Team, it fixed on same version
 
can someone from the staff explain why an downgrade is offered? what was the error?
 
hi everyone, we have released a hot-fix for the current version. The change was that we will no longer send a message to admins saying that update failed if DA is already running the latest version. Before this hot-fix if you tried requesting DA update again via the dataskq you would receive an email message that update failed with a message already latest. Now we will log this message in dataskq logs but will not send an email message to admins.

It is strange that custombuid treats this change as a downgrade, latest custombuild should show a message:

Code:
Latest version of DirectAdmin: 1.63.0 build a8ac330b60c49665f1df6d0e8229fa15127e04c9
Installed version of DirectAdmin: 1.63.0 build 6f7ee16b88a4b28517d202f826e7e348de8973d1

DirectAdmin 1.63.0 build 6f7ee16b88a4b28517d202f826e7e348de8973d1 to 1.63.0 build a8ac330b60c49665f1df6d0e8229fa15127e04c9 update is available.

Long story short, if we make some small changes after release we will not bump version for it. You can safely upgrade.
 
Not sure it is intended to work like this, but I just had to update DA twice through the '/admin/license' page. I was still on 1.62.9 so I clicked 'Update DirectAdmin'. The first update done was the original update. Then after reloading there was still a notification about an update. So I clicked on 'Update DirectAdmin' again and after that update I had the one with the hotfix. Is there a reason it won't update to the hotfix version in one go?
 
Thanks for reporting @Nickske00, some parts of our old infrastructure was still serving initial 1.63.0 release. With this release we are also changing how the latest version is being downloaded. We have re-synced all the mirrors and builds to provide the latest version in one go.
 
Sorry for being late.. I just discovered this Feature https://www.directadmin.com/features.php?id=3056

Web terminal feature (PRO PACK) new​

Users can access shell terminal from the control panel web interface. This allows to quickly have a CLI session without having to log-in to server over SSH.

Terminal can be accessed on user level in System Info & Files -> Terminal.

Terminal feature uses default user shell, so users with disabled SSH access will not be able to use this feature. And systems using a bubblewrap user jail would use bubblewrap in web terminal as well.

How do I disable it for all of the server?

I looked here

dont see it listed?
 
Back
Top