DirectAdmin v1.643 has been released

[Dettol]

@Dettol, PHP 7.4.32 is shipped with DA current upgrade versions.txt file. Old CustomBuild available on the files.directadmin.com mirrors is still having PHP 7.4.30. I think something on your system is pulling versions.txt from files servers.

# da v
DirectAdmin v.1.643 8c5c161f99047c9098e7bf4f89005929dea3942e

# grep php74 /usr/local/directadmin/custombuild/versions.txt
php74:7.4.32:

# curl -s https://files.directadmin.com/services/custombuild/versions.txt | grep php74
php74:7.4.30:

So I have two hypothesis to explain such behaviour:

1. You are still having old Custombuild script version (that still pulls versions.txt from mirrors). Please check if checksums match:

# md5sum /usr/local/directadmin/custombuild/build /usr/local/directadmin/custombuild/versions.txt
b8f5628041c6117c176ed3695b90f5d0  /usr/local/directadmin/custombuild/build
a32e7f4f677a6bc15d9dd0746512c26a  /usr/local/directadmin/custombuild/versions.txt

2. You have some cronjob or other 3rd party tool that automatically pulls versions.txt from mirrors.

You right:

# md5sum /usr/local/directadmin/custombuild/build /usr/local/directadmin/custombuild/versions.txt

543c5d8d904e9b38a0b1498c9328c46d /usr/local/directadmin/custombuild/build
10376b504020464fd6aeed5ce6b45064 /usr/local/directadmin/custombuild/versions.txt

but I clicked "Update Custombuild" or "Update CustomBuild Script & Versions (only)
and staill same

#=#=#                                                                         
##O#-#                                                                        

##########################################################                81.0%
######################################################################## 100.0%
Extracting custombuild.tar.gz...
#=#=#                                                                         

######################################################################## 100.0%
#=#=#                                                                         

######################################################################## 100.0%
#=#=#                                                                         
##O#-#

 

[Dettol]

[root@myserver custombuild]# md5sum /usr/local/directadmin/custombuild/build /usr/local/directadmin/custombuild/versions.txt
543c5d8d904e9b38a0b1498c9328c46d  /usr/local/directadmin/custombuild/build
10376b504020464fd6aeed5ce6b45064  /usr/local/directadmin/custombuild/versions.txt
[root@myserver custombuild]# wget -O /usr/local/directadmin/custombuild/build http://files1.directadmin.com/services/custombuild/2.0/custombuild/build
--2022-10-03 16:18:32--  http://files1.directadmin.com/services/custombuild/2.0/custombuild/build
Resolving files1.directadmin.com (files1.directadmin.com)... 104.128.54.74
Connecting to files1.directadmin.com (files1.directadmin.com)|104.128.54.74|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 901488 (880K)
Saving to: '/usr/local/directadmin/custombuild/build'

100%[======================================>] 901,488      175KB/s   in 6.0s

2022-10-03 16:18:39 (147 KB/s) - '/usr/local/directadmin/custombuild/build' saved [901488/901488]

[root@myserver custombuild]# /usr/local/directadmin/custombuild/build update
######################################################################### 100.0%
######################################################################### 100.0%
######################################################################### 100.0%
######################################################################### 100.0%
Extracting custombuild.tar.gz...
######################################################################### 100.0%
######################################################################### 100.0%
######################################################################### 100.0%
######################################################################### 100.0%
######################################################################### 100.0%
######################################################################### 100.0%
######################################################################### 100.0%
######################################################################### 100.0%
######################################################################### 100.0%
Cronjob frequency: daily
Automatic notifications: no
Automatic updates: no
Installing sa-update cronjob...
Downloading             sa-update.sh...
######################################################################### 100.0%
Automatic SpamAssassin rule updates: daily
[root@myserver custombuild]#  md5sum /usr/local/directadmin/custombuild/build /usr/local/directadmin/custombuild/versions.txt
543c5d8d904e9b38a0b1498c9328c46d  /usr/local/directadmin/custombuild/build
10376b504020464fd6aeed5ce6b45064  /usr/local/directadmin/custombuild/versions.tx
[root@myserver custombuild]#   ./build version
2.0.0 (rev: 2945)

 

[fln]

@Dettol, CustomBuild both the script and the versions.txt file on the mirrors servers are old now, If you upgrade to the latest DA version you do not need to update the script or versions.txt manually. Please just upgrade DA to the latest version (it will pull the latest CB script and versions.txt).

If you pull CB from mirrors you are getting the old version.

Would be great to move this discussion to a new thread.

 

[Richard G]

PHP 7.4.32 is shipped with DA current upgrade versions.txt file.

I'm getting confused now. How about my question?
Previously we got a notice that an update of PHP (or apache or mysql or whatever) by using the custombuild cronjob.

We didn't get any mail about any update at the moment.

Does this mean it's now a requirement to update DA to get newer versions.txt so the cron can see the updates?
And what if we do want the minor update notices but do not want to update DA at this point?

@Dettol The chance is very big that if I do just a ./build update and ./build update_versions that DA will be updated too. That is what we just don't want to do at the moment.
So I can't use the force command either until we want to update DA. Which is soon, but not right now.

@fln we posted at the same time, if my question also needs to be in that new thread, please move the posts.

 

[Nickske00]

If I understand it correct, custombuild is now shipped with DA (and with DA updates), so the filemirrors will not be updated anymore (maybe only the software available, but custombuild script and versions.txt will not be offered anymore on the mirrors). So everytime there is a new version for something a hotfix release for DA will be made.

This is how I understand it at the moment.

 

[fln]

@Richard G, right now CustomBuild email based notifications for new software will work as before, but it will not see new versions if DA is out of date. This would mean the following flow:

• Once DA is upgraded CB will notice new version and start sending email notifications until new versions are installed.
• Once all software is up to date CB cron-job will not see any software upgrades available and will not send any emails.
• If there is new DA with updated versions.txt it will be visible for CB only after DA upgrade.
• In case of security issue we would release a DA hot-fix release (new build, same DA version) with updated versions.txt and old CB cron job start sending emails about new software until it is installed, even without upgrading DA to the latest version.

We are planing to move this cron-based CB email notification about new versions from CB into DA core.

 

[Dettol]

@Richard G, right now CustomBuild email based notifications for new software will work as before, but it will not see new versions if DA is out of date. This would mean the following flow:

• Once DA is upgraded CB will notice new version and start sending email notifications until new versions are installed.
• Once all software is up to date CB cron-job will not see any software upgrades available and will not send any emails.
• If there is new DA with updated versions.txt it will be visible for CB only after DA upgrade.
• In case of security issue we would release a DA hot-fix release (new build, same DA version) with updated versions.txt and old CB cron job start sending emails about new software until it is installed, even without upgrading DA to the latest version.

We are planing to move this cron-based CB email notification about new versions from CB into DA core.

I'm wondering: DA will use some dns like : 8.8.8.8, 1.1.1.1 for checking update(example: Let's Encrypt will use it for renew / get new cert)? if they hacked some isp's dns, and direct to the fake server and let some user download some malware inside version...

 

[Richard G]

We are planing to move this cron-based CB email notification about new versions from CB into DA core.

So this will mean we loose the option to not update DA for a little while, because we won't see any php or apache etc. updates then?
That might look good. However, since lately all DA updates came with several issues we're not quite eager to update DA directly, so it's pity this option is lost now.
I understand the decision, but it's a pity at the moment and hope for improvement on new DA releases.

Thank you for the clear answer.

 

[fln]

@Dettol integrity of updates ensured by a TLS layer. DA will refuse to upgrade if it can not download it over TLS from download.directadmin.com.

@Richard G, I agree, the recent pain of upgrades comes form us deprecating some old DA functionality. All these changes are a building blocks to make DA more robust and stable, especially for Evolution.

 

[Joriz]

We currently still see a lot of issues with the Evo skin Dark Mode of DirectAdmin. Most of the plugins (e.g. CloudLinux selector plugins) are also not ready for Dark Mode and still show up bright and white.

Is there any way to disable Dark Mode globally? Dark Mode still seems like a beta feature now.



Also there seems to be no way to disable of modify the (?) documentation button. Currently this button points to documentation to DirectAdmin itself where also other companies are endorsed. We want to remove this button or point it to our own documentation.
The user_helper variable seems to be ignored for this button.

 

[Dettol]

We currently still see a lot of issues with the Evo skin Dark Mode of DirectAdmin. Most of the plugins (e.g. CloudLinux selector plugins) are also not ready for Dark Mode and still show up bright and white.

Is there any way to disable Dark Mode globally? Dark Mode still seems like a beta feature now.



Also there seems to be no way to disable of modify the (?) documentation button. Currently this button points to documentation to DirectAdmin itself where also other companies are endorsed. We want to remove this button or point it to our own documentation.
The user_helper variable seems to be ignored for this button.


View attachment 6012

The best way is you ask for dev of plugins, even directadmin help you do this, but you will get another problem after that.

 

[fln]

New build af8c913146c2b78ca749a5177867f117f20a8829 is released. It has a CustomBuild fix for new DA installations on AlmaLinux 9. Without this fix MariaDB installation used to fail.

 

[dafang]

Also there seems to be no way to disable of modify the (?) documentation button. Currently this button points to documentation to DirectAdmin itself where also other companies are endorsed. We want to remove this button or point it to our own documentation.
The user_helper variable seems to be ignored for this button.

@fln, will this issue be dealt with in 1.643? Or is there a workaround to have our own help documentation?

 

[fln]

@dafang as a workaround you can add a link to your own documentation page as a custom menu entry. Having single variable that replaces all page scoped documentation (the old user_helper approach) is not great, because it extremely hard to keep custom help pages in sync.

Could you help us identify which official DA help pages endorses other companies? Would be an improvement to make them neutral.

If you really want to control per-page help links, we could consider it as new menu customization feature. This new feature would allow to specify custom help link, or remove the link completely on a per page basis. But we have no plans on reviving user_helper.

 

[johannes]

to control per-page help links, we could consider it as new menu customization feature. This new feature would allow to specify custom help link, or remove the link completely on a per page basis.

Yes please! +++

 

[dafang]

If you really want to control per-page help links, we could consider it as new menu customization feature. This new feature would allow to specify custom help link, or remove the link completely on a per page basis.

That would be really really really good (an understatement of joy)

 

[dafang]

Also there seems to be no way to disable of modify the (?) documentation button. Currently this button points to documentation to DirectAdmin itself where also other companies are endorsed.

Could you help us identify which official DA help pages endorses other companies? Would be an improvement to make them neutral.

Will leave that to @Joriz to reply to, as I had only quoted his statement.

 

[fln]

A new build 7bb57d5b80b660eb81ae54a4078f30531a26f93c has a CustomBuild fix for installing phpMyAdmin on servers with PHP 7.1. Latest phpMyAdmin 5.2 requires PHP 7.2+ and fallback on systems with PHP 7.1 were not working properly. New build fixes the issue.

 

[Ohm J]

I think, it should seperate change log when custombuild update like in the old day. it easy to find/read.

 

[fln]

@jamgames2 you are right, it was bit wired writing this hot-fix note.

The expected flow is to list all CB improvements in a shared DA + CB change-log and use hot-fix releases only to bump versions.txt for high impact security fixes. Things were a bit chaotic on a first CB+DA merge release, but I think we will polish out the release and change-log flow.