Search results

@danami Is there any progress on that feature after 1 year passed by?

Fixed with the release of Advisor version 1.9.13-714: 1.9.13 (02 Jun 2023) [-] Running the "plesk ext advisor --advice-list" command no longer results in the "Undefined create_function" error. (EXTADVISOR-925)

A good new default recommendation could be "b.barracudacentral.org".

Hello @Peter Debik , we did follow a Plesk support article that is using exactly that command: Website statistics (Webalizer) does not show relevant data So the article should be updated or removed.

Username: TITLE Webstatmng command "/usr/local/psa/admin/sbin/webstatmng --set-configs --stat-prog=webalizer --domain-name=<domain_name>" is not working anymore PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.52 Update 2, Debian 10.13, x86-64 PROBLEM DESCRIPTION The...

Username: TITLE Advisor command "plesk ext advisor --advice-list" is not working anymore PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.52 Update 2, Debian 11.7, x86-64 PROBLEM DESCRIPTION The command "plesk ext advisor --advice-list" is not working anymore...

As the command "plesk ext advisor --advice-list" is broken in the latest Plesk release, does anyone know the name for blacklisting "ModSecurity & Fail2ban".

Also two years later in 2023 nothing has changed. The whole reseller management is neglected. The needed branding or special settings are missing in so many areas. The only work-around is to put only one reseller per server and then using the admin account to make the branding for the reseller...

Deleting the sources to avoid warnings about the missing public keys to verify the signatures is an interesting way of solving this issue :eek:. The better approach would be to install the key, if you are using Imunify360: wget -O RPM-GPG-KEY-CloudLinux...

For us an upgrade to 18.0.51.1 is no option yet because this version has serious bugs that we cannot burden onto our clients. All our live servers on version 18.0.49.2 lost monitoring out of nowhere. Whatever the reason is (external or extension) please fix it ASAP. Just telling the clients to...

At the moment the update policy of Plesk is getting more and more headache. Nearly with every new feature release 18.0.x new bugs on existing functionalities are introduced. In the past it was enough to wait for Update 2 or 3. But nowadays we have to skip even complete feature releases. Right...

We can only warn every Plesk user with high amounts of customers on their servers. Plesk 18.0.51 is a support nightmare concerning this bug. Even Plesk 18.0.51 Update 1 does not address it.

Nevertheless is there an ETA for this bug? It would be great to have a fix in "Plesk 18.0.51 Update 1" as right now this is a main blocker for any upgrade of live systems.

@Peter Debik You made my day. Our issue was caused by the problem you did describe.

We can confirm that as of March 22, 2023, the issue with Google nameservers on that domain still exists intermittently.

We are not sure if this is related to this bug but we have on top the following issue on our test servers where we did roll out this upgrade: - when trying to create a password protected directory + user the Plesk GUI could not finish the operations and we got timeouts plus the changes were not...

The switch did happen silently already for Plesk Obsidian 18.0.50. Thanks @TeamPlesk!

Hello, on some of our Plesk servers we have a strange behavior of the Plesk Backup Manager. If a subscription is bound to a chrooted shell or SSH access is even forbidden, a backup (e.g. only configuration) will create the .ssh directory in the subscription including SSH keys (id_rsa +...

@Peter Debik Thanks for your quick work around that did the job for us. In our case the problematic PHP handlers were still used in some service plans as default PHP handler.

We have the same issue also with PHP 7.4 on our servers with the latest Plesk version 18.0.49 Update #2.