Search results

@Kaspar@Plesk ISSUE REOCCURS on updated servers. Updates are from Plesk Obsidian 18.0.61.x to Plesk Obsidian 18.0.61.5 Can this issue be resolved before the next MU? Kind regards....

@Kaspar@Plesk Improving the WAF is not really the question here. In essence, it has more to do with REINSTATING functionality that has been present before. For instance, the excellent (free and paid-for) Atomicorp rulesets should be supported - it does not work like a charm like it used to...

@LTUser I am not sure what exactly happens, but I think that the clue is presented in the message : Checking for nginx ULIMIT value Nginx is rather versatile, works like a charm out-of-the-box and one should - normally - not run into any issue when using Plesk installers. However, some...

@Kaspar@Plesk It would be keep the OWASP ruleset updated on a more frequent basis. In a not so far away past, Plesk did continue to use (old) rulesets that were vulnerable, even though security patches were released already. In addition, Plesk Team could consider to mitigate too strict...

@Kaspar@Plesk The question can be answered with a definite "no". Although the reported bug is very likely to be associated with one of the CLI utilities underlying - the Webserver Configurations Troubleshooter - the Plesk CLI Repair Utility the reported bug seems to be only manifesting...

@Kaspar@Plesk It really is not. The workaround solution only fits the bill, because it causes Nginx config templates to be regenerated. However, the reported bug is related to the inability of Plesk config generators to take into account custom Nginx templates. That inability has been...

@Kaspar@Plesk To be precise, the bug reported is not the same as the bug with ID PPPM-14442. Nevertheless, a bug fix can tackle both problems. The bug with ID PPPM-14442 is a mix of various issues related to http/3 support by Plesk and/or Nginx and the various (root) causes of these issues...

@Plesk Team, In addition, it has to be duly noted that the Webserver Configurations Troubleshooter extension does not work properly. A run of the Webserver Configuration Checker - surprisingly - results in : Checking Plesk version Installed Plesk version/build: 18.0.61 Ubuntu 20.04...

Username: TITLE ISSUE - Nginx config generation failure and http2 directive implementation failure PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Tested on : Product version: Plesk Obsidian 18.0.61.4 OS version: Ubuntu 20.04 x86_64 Build date: 2024/05/28 05:00...

@mow, It is a trade-off. The trade-off between "quick fix and preventing costs as a result of issues or bugs" or "being confronted with costs, while waiting until issues or bugs are fixed". I do agree that Plesk customers should not be confronted with that trade-off ...... it is essentially...

@HHawk, I am addressing you and all other people interested in the topic. Everybody can decide for themselves whether they can "read" my posts, find the text "readable" (or not). Everybody can have their own opinion, come to their own conclusions. You conclude - apparently - that my post...

@HHawk It must have been clear that I mention some hosting providers in my signature - there is not enough space to mention all hosting providers that I have actively tested with Plesk instances. Server4You is not my company, it is a hosting provider, so no need to answer the question "how...

@HHawk There are other more important issues with Plesk Migrator - some of them have been solved, others still have to be solved. However, one cannot come to any general conclusion when only focusing on one particular issue that has not been solved. In essence, Plesk Migrator works fine...

@AYamshanov To be honest, the UserVoice request might be a good idea, but one of the previous suggestions - secure MySQL connections - took a very long time, even though it was requested by many other users. In addition, some suggestions I prefer to associate with the issue or bug that is...

@Peter Debik The German banks increases prices as a result of increased complexity of regulations and financial law, augmented with increased required levels of liquidity and solvability, augmented with a "shareholder first" attitude of management (that often has stock options ..... and hence...

@HHawk I just saw your post as a notification in my email box. I can only be honest in response to your (and other) posts in this thread. Naturally, most people recognize the matter at hand and/or recognize the issues that you might encounter. However, that does not mean that everything...

@AYamshanov Could you be so kind as to develop a simple "button" in Tools & Settings > Server-wide mail settings that allows to activate drWeb (or other antivirus) for ALL mailboxes present on the server? After all, at this moment, drWeb is not activated by default for a newly created...

@Bitpalast Well, yes, as from your presence on the forum, it could already be concluded that you spent 250 hours per week on work :cool: Moreover, I can personally understand your choice - it is good to do something for the community and it is easy to get absorbed by the work for the...

@mjehlenz As stated before, the workaround does not always work - it is random behavior on the (server-)side of DrWeb. I have experienced that the workaround did work, then it didn't, then it did with other settings and ....... it almost seems like a pattern, but it is not. The best thing...

@Bitpalast Strange to change the handle :-D No, it has nothing to do with firewall settings and/or it is not even a Plesk bug : it is random behavior on the DrWeb side. The workaround is - as admitted before - very dirty. In essence, the dirty nature of this workaround is given by the...