@mahmut ozdemir
It is very likely that there is a Cloudflare related issue.
However, a "web server" is something different than a "repo server" - you are trying to reach a "mirror", a repo server containing data to download.
MariaDB mirrors (with the exception of one that you should not be...
It is a hassle, but some people do it : they create a separate subdomain mail.domain.tld via Plesk GUI.
But if you do not have such a subdomain, which setup do you use? Plesk DNS? TLSA? etc etc.
In addition, do you have issues with webmail certs not renewing / not being assigned (when other...
@Hangover2
It is good to read that you have taken the effort to write down this part
since that essentially provides a good explanation (in rough outlines) of which kind of legal issue might be present.
Nevertheless, there is a notable difference between a legal issue and a legal case...
@Kaspar,
This "mail.domain.tld" setting does not work properly.
There - essentially - is a serious bug, related to "lack of development logic".
With the current "development logic", the setting works as intended, but not as expected.
Stated differently, the current "development logic"...
@Longi,
There is a general answer to the "521 error question", being that something is wrong on the Cloudflare side.
That is the central assumption that one has to use when being confronted with a 521 error from Cloudflare.
In this case (and most other cases), one can simply check the...
@Barend,
It is - also - a bit messy from the legal perspective.
In the EU, the relevant authorities are highly institutionalized and to some extent bureaucratic.
Stated differently, notifications and complaints get stuck in a queue of processes and end up as a file on a desk or even in the...
@Bitpalast
I fully agree with
but I would like to hint - with all due respect - that the other parts of your post are related to something that we should not give into : polarization.
This whole topic thread has become - more and more - a battle between two camps that cannot convince each...
@HHawk (and @manni),
Seeing this
I must ask : you are both aware of the fact that one can work around the one-server-one-plesk-license model?
In a rather simplified explanation : just loop a number of servers together, use one server for Nginx (as a proxy), use one server for databases and...
@HHawk
There is no irony in this quote
since you are absolutely right.
In addition, parties wanting to enter the market (as investor or new business) get invested in (by investors) to speed up the process that will or should result in the new party being able to compete with existing...
@HHawk,
Some of this is correct, some is not.
There will not be "risk" that exceeds the current level of "risk" - WebPros, Plesk, they are not more exploited than other tech businesses.
Tech industry is always supposed to be that unicorn and people (and investors) really believe that...
@manni,
This
is not a "new direction" - it is not new.
Most license providers - back in the old days - were forced to be "big" : the traditional humbug of "silver", "gold" and "platinum" (or whatever label was attached) plans, with a (false) signal that "the more VIP a provider is, the...
@fliegerhermi
Most things are not strange - strange things are often the result of the wrong questions being answered or the right questions being incorrectly answered.
For instance, it can be the case that your FTP user has not been setup properly and/or that the remote backup directory has...
@chris-design
The updates come from the domain update.geo.drweb.com that has many IPs and most of them are associated with network issues (read: delays).
One IP is performing significantly better, so you can try to solve your issue by adding
85.10.234.30 update.geo.drweb.com
to your...
@Sebahat.hadzhi
This
requires and/or has to satisfy (at least) three conditions :
1 - existing plugin or theme update managers, if installed as a WordPress plugin, should be "worked around" in the sense that they should not interfere,
2 - support for zip file upload and/or zip file...