Use an authorized administrator on a self-managed DirectAdmin server. Keep a recent recoverable backup, console access and a maintenance window. Review the current release notes, installed customizations and application compatibility before changing a shared runtime.

1. Open administrator-level CustomBuild > Updates, or run da build versions in an administrative shell to inspect available component updates.
2. Record installed versions and the components you intend to update. Review custom version pins and custom build templates that can affect the result.
3. Update a selected component through the supported control when a narrow change is appropriate. Use da build update_versions only after reviewing the full set it will change.
4. Monitor the build output and preserve the first meaningful failure. Do not launch a second build while the first is still running.
5. Review DirectAdmin application updates and operating-system security updates through their own supported maintenance workflows. Recent DirectAdmin releases do not update the panel application through CustomBuild update_versions.

Confirm the intended component versions, service health and representative customer websites. Test PHP applications, mail and database connectivity as relevant to the changed components. Record any restart or reboot still required by system-package maintenance.

If a build fails, check the exact dependency, download or configuration error before retrying. da build all rebuilds the configured stack and is not a routine first response to one failed update. Restore a tested configuration or use the supported component recovery path if service is affected. Preserve logs and avoid silently pinning vulnerable versions indefinitely.

• Reviewing and changing CustomBuild options
• When to rebuild DirectAdmin web-server configuration
• Diagnosing DirectAdmin license and update failures
• Adding a PHP extension through DirectAdmin CustomBuild

• DirectAdmin: Upgrading Services
• DirectAdmin: Version 1
• DirectAdmin: Updating Da