Skip to content

Knowledgebase

Choosing Apache, nginx or nginx with Apache in DirectAdmin

control-panels, web-hosting

Choose a DirectAdmin web-server stack according to application compatibility, operational experience and measured workload. Apache, nginx and nginx in front of Apache process configuration differently. A stack replacement affects hosted customers and should be treated as a migration, not a quick performance toggle.

Information to have ready

Use an authorized administrator on a self-managed server. Inventory application rewrites, .htaccess rules, PHP handlers, custom virtual hosts and caching. Keep recoverable backups and test the target stack on a representative nonproduction server.

01 Choose Apache, nginx or nginx with Apache in DirectAdmin

  1. Inspect the current webserver CustomBuild option and supported values with da build opt_help.
  2. Choose Apache when applications depend on its configuration model, or assess nginx with Apache when a reverse-proxy arrangement fits. A standalone nginx setup requires explicit handling of Apache rewrite and access rules.
  3. Review memory requirements and handler compatibility. Do not assume a commercial LiteSpeed configuration and OpenLiteSpeed behave identically if evaluating those alternatives.
  4. Use the current vendor-documented sequence to set the target webserver option, build the selected service, build compatible PHP where required and rewrite configuration. Perform this in a scheduled maintenance window.
  5. Test representative domains and custom directives before declaring the change complete. Keep the original configuration and a practical return-to-service plan.

How do I test the selected web-server stack?

Check redirects, protected directories, static downloads, PHP requests and application routing. Measure errors and resource use under comparable load. Confirm certificate handling and customer configuration controls still behave as intended.

Troubleshoot unexpected results

If an application breaks, identify whether the cause is a missing rewrite, different static-file handling or runtime mismatch. Do not delete .htaccess files or disable security to make the symptom disappear. Revert through the supported stack configuration if compatibility cannot be established, recognizing that service rebuilds and restarts need a controlled recovery window.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support