Skip to content

Christoph Flathmann

My feedback

4 results found

  1. 407 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    This is a valid request, so we’ll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features.

    The original request contains a manual solution, so, we consider to automate it. Please, add a comment if your case will not be solved with that solution.

    Thanks in advance!

    — rk

    Christoph Flathmann supported this idea  · 
  2. 615 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Repeatedly we're seeing questions on when http/3 will be implemented. http/3 is available in the experimental branch of Nginx, called "main line". This is not a branch that is "stable". Plesk only offers stable software versions for the utmost reliability you can get as reliability is much more important than speed. A fast website is of no use if its webserver crashes or the protocol doesn't work as expected in all cases. Plesk does not offer experimental features. The stable version of Nginx that supports http/3 is expected to become available in April 2024. This is when it makes sense for Plesk to also offer http/3.

    From articles that foster the hype about http/3, it sounds as if it can increase a website's speed incredibly much. On average, on real website tests by several reknown sources, the acceleration has been seen at around 0.2 to 0.3 s/page, typically around 12…

    Christoph Flathmann supported this idea  · 
  3. 224 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Christoph Flathmann supported this idea  · 
  4. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Christoph Flathmann commented  · 

    Basically the scenario I thought of would be:

    Superzones:
    - example.org
    - yourfancydomain.com

    Whitelist:
    - yourfancydomain.org

    So a customer will get a subdomain on yourfancydomain.org
    - customer1.yourfancydomain.org
    - customer2.yourfancydomain.org

    And allow them now to add maybe a subdomain to their domains.

    But don't allow customer1 to create a subdomain on customer2's domain

    So we can provide our customers with a free domain.

    Christoph Flathmann shared this idea  · 

Feedback and Knowledge Base