• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Log viewer for domain log files tries to parse encrypted files which results to display error

Status
Not open for further replies.

GwenDragon

Basic Pleskian
Server operating system version
Debian 11.5
Plesk version and microupdate number
18.0.48
The protocol view of log files results in display of broken lines if log files are encrypted by GnuPG.
The encryption is needed for the domain owners log files and done by a logrotate (config compresscmd!) every day for 1 week. This generates compressed files like error_log.1.gpg … error_log.7.gpg.

When domain owner wants to see logs of the domain, the protocol viewer tries to parse f.ex. error_log.1.gpg and display garbage.
That is a bug.
The protocol viewer should exclude some file formats it is not able to parse.

Screenshot 2022-11-22 121611.png
 
Status
Not open for further replies.
Back
Top