Reinhard Hutter
My feedback
5 results found
-
192 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.
—
ETReinhard Hutter supported this idea · -
107 votesReinhard Hutter supported this idea ·
-
829 votes
Would you mind to try Nginx caching in Plesk Onyx 17.8 Preview?
This would be very helpful to get your experienced feedback here http://www.surveygizmo.com/s3/4165754/Plesk-17-8-Preview
Reinhard Hutter 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
Reinhard Hutter 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.
—
IGReinhard Hutter supported this idea ·An error occurred while saving the comment
Plesk 12 comes with a default
location / {
...
}
directive in the nginx config file. This is really bad because very many prominent PHP applications and frameworks (e.g. Symonfy 2) ship with setup instructions containing a
location / { ... }
directive themself, leading to "duplicate location" errors when adding those directives in "Additional nginx directives"