Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We value your experience with Plesk during 2025 Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025. Please take this short survey: https://survey.webpros.com/
On Plesk for Linux mod_status is disabled on upgrades to improve Apache security. This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.
Further update: inspecting logging settings in the Internet Information Services (IIS) Manager it turned out "x-ff" and "cf-cip" were added to the log files as custom fields at the end of each log line. I removed these fields and now the mapping is correct again and my log in Plesk looks like it...
Update:
For anyone stumbling upon this thread, I today discovered that since installing the extension all log files have "_x" added to their name (for "extended" perhaps). For example "e_ux250123.log" has become "e_ux250123_x.log". Also two new columns have appeared within the log filea: "x-ff"...
Hello @Sebahat.hadzhi, thanks for getting back to me. As for your questions:
Custom rules: yes, I do have some rules to block specific IP addresses from accessing specific ports. But I have had these for a long time and they ever caused log file problems.
Firewall: only the firewall that comes...
Last week I installed the Flex firewall manager. Ever since then the log files of my web sites have become unreadable. For example, the IP address of the source is not extracted/shown. All my IIS access entries now look like this:
Already ran the repair tool and running:
Plesk Obsidian Web...