• 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.

Issue Log Browser: PHP Warning „Undefined array key ‘user’“ in ImapLoginProcessor.php

voelu28

New Pleskian
Server operating system version
Ubuntu 20.04.6 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.74 Update 3
Hello,
after re-enabling the Log Browser extension, my Plesk server is constantly logging the following warning in /var/log/plesk/panel.log:
PHP Warning: Undefined array key "user"; File: /opt/psa/admin/plib/modules/log-browser/library/Injest/ImapLoginProcessor.php, Line: 26
The warning is generated continuously by a sw-engine async task and causes heavy log spam.

I already applied the known workaround in panel.ini:
[ext-log-browser]
mailQueue.customerAccess = false

and restarted sw-engine and sw-cp-server, but the warning still appears.
This seems to be related to IMAP login parsing, not the mail queue itself.
Has this issue already been identified as a bug in the Log Browser extension, or is there an additional setting to disable IMAP login processing?
Log Browser extension: latest available via CLI reinstall

Thanks in advance.
 
Hello, @voelu28 . There's no such bug registered (at least, as far as I am aware). Could you please confirm whether you are using Dovecot or Courier? Thank you in advance.
 
Thank for the confirmation. I am unable to replicate the behavior on a test environment in order to open a bug report, but I inquired with our team for more details on what might be causing the warning. I will follow-up with more details as soon as possible.
 
Back
Top