• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Dukemaster

Regular Pleskian
Hi friends of PLESK,
Since I used to take the chance trying something total different according to PLESK by using ❝only Nginx❞ the more I realized that Plesk offers a new fascinating technical way. But also is PLESK basically built for using Apache and Nginx together as a perfect bundle for security and performance reasons (e.g. caching).
There is no documentation on internet for the stand-alone usage of Nginx by PLESK, except by @UFHH01, @TimReeves, (fore sure there are more, but those members don't share their experiences).
By using the option "without Apache" and "only Nginx" for domains you will realize that controlpanel won't stop offering obsolet options for Apache.
An idea would by deactivating all of these options which are unnecessary and confusing some user, mostly the "smart static files processing" option.
Smart static files processing is a double-directive if someone is using only nginx ! ! !
Because it's still refering to Apache in background.

There is place for some user-friendly changes in the panel interface.
Screens show more as thousands words.

PLESK + Nginx = ❝Katjuscha❞ ♥ ␆.jpg PLESK + Nginx = ❝Katjuscha❞ ♥ ␅.jpg PLESK + Nginx = ❝Katjuscha❞ ♥ ⓵.jpg
 
Last edited:
Back
Top