Search results

@HHawk The statement can be responded to with a : no, they will definitely not. I am simply trying to say here that some things or views will never change within Plesk or will only change with very very great difficulty. And the definition of "difficulty" here is : it takes years to...

@Sebahat.hadzhi Please elaborate on the "prototype" and how this differs from the current security components. Thanks in advance!

@Sebahat.hadzhi I have to be brutally honest. This is an accident going to happen and a reoccurrence of similar attempts from the past - attempts that failed miserably. On the hand, there is the concept of WebPros Cloud. In essence, this concept is already alive in the form of many...

@LTUser, I agree with your statement concerning the "fees" of vital components that - ideally - should be present at no costs at all. There are better and cheaper alternatives, quite many. In addition, there is always the option to setup a free spamd cluster. Both the alternatives and...

@Gary W. I am a bit disappointed if you or Plesk Team removed your last posts - what happened there?!?? One of your posts talked about a "1400-word delirium" from my side - I do not take personal offense, no worries. The other of your posts showed an image and contained a statement about...

@Shamrock If this is the only objective (people visiting), then you do not need to think about NCSC or go to internet-dot-nl (vague site, by the way). If "visiting" is defined as "making your website accessible to modern browsers", then TLS 1.3 with a very strict cipher suite will always...

@TorbHo This statement I can fully agree with. This statement I feel ambivalent about. Most loyal customers should be defined as "customers that stay with Plesk". The "many users" that you talk about are "users" that - often - do not have a fair appreciation of the material and...

@JVG This statement needs to be clarified. In essence, the "full server backup" is a sequential process of making backups of various individual domains / subscriptions. Stated differently, all domains and subscriptions are sequentially backed up into a "full server backup". The backup...

@Shamrock Do not expect too much. It is rather impossible to make sense of what can be labelled as a "set of secure ciphers" - this differs across use-case scenario's and it changes over time. Manual adjustments will always be required, if any adjustment is necessary. Certainly not the...

@Gary W. This statement is rather lopsided - why not take 10 years ......... or 50 years? It might be true that you save some money, but taking a random and long period is just incorrect and some might argue that it is "exaggeration". The simple fact is that, if and only if one does a...

@AndreyKashin Now, after the preliminary introduction in my previous post, let's work towards to answers to your questions. This statement is a clear indication that your server has not sufficient resources. A tiny upgrade of the server would suffice, since any 32GB / 64 GB RAM server...

@AndreyKashin First of all, @ChristophRo has given you some valuable insights and the most important one is : use servers with sufficient resources. Secondly, this part is partly right and partly not entirely right. In fact, there is a bit of performance gain when using incremental...

@Shamrock The question is rhetorical in the sense that the alias will "point" to the "main domain" and, as such, the config of the main domain is equivalently applying to the alias. Could you be more elaborate about and describe what you think is "different" from the main domain? In...

In that case, not an issue with Plesk. Please provide more information.

@Shamrock, This question is probably best answered as : yes. However, you can make a backup of relevant config files first. If you have Nginx config, then copy the /etc/nginx/conf.d/ssl.conf to a file like [filename].bak - leave the ssl.conf file as is (and do not remove). Afterwards...

@Shamrock The Mozilla config generator is one of the kind "pick me (Mozilla), don't think and mess up your config with what I say - trust me!". In essence, most of the valuable recommendations made by the Mozilla config generator are already present in the default Plesk config. Some...

@Ricardo Capistran It is as @Kaspar has already stated : it is not unusual. Nevertheless, one should take notice of the context that applies. Let me explain. If and whenever using only Fail2Ban, a count of 3000 banned IPs is certainly not abnormal, not at all! In fact, Fail2Ban...

@TorbHo This statement is absolutely true, but it is not something of "lately". In fact, this is a natural tendency for years now : Plesk evolving with many (many) hickups that require bug fixes that require patches. To some extent, this "tendency" is the result of the desire or even the...

@mow, I have tried that (for all IPs associated with DrWeb) and only makes a very very very very small difference ...... and only for the 85.10.234.30 IP. In theory and in practice, it helps ........ the advantage is quite small. You can check this by sending a ping to the DrWeb update...

@Tjerk Visser They did not, all update server - with the exception of one - are still very slow, to the extent that they become unreachable. The best thing to do is still forcing the IP 85.10.234.30 for updates. Kind regards...