Search results

@PeopleInside and @GerdSchrewe Gentlemen! In a sense, you are both right. The problem here is that there might be workarounds for a solution that does not exist ...... and "setting cronjobs at different times", "waiting for new updates", "ignoring error messages from Plesk package manager"...

@fliegerhemi, If you do not have the 534 error, then do not worry. However, please check carefully when you do reconnect. If the 534 error is present, then you might need to force FTP connections over IPv4 - otherwise, you will get authentication failures that can cause major issues. Kind...

@Sebahat.hadzhi Let's have a go then! Update : I am sorry, not possible, no microphones (or other things required) present here ;-) Kind regards...

@AYamshanov and @Sebahat.hadzhi The intentional change is quite understandable - there is no reason to show the entire hash of a password, which hash is one of the things truncated. However, it comes to mind that ..... if this change was intentional ....... why is the prefix $2y$12$...

@JeroenK, No thanks needed. By the way, Nginx default config provided with Plesk is - in theory - sufficient in most use-case scenario's. That does not necessarily imply that huge improvements can be made with custom Nginx config. In practice, it is not at all sufficient to use the...

@PeopleInside The workaround suggested by Plesk can work for many reasons, but it still is a workaround that can other issues - for instance, an issue might be and probably is that you are updating packages during rush hours, hence leaving the server less responsive and the web server even...

@PeopleInside In most cases, these kind of "pum related" issues go away after 1 or a couple of days. As a result, in most cases, it is safe to ignore the error notifications - not desirable, not truely safe, but ignoring them is sufficient. Setting the cronjob at 14PM - or any time at...

@fliegerhemi, The error message can - in theory - be safely ignored. However, this "150 Opening BINARY mode data connection" is normally indicative of a firewall blocking the passive ports used for FTPS (or, in some rare cases, issues with the range of predefined passive ports). If you...

@JeroenK, Please remove the host : $host custom value set in 'Additional nginx directives'. This custom value should not be needed at all. For Nginx, this is - in this precedence : a hostname from the request line, a hostname from the Host request header or the server name matching a...

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