• 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.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • 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.

Issue When will the latest Update #3 be fixed?

DieterWerner

Regular Pleskian
The latest update contains a lot of errors.
Repair installation -y ends with Errors
Permissions of plesk packages are changed (repair can't change that back)
Fail2Ban has problems to display the blocked ips of a jail
Admin logout leads into an error message
(will be continued)
 
At the risk of making you even more angry than you already are... :D
We ran that upgrade yesterday and... We have no errors, no faults and no problems at all - with anything (so far ) - after the upgrade...
Setup differences perhaps?
 
In our case it seems to be related to the presence of the "Dropbox Plugin", which obviously makes HTTP calls to Dropbox's servers. And the libraries to do that (Guzzle HTTP) seems to be missing. Furthermore it looks like basically any change done in Plesk triggers the initialization/loading of this plugin, and as a result of that triggers a PHP Fatal Error which halts further processing of the request
 
It looks like if you don't have the dropbox backup extension enabled, there isn't an error during or after upgrade.
 
We're on CentOS 7, no errors on 18.0.38 Update #3, besides some UX/UI changes that we had to update. No dropbox extension.
 
The latest update contains a lot of errors.
Repair installation -y ends with Errors
Permissions of plesk packages are changed (repair can't change that back)
Fail2Ban has problems to display the blocked ips of a jail
Admin logout leads into an error message
(will be continued)

That has been displayed even after 'repair all -y'
Type PleskUtilException
Message f2bmng failed: ERROR:__main__:Failed to get packages by files: package manager returned 5 lines instead of expected 3. Command was ['/bin/rpm', '-qf', '--queryformat', '%{NAME}\\n', '/etc/fail2ban/jail.conf', '/etc/fail2ban/jail.d/plesk.conf', '/etc/fail2ban/jail.local'] and returned exit status 1. Your package system might be inconsistent. Please check it for issues with 'plesk sbin pum --check --full'.
File Agent.php
Line 196
 
That has been displayed even after 'repair all -y'
Type PleskUtilException
Message f2bmng failed: ERROR:__main__:Failed to get packages by files: package manager returned 5 lines instead of expected 3. Command was ['/bin/rpm', '-qf', '--queryformat', '%{NAME}\\n', '/etc/fail2ban/jail.conf', '/etc/fail2ban/jail.d/plesk.conf', '/etc/fail2ban/jail.local'] and returned exit status 1. Your package system might be inconsistent. Please check it for issues with 'plesk sbin pum --check --full'.
File Agent.php
Line 196

Could it be that you have an active Epel repository? That could lead to unexpected results as plesk installs updates from Epel repository in stead of the Plesk and/or OS repositories.
 
The latest update contains a lot of errors.
Repair installation -y ends with Errors
Permissions of plesk packages are changed (repair can't change that back)
Fail2Ban has problems to display the blocked ips of a jail
Admin logout leads into an error message
(will be continued)
Very nice - after a restore of the Backup 03.10.21, everything works fine again.
 
Back
Top