Filip Filip
My feedback
12 results found
-
125 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.—
IG -
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
-
410 votes
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
-
405 votesFilip Filip 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…
Filip Filip supported this idea · -
127 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.
—
IGFilip Filip supported this idea · -
140 votes
Thank you for your input! We will consider these nginx configuration suggestions in upcoming releases if it will be popular.
Everyone, please continue voting for this feature and add your comments if you consider it important.
—
IGFilip Filip supported this idea · -
294 votes
The previous status was set by mistake.
Due to the changes in MongoDB’s licensing we are no longer able to consider this as a potential feature to be added to our product.
Please continue to vote if you would like to use CouchDB in Plesk.
—
AAFilip Filip supported this idea · -
29 votesFilip Filip supported this idea ·
-
467 votesFilip Filip 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
Filip Filip supported this idea · -
236 votes
Current scope for Plesk Onyx is to enable an ability to serve all http(s) requests by Nginx only.
Note: apache will still be installed. Switching of apache to optional component is subject for the next release.
Update:
The ability to turn off Apache and have content served by nginx only on a per-website basis is now available in the latest Plesk Onyx 17.0.14 preview. We encourage you to check the implementation and let us know what you think. Please visit the following forum thread to learn how to access the preview: https://talk.plesk.com/threads/plesk-onyx-preview-and-feedback.337172
How to try this feature:
Go to any website, click Apache & nginx Settings and deselect the “Proxy mode” checkbox under nginx settings. The feature is also available in Service Plans.
We would appreciate hearing your feedback on implementation of this functionality. Thanks in advance!
—AK
Filip Filip supported this idea ·