Record the domain proxy, PHP handler and static-file settings. Identify any .htaccess rules protecting downloads or routing requests. Test in staging first when the website depends on Apache-specific behaviour.

1. Open the domain Apache & nginx Settings page and inspect Proxy mode. With proxy mode enabled, Apache remains part of the request path.
2. Review smart static-file processing and direct static extensions. Requests served directly by nginx do not pass through Apache rules, which matters for protected assets and application-controlled downloads.
3. If evaluating nginx-only hosting, first translate necessary application routing and protection into supported nginx configuration. Confirm a compatible PHP handler and application requirements.
4. Change one setting and save. Test a public asset, a protected asset, a nonexistent path and a dynamic page.
5. Measure response behaviour and errors before deciding whether the change is useful. Keep the recorded settings available for a quick return to the previous request path.

Confirm assets load with correct content types and cache behaviour, protected files remain protected, and application routes work. Compare meaningful request timings under similar load; a cached page view alone is not a reliable server benchmark.

If downloads bypass authentication or routes return 404, restore the previous settings immediately and inspect which server now handles them. Do not globally stop Apache to switch one domain. Keep session pages, carts and personalized responses out of any broad cache rule unless the application has a tested cache policy.

• Adding supported Apache and nginx directives in Plesk
• Choosing and changing a domain PHP handler in Plesk
• Diagnosing website errors with the Plesk log browser
• Understanding customized subscriptions and plan synchronization in Plesk

• Plesk: Apache And Nginx Settings