Plesk administrator command
Use httpdmng to regenerate one domain’s web-server configuration after validating the source settings
This command requires root access and is not for UKC shared-hosting customers. Plesk Obsidian uses httpdmng to rebuild generated Apache and nginx configuration for a domain. Correct invalid custom directives first, back up relevant configuration and reconfigure only the affected domain.
When is a single-domain reconfiguration appropriate?
Custom directives changed
You corrected a domain-specific Apache or nginx directive and need Plesk to regenerate its active configuration.
Generated files are stale
The Plesk source settings are correct but the generated virtual-host configuration no longer matches them.
One domain is affected
Other subscriptions work and the evidence points to one virtual host, so a server-wide rebuild would be unnecessarily broad.
Not a content fix
httpdmng does not repair PHP code, WordPress, DNS, certificates or an incorrect document root selected in the application.
Administrator procedure
- 1Capture the failure
Save the exact domain, Plesk action, configuration-test output and relevant log lines before changing anything.
- 2Back up custom configuration
Copy the domain’s custom vhost and nginx directives and confirm the intended values in Plesk.
- 3Reconfigure one domain
Run the supported Plesk utility with the exact domain name:
/usr/local/psa/admin/sbin/httpdmng --reconfigure-domain <domain_name> - 4Review the result
Read command output, run web-server configuration tests and inspect newly generated files and service logs.
Post-change checks
| Check | Expected result |
|---|---|
| HTTP and HTTPS | The correct website answers on both schemes and redirects only as intended |
| Certificate | The requested hostnames are covered and no mismatch is shown |
| PHP handler | The domain uses the configured version and handler without gateway errors |
| Logs | No new syntax, upstream or permission error appears during a test request |
| Other domains | Unrelated subscriptions continue operating normally |
Plesk applies changes made through Web Server Settings automatically in normal use. Manual httpdmng execution is primarily a recovery or advanced-administration step.
httpdmng questions
Should I reconfigure all domains?
Not when the issue is isolated. Start with the smallest supported scope and expand only when evidence shows a wider generation problem.
Will the command overwrite custom files?
Plesk regenerates derived configuration from its source settings and supported custom directive files. Back those up and understand which layer is authoritative before running it.
What if it reports an error?
Do not repeatedly rerun it. Correct the named directive, missing resource or source setting, then test again.
Keep the repair narrow
Validate first, reconfigure once and inspect the generated result
If this is a UKC shared-hosting domain, send the evidence to support instead of using server commands.