DirectAdmin v1.667

@ViT, thanks for reporting the issue. This problem only affects pureftpd (not proftpd).
Also already reported december last year:
Your answer:
Password change after FTP and main account password desync issue is not new, but we will look into this, thanks.

Glad to see it's getting fixed now. ;)
 
Did you read the topic? Post 7?

 
Hi

Since this update, we cannot change the PHP version anymore via the users' DirectAdmin 'home' page.
When I click the button 'change', it says 'Feature disabled'.
However, it is still possible via Domain Setup > click domain > PHP Version Selecter in the upper right corner.
So it is a minor issue.

Kr
Dries
 
An update is released to fix a regression with password changing in Enhanced and legacy API (to allow changing system and FTP account passwords separately).
 
An update is released to fix a regression with password changing in Enhanced and legacy API (to allow changing system and FTP account passwords separately).

As I believe your license server is on Cloudflare and they are experiencing instability, several Directadmin installations that we manage are down after the update, displaying an error message when validating the license, and pointing to /evo/login/license-expired


How to solve this? Your license validation system should not take everyone offline due to an availability failure in your own license system.
 
DA services affected by this will retry and start automatically. It seems CF got it under control already. If CF would not be able to react quickly we have the infrastructure in place to bypass CF. Due to small scope of the incident and fast response from CF did not activate it.
 
DA services affected by this will retry and start automatically. It seems CF got it under control already. If CF would not be able to react quickly we have the infrastructure in place to bypass CF. Due to small scope of the incident and fast response from CF did not activate it.

Several servers that we manage had DirectAdmin down for an extended period of time and displayed an expired license message to all customers. This is critical and causes us great concern.

This incident makes it clear that the license validation system puts all customers at risk in the event of network instability, which can occur for a variety of reasons (routing problems, problems with Cloudflare itself, etc.). It is not expected that services will be down due to a problem with your license validation system, and only "some time" after your alternative infrastructure takes over.

It would be important for the license validation system to have a grace period, perhaps 24/48 hours, and during this period the administrator would only receive alert messages, but the panel would remain active.
 
Back
Top