• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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