DirectAdmin 1.62.2 has been released

[DirectAdmin Support]

Hello,

We've released DirectAdmin 1.62.2 to address an issue with the new "dataskq -> directadmin" symlink update.
If you're running 1.62.1, we highly recommend updating to 1.62.2 to ensure you have a current dataskq binary.

All change can be found here:

DirectAdmin Web Control Panel Version History

directadmin.com

New Feature:

• Advanced E-Mail Tracking (Pro Pack)

Bug Fixes:

• dataskq not becoming symlink
• UTF-8 textarea encoding for Enhanced skin vacation/auto-reply, if skin uses UTF-8

Sorry for any confusion with the successive updates.

John

 

[Peter Laws]

The login page is utter bull-bull....... Can't get my password manager to work (properly).... Well done!

 

[HageHosting]

How can i test the beta (RC) Pro Pack from Direct Admin ? Better how can i install these features on my Direct Admin.
This solution didn't work --> https://help.directadmin.com/item.php?id=408

 

[Magician]

After upgrade my load average rise twice and remains on this level still. Debian 10, VPS KVM. Any suggestion?
On 1.62.1 was OK.
Is a way to downgrade DA to be sure upgrade is a reason?

 

[smtalk]

I'd suggest using "top" to see which process is the most resource intensive Are you sure it's DirectAdmin service?

 

[Magician]

Hi @smtalk ,
Start time of rising load average and CPU usgae is exactly same as I update DA do 1.62.2
/usr/local/directadmin/dataskq run every minute, by 18 seconds every time 100% CPU, four cores.
task.queue.cb.tmp is empty
I removed brute_log_entries.list, restart VPS and nothing changes
/var/log/directadmin/errortaskq.log:

2021:06:18-10:14:05: Brute Force (194.195.118.111, 'first_entry=1623753182&last_entry=1624004041&last_notify=1624004043&wordpress1=5&wordpress2=8'): Script output: [OK] The IP 194.195.118.111 was blocked with CSF.

2021:06:18-10:15:04: Brute Force error (103.147.184.193, 'exim2=1500&first_entry=1621046401&last_entry=1624001761&last_notify=1624004104'): Script output: [WARNING] The IP 103.147.184.193 is already blocked: lfd: (smtpauth) Failed SMTP AUTH login
from 103.147.184.193 (-): 5 in the last 3600 secs - Sat Jun 12 09:50:58 2021

2021:06:18-10:17:05: Brute Force (185.98.5.160, 'first_entry=1623861001&last_entry=1624004222&last_notify=1624004223&wordpress1=4&wordpress2=9'): Script output: [OK] The IP 185.98.5.160 was blocked with CSF.

2021:06:18-10:19:06: Brute Force error (212.70.149.88, 'exim2=7223&first_entry=1623848642&last_entry=1624004342&last_notify=1624004346'): Script output: [WARNING] The IP 212.70.149.88 is already blocked: lfd: (smtpauth) Failed SMTP AUTH login from
212.70.149.88 (BG/Bulgaria/-): 5 in the last 3600 secs - Wed Jun 16 15:04:41 2021

2021:06:18-10:19:07: Brute Force error (87.246.7.228, 'exim2=7738&first_entry=1623848521&last_entry=1624004342&last_notify=1624004347'): Script output: [WARNING] The IP 87.246.7.228 is already blocked: lfd: (smtpauth) Failed SMTP AUTH login from 8
7.246.7.228 (BG/Bulgaria/228.0-255.7.246.87.in-addr.arpa): 5 in the last 3600 secs - Wed Jun 16 15:02:56 2021

2021:06:18-10:20:05: Brute Force error (185.143.223.17, 'exim1=241&first_entry=1623553981&last_entry=1624004402&last_notify=1624004404'): Script output: [WARNING] The IP 185.143.223.17 is already blocked: lfd: (smtpauth) Failed SMTP AUTH login fro
m 185.143.223.17 (RU/Russia/-): 5 in the last 3600 secs - Sun Jun 13 07:14:09 2021

2021:06:18-10:21:04: Brute Force (31.130.202.240, 'first_entry=1623744301&last_entry=1624004462&last_notify=1624004463&wordpress1=4&wordpress2=8'): Script output: [OK] The IP 31.130.202.240 was blocked with CSF.

2021:06:18-10:21:05: Brute Force error (87.246.7.245, 'exim2=7190&first_entry=1623848521&last_entry=1624004462&last_notify=1624004465'): Script output: [WARNING] The IP 87.246.7.245 is already blocked: lfd: (smtpauth) Failed SMTP AUTH login from 8
7.246.7.245 (BG/Bulgaria/245.0-255.7.246.87.in-addr.arpa): 5 in the last 3600 secs - Wed Jun 16 15:04:01 2021

2021:06:18-10:21:05: Brute Force error (91.191.209.234, 'exim1=453&first_entry=1623738061&last_entry=1624004342&last_notify=1624004465'): Script output: [WARNING] The IP 91.191.209.234 is already blocked: lfd: (smtpauth) Failed SMTP AUTH login fro
m 91.191.209.234 (BG/Bulgaria/-): 5 in the last 3600 secs - Thu Jun 17 01:50:53 2021

2021:06:18-10:25:07: Brute Force error (51.38.41.19, 'first_entry=1623871621&last_entry=1624001161&last_notify=1624004707&wordpress1=4&wordpress2=10'): Script output: [WARNING] The IP 51.38.41.19 is already blocked: Blocked port 80 with Directadmi
n Brute Force Manager

2021:06:18-10:27:04: Brute Force error (51.81.152.36, 'first_entry=1623695522&last_entry=1624004821&last_notify=1624004824&wordpress1=7&wordpress2=13'): Script output: [WARNING] The IP 51.81.152.36 is already blocked: Blocked port 80 with Directad
min Brute Force Manager

Nothing different than before update

 

[Magician]

Any suggestion where to find problem / solution?

 

[DirectAdmin Support]

I'd say, run the dataskq in debug mode (assuming no task.queue entries):

cd /usr/local/directadmin
./dataskq d2000

and see what it's up to.

Another way to pull info from a running dataskq:

https://help.directadmin.com/item.php?id=402

Let us know, although don't post any "sensitive" info here

John

 

[ViT]

Hi,
I use ssl = 1, port = 1234 in directadmin.conf
The plugin's config file is at:
/var/www/html/roundcube/plugins/password/config.inc.php
$config['password_directadmin_host'] = 'ssl://localhost';
$config['password_directadmin_port'] = 1234;

Users can't change their email password from Roundcube.

 

[jca]

New Feature:

• Advanced E-Mail Tracking (Pro Pack)

Any more details on this? Not sure how to turn on and exactly what it does.

Thanks for the updates!

 

[Magician]

I'd say, run the dataskq in debug mode (assuming no task.queue entries):

cd /usr/local/directadmin
./dataskq d2000

and see what it's up to.

Another way to pull info from a running dataskq:

https://help.directadmin.com/item.php?id=402

[email protected]:/usr/local/directadmin# ./dataskq d2000
Debug mode. Level 2000

root priv set: uid:0 gid:0 euid:0 egid:0
pidfile written
starting queue
mysql1: Login Fail Match: 2021-06-19 18:56:06 1470 [Warning] Access denied for user 'aaaaa_j17'@'localhost' (using password: YES)
Tally::system_acount_is_suspended((null)): not a valid system username
Removed the following entries from ./data/admin/brute_ip.data. More than 32 hours since last entry.
listType: 0 size=64
0: 34.121.87.114
Removed the following entries from ./data/admin/brute_user.data. More than 32 hours since last entry.
listType: 0 size=64
0: address%40something%2Ecom
1: cdrom%40something%2Ecom
2: devtest%40something%2Ecom
3: ebanking%40something%2Ecom
4: factoria%40something%2Ecom
5: factusol%40something%2Ecom
6: fadiass%40something%2Ecom
7: fadillah%40something%2Ecom
8: fadl%40something%2Ecom
9: fadzaic%40something%2Ecom
10: fadzaim%40something%2Ecom
11: fahad%40something%2Ecom
12: fahim%40something%2Ecom
13: faic%40something%2Ecom
14: fail%40something%2Ecom
15: faina%40something%2Ecom
16: investigacion%40something%2Ecom
17: pay%32%40something%2Ecom
18: s%32%30%40something%2Ecom
19: screenshot%40something%2Ecom
20: se%40something%2Ecom
21: sems%40something%2Ecom
22: w%34%40something%2Ecom
23: wmail%40something%2Ecom
127.0.0.1 is in the skip list. Skipping
done queue

After "127.0.0.1 is in the skip list. Skipping" - took at least 10 sec. to finally show done queue. Probably something going on then.

If I run this command again and again then it took only 1 sec to process - without debug data, just:

[email protected]:/usr/local/directadmin# ./dataskq d2000
Debug mode. Level 2000

root priv set: uid:0 gid:0 euid:0 egid:0
pidfile written
starting queue
done queue

But if I wait then situation above occur.

 

[asadkhan]

Most of the users are reporting skin issues please have a look on it as well after reloading page it appears

Screenshot

Captured with Lightshot

prnt.sc

 

[smtalk]

Most of the users are reporting skin issues please have a look on it as well after reloading page it appears

Screenshot

Captured with Lightshot

prnt.sc

May you check if you have this problem with pre-release too? Are you sure it wasn't login-as functionality, and not a direct login as end-user?

 

[wts]

Since version 1.62 when using the Icons grid layout, I'm unable to merge access levels of admin and user. Why was this option removed? I'm the only user on the machine, without the merged access levels, this makes managing it a lot more annoying.

 

[dassels]

After updating to version 1.62.2 I'm getting these repeating errors (just a sample but come up throughout the day):

directadmin[8494]: 2021/06/26 09:37:50 error proxy request error error=context canceled url=http://unix/IMG_FAVICON
directadmin[8494]: 2021/06/26 09:38:29 error proxy request error error=context canceled url=http://unix/assets/icons/category.svg
directadmin[8494]: 2021/06/26 09:38:59 error proxy request error error=context canceled url=http://unix/assets/pages/0.js?4203770ab1481cd70fa9
directadmin[8494]: 2021/06/26 10:40:33 http: TLS handshake error from 186.10.83.78:8968: tls: first record does not look like a TLS handshake (variations of these)
directadmin[8494]: 2021/06/26 20:38:34 http: TLS handshake error from 74.120.14.56:45648: read tcp 209.50.61.195:2222->74.120.14.56:45648: read: connection reset by peer
directadmin[8494]: 2021/06/26 22:12:01 http: TLS handshake error from 192.241.214.51:45102: EOF

Everything else seems to be working ok. Just wondering if anyone else got these and whether they can be ignored or if there is something I need to investigate.

 

[alwaysbusy]

Sorry, had been seeing to late that you collect here the reviews about it.

I had been telling my review about the new colors in the grid version here:

Icon Colors on latest Direct Admin version (1.62.2)

Hi is it possible to change back the icon colors on the latest DA version? I am really used to the lovely old ones - they had been looking fresh and nice. The ones from the latest version look totally the opposite :-/ Good would be when there would at least be a option to choose between of...

forum.directadmin.com

Not the best choice the new colors :-/ - in my opionion they look faded and. The shiney old ones had been much nicer.

Would be nice to get the old colors back as option. But anyway, i can live with it - i am not so often logging into the panel. Thanks for your constant work on the panel!

Greets