Search results

@Fede Marsell The words "might" and the condition "IF AND ONLY IF TRUE" should be read in the way they are intended : it is sarcasm. It is almost impossible that the message posted by @Ekaterina Babenko is "true", in the sense of "being adequate". In addition, whether or not data is...

@VNick, I believe that we - in a far away past - did a similar thing in order to facilitate dbase upgrades. If and when I have some time, I will have a look at the old development files and try to find the solution that we implemented back then. It worked like a charm, so it cannot do harm...

@Ekaterina Babenko There might be some persons reading your message as a relief that data leaks are not present and/or cannot occur and/or are minimized. The strange thing is that you suggest that "specific data" is not used and also not uploaded. The above implies, if and only if TRUE...

@/dev/null I firmly belief that a distinction should be made between a "good push" and a "bad push" - to stay in your terminology. Some things we really cannot object to. Nevertheless, Plesk has the history of adding "things" (of all sorts, being either extensions, components, upgrades...

@Sebahat.hadzhi and @AlL, It seems to be the case that, in addition to the odd error notifications, there are some connectivity issues. I can refer to the following link where I have add some information and some STR that can help to minimize the connectivity issues. Kind regards....

@Sebahat.hadzhi and @Peter, It seems to be the case that, in addition to the odd error notifications, there are some connectivity issues. The connectivity issues are NOT the root cause of the problem of the error notifications. Nevertheless, there is the need to get this "connectivity issue"...

@Sebahat.hadzhi It is not a license issue, unless Plesk did issue problematic licenses themselves. The simple proof that it is not a license issue is already present in 2 ways : (a) you cannot replicate it and (b) all manual updates work fine. Again, it should be wise to focus on the...

My educated guess would be that Plesk has a business model, associated with the (paid for) extension. At least in theory, the combination of "feedback" of all Plesk servers with respect to bad files and bad IPs would allow for the development of a better solution. It is just a different way...

@Fede Marsell The statement is not really accurate. I can safely assume that Plesk is looking into the matter, before making any (bold or implicit/explicit) statements. If that assumption can be proven to be incorrect, then there is a case of "negligence". The legal aspects of this...

@VNick, The Performance Booster extension is a bit poor in the area of db optimization (and optimization in general). The idea is indeed interesting and might need some (serious) tweaking in order to be able to function as an efficient db optimization tool. However, it might be possible...

@Bitpalast I fully agree, that is why I suggested the Nginx route. The iptables route is better and the hosts.deny should be even more better. Nevertheless, the iptables route can be quite cumbersome and dangerous to some extent, if the DROP list changes and requires some iptables...

@VNick, That sounds excellent. This also implies that Plesk has a "conversion template" containing "old-to-new-variable conversions" and "remove-deprecated-variable conversions". Are those "templates" included in the packages? The latter question might not seem really relevant, but it is...

@Sebahat.hadzhi I think that @Fede Marsell is addressing an issue that should indeed be called a "data leak" in a legal sense. There is no legal ground for sharing data / uploading data by an extension, if that extension has not been installed explicitly and (legal) conditions have not been...

@Sebahat.hadzhi Output of systemctl status drwebd will not result in abnormalities - at least, it should not be the case. It is clearly a bug of some kind that is not related to connectivity issues and/or license issues - after all, manual updates should not work if that was the case...

@AbramS, I have just noticed this script, which seems to be sufficient in many ways. Nevertheless, it is more convenient to load the DROP list into a custom Nginx conf with the format deny [ IP1 ]; deny [ IP2 ]; ... deny [ IPn ]; and refresh the Nginx conf on a frequent basis, preferably...

@Sebahat.hadzhi I am asking in reference to the MariaDB Upgrade tool. There is no specific set of custom config files that I am referring to, since it is a general question. However, I can state the following. In many test scenario's, I use two types of customizations : 1 - inline...

@Sebahat.hadzhi I am aware of the fact that one has to - forcefully - remove some files. However, my main concern was (read: back in the days that I tested the Imunify extension) that the firewall rules were "removed" in a very unpredictable way : in some cases, all entries were deleted...

@Sebahat.hadzhi It is probably difficult or even impossible to replicate a specific symptom. In essence, there are multiple "symptoms" which are very likely to be caused by ONE root cause of the problem. In addition, the "symptoms" are not consistent over time - in a test environment, I...

@Sebahat.hadzhi Are there known issues for upgrades of installations with custom config? How are they dealt with in the process? Are backups of (custom) config files made? I am curious ......... Kind regards....

@Sebahat.hadzhi Problem here is that Plesk addresses one problem, being the "unwanted" installation of Imunify. Nevertheless, this "issue" (or bug) has been present for a longer time period - removing Imunify extensions has (always) been a (tiny) bit problematic. In addition, Imunify...