Skip to content

Francisco Panis Kaseker

My feedback

6 results found

  1. 76 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)
    Francisco Panis Kaseker supported this idea  · 
    An error occurred while saving the comment
    Francisco Panis Kaseker commented  · 

    +1

  2. 591 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)
    Francisco Panis Kaseker supported this idea  · 
  3. 634 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…

    Francisco Panis Kaseker supported this idea  · 
  4. 52 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)

    At the moment you can change default vhosts location in Plesk using the command-line utility transvhosts.pl
    Just check available options with

    plesk bin transvhosts.pl —help

    Changing vhosts directory location for part of domains is impossible now.

    Anyway thank you for your input. We will consider this functionality in upcoming releases, if it will be popular.

    Everyone, please continue voting for this feature if you consider it important.

    IG

    An error occurred while saving the comment
    Francisco Panis Kaseker commented  · 

    Already asked this so many times... basically if you have 500 sites, you can not use plesk. you can not share 500 domains in the same ssd nvme drive. any iO peak will put your server down. ridiculous. And besides that the storage limit problem. Plesk support seems not be aware about those risks.

    An error occurred while saving the comment
    Francisco Panis Kaseker commented  · 

    Sorry, but this is critical. In cloud solutions you can manage the disk size, but baremetals have restrictions. cpanel fofer /home, /home2, /home3 etc solution. I know I can manually bind certain directories to other storages, but non sysadmin users can not move certain vhosts to another storage without know command line stuffs. and even cloud has restriction per volume, so sometimes you need to add more volumes.

    An error occurred while saving the comment
    Francisco Panis Kaseker commented  · 

    this is a very important feature. it will helps to scale the bare metal server and at the same time we can provide low storage performance to certain customers and high storage performance for premium users.

  5. 9 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
    Francisco Panis Kaseker commented  · 

    +1

  6. 58 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)
    open discussion  ·  IgorG responded

    Thanks for your feature request. We will definitely consider the possibility of its implementation if it receives a significant number of votes and is in demand.

    IG

    An error occurred while saving the comment
    Francisco Panis Kaseker commented  · 

    Crowdsec using iptables is not complete for most of servers. Is very common to use cloudflare and other third proxy servers to protect the sites. For those kind of servers, we need crowdsec nginx and apache bouncers.

    An error occurred while saving the comment
    Francisco Panis Kaseker commented  · 

    +1. crowdsec is very efficient to block non false-positives bad networks and is free! we already can setup the firewall bouncer in plesk, however will be much better to have nginx implemented, because most of the people use services like cloudflare, so crowdsec nginx bouncer needs to see the real ip.

    Francisco Panis Kaseker supported this idea  · 

Feedback and Knowledge Base