Use an authorized server administrator. Record the reason for the rewrite and preserve relevant generated configuration and supported custom templates. Review whether a narrower domain-specific regeneration is sufficient before touching the shared stack.

1. Inspect the current webserver and PHP options and confirm they match the installed components.
2. Review custom templates and domain custom HTTPD fields for syntax and compatibility. Move required unsupported direct edits into a supported custom location before regeneration.
3. Run the vendor-documented da build rewrite_confs operation when a full rewrite is required. Capture the output and wait for completion rather than launching it repeatedly.
4. Read validation errors and service reload results. Correct the specific invalid custom directive or missing component before attempting another rewrite.
5. Test representative domains, including a customized site, a PHP site and a static site. Check HTTP and HTTPS behaviour and relevant service logs.

Confirm generated configuration reflects the intended options and that services remain healthy. Verify custom directives survived because they reside in supported inputs. Keep the before-and-after record for the next maintenance review.

If a manual edit disappears, restore its intent through the documented custom mechanism rather than pasting it repeatedly into generated files. If a rewrite exposes a mismatch between configured and installed components, resolve the stack inconsistency through CustomBuild. Do not run da build all blindly or delete customer configuration to clear a failure. Recover the last known good inputs and seek support with the exact error.

• Making persistent per-domain web-server changes in DirectAdmin
• Reviewing and changing CustomBuild options
• Choosing Apache, nginx or nginx with Apache in DirectAdmin
• Planning a DirectAdmin multi-server DNS setup

• DirectAdmin: Custombuild Overview
• DirectAdmin: Customize Everything