Search results

@Raudpats The best question here is to ask what you have changed in the apache config. Did you uncomment (or change) the Mutex entry in apache config? If yes, than that could be or is the likely culprit - you can test this by simply commenting out the Mutex entries : if that works, your...

@David Borrink I think that you should explicitly set the remote storage settings for the "mail domain" under Websites and Domains > Backup and Restore > Settings. Please create a specific (sub-)directory on Dropbox first and use that (sub-)directory in the remote storage settings...

@Manuel Garcia It is correct that, as stated by @Sebahat.hadzhi, Postfix is bouncing messages by default to the original sender - that is, Postfix will at least try. The config line bounce_notice_recipient = postmaster will allow bounce messages to be sent to the postmaster, in addition...

@Fede Marsell Wrong conclusion, I have more interest in this matter than most people. In fact, I have asked a legal team to investigate the matter and to determine the competent court. As opposed to talking about this topic, I am investing serious money to determine which kind of actions...

Excellent, thank you. I will do a test migration soon with the solution of @Kaspar and, if necessary, provide you with some feedback ... Kind regards...

@Hangover2, @Fede Marsell and @AlL, As mentioned in another post, quoted briefly as "[ ... ] The best way is to convince Plesk that Imunify is - factually - determining what is "suspicious". This is also the main problem here : Imunify is that kind of extension that flags (almost)...

@brother4 It is pretty safe to conclude that it is related to the fact that you are on a virtualized host, but I am not sure whether that makes things impossible. I think that you should try "updating" from SSH command line, as opposed to the other methods of updating. Just open two SSH...

@Sebahat.hadzhi If the workaround from @Kaspar is valid, then I do not see why the ETA should be in August. Could you be so kind as to speed up the process and implementation of the update? Kind regards....

@TorbHo and @Kaspar @Kaspar, thanks for the quick testing and suggestion for the workaround! @TorbHo, can you keep everybody posted about your experience with the workaround? It should be working like charm, since that is to be expected - nevertheless, an update from you is always welcome...

@TorbHo Please note that messages with valid DKIM signatures are - often (but not always) - also rejected by GMX and web.de. They are notorious when it comes to bad mail server configuration and also when it comes to bad mail reputation - spammers like it. So, do not worry about those...

@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...