• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

server path to access log files?

P

pmars

Guest
My site management company needs to know where the access log files are located on my server. Automated IP blocking and access abuse depends on finding the location of these files and adding a script to read them. They say they cannot find them in the usual locations for apache servers... what's going on here?

Yes... I'm new to this, and a bit overwhelmed at this point.

Pete
 
Just in case. In plesk each virtual host has its own access log files. They resides in directory:

/home/httpd/vhosts/<domain.name>/statistics/logs/access_log

But be carefull in accessing to this file. Plesk moves the content of this file to access_log.processed when it encaunter a traffic. Also plesk rotate access_log.processed file in according with logrotation settings.
 
Back
Top