Anonymous
My feedback
56 results found
-
5 votes
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.—
IGAnonymous supported this idea · -
237 votes
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.
— AY
An error occurred while saving the comment Anonymous supported this idea · -
1,263 votesAnonymous supported this idea ·
-
531 votesAnonymous supported this idea ·
-
467 votesAnonymous supported this idea ·
-
448 votes
Thank you for your input. We will definitely look into integrating DynDNS in our future releases
Anonymous supported this idea · -
442 votesAnonymous supported this idea ·
-
426 votes
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.
— AY
Anonymous supported this idea · -
625 votes
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…
Anonymous supported this idea · -
405 votesAnonymous supported this idea ·
-
404 votes
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.
— AY
Anonymous supported this idea · -
357 votes
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.— SU
Anonymous supported this idea · -
391 votes
As UserVoice staff cleaned up the most of twisted voices, I’ve returning this suggestion to open discussion.
Everyone, please continue voting for this feature if you consider it important.
—IB
Anonymous supported this idea · -
276 votes
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.
— IB
Anonymous supported this idea · -
376 votes
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.
— AY
Anonymous supported this idea · -
243 votesAnonymous supported this idea ·
-
286 votes
We have an article with an instruction how to set up django on Plesk server https://www.plesk.com/blog/product-technology/plesk-and-django
So, now we would like to get a feedback what is the most critical things you need to manage with Plesk regarding django.Anonymous supported this idea · -
228 votes
Thank you for your input. We will consider this functionality in upcoming releases. Note that Plesk supports multiple mail servers and if we are going to add this feature, it’s possible that it won’t be available for all supported mail servers at once
Anonymous supported this idea · -
220 votesAnonymous supported this idea ·
-
223 votesAnonymous supported this idea ·
create a custom file such as main.cf.custom and then add a command to plesk's scheduler for after update completed: cp custom.file /etc/postfix/main.cf