• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Log Display Issues

themew

Regular Pleskian
Issue 1: Site using NGINX only and SOURCE reports in the log on the current date as nginx SSL/TLS access, but when the date changes to tomorrow, the source changes the log entry to Apache SSL/TLS access on the exact same log entry. Scrolling up through the log displays all entries as Apache SSL/TLS access when it originally displayed nginx SSL/TLS access,

Issue 2: Log entries are always displayed twice (same issue when it occurred in Onyx Resolved - Logs with double entries )

Product: Plesk Obsidian 18.0.31 Update #1
OS: CentOS 8.2.2004

Not sure if this is an isolated issue or if not, has already been reported to the devs.
 
@themew Remember that problem back in Onyx very well ;)
So FWIW had a quick re-check of our current setup to see, if we had the same problem again (Issue 2) and/or the new problem that you've identified (Issue 1)
On any hosted domain, that uses nginx only / Apache is not actve, yes, we have exactly the same 'wrong label' error (Issue 1)
On all domains regatdless of nginx / Apache setup however, we do not have any reoccurence of (Issue 2)
(Issue 1)
appears to just be a small coding glitch i.e. it's incorrectly re-labeling part of all of the log entries, but the actual content, is still correct.
 
@themew Remember that problem back in Onyx very well ;)
So FWIW had a quick re-check of our current setup to see, if we had the same problem again (Issue 2) and/or the new problem that you've identified (Issue 1)
On any hosted domain, that uses nginx only / Apache is not actve, yes, we have exactly the same 'wrong label' error (Issue 1)
On all domains regatdless of nginx / Apache setup however, we do not have any reoccurence of (Issue 2)
(Issue 1)
appears to just be a small coding glitch i.e. it's incorrectly re-labeling part of all of the log entries, but the actual content, is still correct.

@learning_curve Thanks for your reply. Are you using CentOS or Ubuntu on your servers where you're not seeing the double log entries?
 
Ubuntu 18.04.5 LTS now, but soon to be Ubuntu 20.04.1 LTS. We switched over from CentOS to Ubuntu back in the Plesk Onyx days.
We recently tested a server using Plesk with Ubuntu 20.04 and didn't see the duplicate entry issue in the log. Wondering if this is error is OS specific...
 
Back
Top