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 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.
A new version of the Log Browser extension has been released, it is a bug-fix release.
1.8.2 (04 July 2024)
[+] Added support for Ubuntu 24.04.
[-] A corresponding message now appears when trying to resend several email messages with none selected. (EXTPLESK-5609)
[-] The "Processing..." status is now displayed for emails being delivered instead of the [MailQueueList.Filter.Status.null] locale key. (EXTPLESK-5612)
[-] Delivered messages now include tooltips explaining why they cannot be removed from the queue. (EXTPLESK-5615)
[-] Log can now be retrieved correctly on Plesk servers running on Ubuntu 24.04 or other Linux distributions that have systemd version v254 or later. (EXTPLESK-5616)
[-] The "Exception: PHP Deprecated Construction: strpos()" error is no longer logged by mistake. (EXTPLESK-5617)
[-] Fixed the issue where certain mail log entries could stop further processing of the log file, resulting in the "Exception: PHP Warning: Uninitialized string offset 0" error. (EXTPLESK-5642)
[-] Log Browser no longer produces unnecessary and misleading "Execution postqueue has failed with exit code 127" errors on Plesk servers without Postfix. (EXTPLESK-5643)
[-] Emails with the "Expired" status are now handled properly. (EXTPLESK-5644)
[-] Servers without mail logs are now correctly ignored. (EXTPLESK-5645)
If I understood the question correctly, it is about showing events saved in the Action Log table to the end-customers. Currently, it is possible to hide/disable the feature, the end-customer will not see the tool in the interface, it can be done by adding the following lines to the panel.ini file:
If you want to continue showing events to end-customers and at the same time filter out events performed by Admin, it is not possible. The idea of the tool is to show end-customers what is happening with their subscription transparently. In this case, logging will be continued but on available only for Admins.
If I understand the question wrong, could you please provide more detail about the idea and scenarios?
A new version of the Log Browser extension has been released, it contain a new feature and a few bug-fixes,
1.9.0 (5 August 2024)
[+] Re-worked the "Mail Queue" menu to make it easier to track the status of messages and identify and resolve issues.
To enable this feature, add the following lines to the panel.ini file:
[ext-log-browser]
mailQueue.serverWide = true
Added a tooltip to the domain-level "Track Email Delivery" pages explaining why it is not possible to resend or remove sent, rejected, and bounced emails.
Added a tooltip to the domain-level "Track Email Delivery" pages advising to select one or more deferred emails when attempting to click Resend with no deferred emails selected.
[-] Customers can no longer see names of other customers in the filter. (EXTPLESK-5654)
[-] The header of the last server reboot notification is now correctly displayed in Tools & Settings > Notifications (under "Plesk"). (EXTPLESK-5685)
[-] Fixed the issue where the Log Browser extension got stuck trying to process logs with an excessively large number of entries. (EXTPLESK-5686)
To customize for what period data should be processed, add the following lines to the panel.ini file:
[ext-log-browser]
mailQueue.firstEntryOffset = 2678400 ; in seconds
[-] Fixed the issue where certain mail log entries could stop further processing of the log file, resulting in the "Exception: PHP Warning: Uninitialized string offset 0" error. (EXTPLESK-5700)