Use a trusted authenticator device and confirm the account recovery route. Keep the current panel session open until a new login succeeds. Current Evolution navigation differs from older password-profile screenshots, so use the interface search for Two-Step Authentication if necessary.

1. Open the account Two-Step Authentication page and start enrollment.
2. Add the displayed setup secret to a supported authenticator using its QR or manual entry workflow. Keep the secret private; anyone holding it can generate matching codes.
3. Enter a current code to confirm setup. Check automatic time synchronization on the device if codes are rejected.
4. Store the scratch or recovery codes offered by the installed version in protected storage separate from the authenticator device. Do not rely on an old tutorial claim that they expire on a specific schedule.
5. Test a fresh login in a private window. Complete the password and second-factor steps and confirm the expected account opens before closing the original session.

Confirm the normal login requires the second step and that recovery information is accessible to the authorized owner. Review trusted-device settings deliberately, especially on shared computers. Keep login keys inventoried separately.

For repeated code failure, verify the correct account entry and device time before retrying. If the device is lost, use the supported recovery procedure or authenticated support route. Do not share recovery codes in tickets or disable server-wide protection to recover a single user. After using a recovery credential, review whether the remaining recovery set should be regenerated.

• Creating a restricted DirectAdmin login key
• Investigating a DirectAdmin brute-force block
• Logging in to DirectAdmin securely
• Adding a PHP extension through DirectAdmin CustomBuild

• DirectAdmin: Securing Da Panel
• DirectAdmin: Version 1
• DirectAdmin: Version 1
• DirectAdmin: Version 1