Search results

@netart.gr First of all, the code should not be added to a demo website in order to notice the effect of the code : add it to the production site. However, as a fan of Nginx, I would recommend to use Nginx as a proxy in order to keep some bots and bad traffic away - that is always better...

No, 18.0.49.2 .......... but Ubuntu based on this particular development server. Nevertheless, the size of the clean-reports file should not really matter, given the error notification that I have read. In essence, that error notification is a "humbug" PHP error notification with respect to...

@Alexander Yamshanov I strongly feel that this is a tutorial that is essentially well-intended, but not really suitable for daily practice. I can give you many reasons, but I will give you 2 major reasons : 1 - as long as Plesk does not support secure SQL connections, any unfortunate event...

@GwenDragon That is quite common : a user with a problem and during investigation, a whole array of issues seems to be present ...... a never ending array of issues. As opposed to solving each issue individually, a fresh install (of an extension or even Plesk itself) is often the best...

@Kaspar, Do permissions look like this? -rwxr-x--- 1 root psaadm 668 2023-01-10 17:19 clean-reports

@BNSHosting.net It is highly recommend to reinstall Postfix completely. I do not know whether you have tried to fiddle with the configuration or that your installation of Postfix has been messed up completely somehow. It does not look good, when having a look at the config files that you...

@Visnet and @Kaspar Can you check the presence of the file "clean-reports" by running the command : ll /usr/local/psa/libexec/modules/watchdog/cp/ There should be an executable with the name clean-reports. If not, then that is the problem. The root cause might be totally different : the...

@azzaka I am happy to see that you moved some or more Plesk instances to Azure - that is or might be a good solution, even though the cost is relatively high and major drawbacks are present in terms of performance and throughput (and potentially egress and ingress costs). Many years ago, I...

@custer The big question here is : WHY? Smart Updates or Smart PHP Updates as a premium extension to an existing extension, the WPT. I might be mistaken, but the WPT is free in Web Pro and Web Host editions and the WPT Deluxe is an additional 8.50 euro to 15.50 euro per month? A lot of...

@custer, Please make sure that the commercial jetpack plugin is - installed properly, with all prerequirements, - updated automatically, and allow WPT to check for the above by default. In my experience, the Jetpack plugin is troublesome in two ways : 1 - it installs a lot of code that...

@HHawk I have read your messages and do understand your "frustration" (for lack of a better word) to some extent. I certainly agree that there are many things to improve at Plesk and/or within Plesk and/or by Plesk and/or by Plesk Team. However, there is some degree of reality that we have...

@Monty, The thing here is that multiple parties tried to solve one issue, with all solutions being viewed from the specific perspective that each party had. It is not messy that a lot of parties suddenly find solutions, that is true. It is messy that one has to pick and choose between a...

@mow and @Monty, These quotes are right ........ but you are also aware of the fact that Plesk allows for custom templates. In the Plesk structure, these custom templates are used first ..... and then the default templates are used - that is a very rough outline of what happens. The...

@Monty I am not sure whether the Plesk update is required, if the Canonical patches are present. It is a big mess, with various work-arounds required to keep websites running ......... followed by various patches (bug fix solutions) that might not be compatible with applied work-arounds...

@mow It is good that you write it down like that - forum members can see the differences in the various approaches and decide what to do. I have tested all approaches mentioned and chose to apply the work-around of reverting to an old Apache version, based upon the idea that it should only be...

@Monty Thanks for the very valuable tip. And now it becomes interesting ;) The bug fix update to be released by Plesk Team ..... or the patch with the PPA package mentioned often in this thread (or uninstalling that PPA) ....... or the workaround presented in the first KB article (or the...

@IgorG A release of an update with a fix would be preferred. I am interested in what a "more straightforward solution" would be, since in any (pretty standard) Plesk instance, the current KB fix works like a charm. I have tested some other solutions, but it all boils down to required...

@IgorG, In essence, you are right - I did not think about that. Nevertheless, I do not think that it is smart for other people to put any package on hold, whatever reason there might be. However, from the perspective of Plesk, it does make sense to not add an automatic unhold. Kind...

@IgorG, Could you be so kind as to make sure that any formal Plesk fix will include an automatic apt-mark unhold apache2 command? By the way, excellent and quick response by Plesk Team and excellent KB article Website on Plesk server suddenly started to show 500 error: AH10292: Invalid proxy...

@AntonM@Parallels Thank you for the clean solution - that is, solution ("work-around") number 2. Solution number 1 ("Switch to FastCGi instead of PHP-FPM") is not really a viable option - it is a dirty work-around and will cause configuration related issues when working with Nginx, certainly...