Gabriel T
My feedback
41 results found
-
6 votes
-
106 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 -
38 votes
This feature has not gotten many votes during the past five years. Technically, a graceful restart of Apache is unnoticeable for the user as not service interruption occurs. Further, Apaches model loads all configuration data into memory upon start or reload. The Odin link provided in the comments does not lead to a more details explanation of the feature request. And finally, in the Nginx/Apache combination with an increasing number of users considering Nginx-only hosting a change in the Apache worker process won't be sufficient.
Please provide a sound explanation why a graceful restart of web servers is insufficient for adding or modifying web server configuration.
-- PD
-
184 votes
Thank you for your input! We are planning to implement this functionality in upcoming releases. The request is registered as: PPM-2517
Everyone, please continue voting for this feature if you consider it important.
— ES
-
235 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
An error occurred while saving the comment -
187 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.
—
ET -
53 votes
An error occurred while saving the comment Since I got really tired of exporting to csv and waiting for this to be planned I created a small extension for myself to give me an overview list of pending renewals.
Feel free to use it if you feel adventurous but it's only a rough draft at the moment and by no means production ready.
An error occurred while saving the comment As soon as I tried to do the same I noticed it too. If I recall correctly it was possible in PLESK 10 when I stopped using PLESK alltogether. Too bad I can't see it now in Onyx.
-
139 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.
—
IGAn error occurred while saving the comment The worst part about this issue is that you're also unable to use HTTP/2 with this bug because it relies on nginx with SSL. This is going to make plesk obsolete pretty soon. I wish this would be given priority within this year otherwise our company has decided to plan a migration to CPanel for next year.
An error occurred while saving the comment I've been thinking about this and there's another way to approach this solution too. Some special tags could be implemented so that when the final vhosts is completed some additional tasks are also executed like, MERGE/REPLACE/DELETE
For example
location / {PLESK_DELETE
try_files ...
} -> Delete all directives matching location / and then write current location directivelocation ~* \.*.(jpg|jpeg|png|gif|ico|css|js)$ {PLESK_MERGE
expires 14d;
} --> If location directive exists then append expires 14d to the location block; else write current location directivelocation / {PLESK_DELETE} --> remove directives matching location / before adding other directives.
Order of execution could be
1. PLESK_DELETE
2. PLESK_REPLACE
3. PLESK_MERGEAn error occurred while saving the comment I've noticed that In addition to this point there is also another problematic location directive .
location ~ /$ {
<?php echo $VAR->domain->physicalHosting->proxySettings['directoryIndex'] ?>
}can cause urls in the form of http://www.domain.com/path/ to yield 404 while http://www.domain.com/path is OK for CMS pages.
-
106 votes
-
274 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
-
460 votes
-
437 votes
-
87 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
An error occurred while saving the comment @Sergey sorry for the long delay to respond. I was caught up in work and didn't have time to catch up here. What I mentioned for SEO is just a simple use-case based on statistics reports I gathered online. To be honest I don't understand how you suggest to configure virtual directories in this case to bypass this SEO issue. It would very interesting to see an implementation example to overcome this situation.
I also understand this would be a long-term commitment to implement this because it does seem really hard to do. But I do think it would also be a great asset for PLESK and worth investing the time and effort.
-
123 votes
-
517 votes
-
102 votes
Hi everyone,
This seems to be important, so we’ll address it in one of the upcoming Plesk releases.
Please continue to vote so we can accurately assess the popularity of this request.
— AK
-
400 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
An error occurred while saving the comment I'd also like to see this happen. Personally I'd like it if there was a separate button next to FTP Access e.g. SFTP Users with the option to set the home directory for each user.
https://snag.gy/HK4ZFT.jpgThere would also need to be a limit on subscription level to how many SFTP users can be created to ensure reasonable usage.
Then developers would benefit a lot by being able to use sshfs.
There seems to be a related request as well https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/5030867-enable-chrooted-sftp-for-more-than-one-user-per-ac
-
349 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
-
222 votes
-
585 votes
Since Plesk Onyx you will be able to install memcache as a Docker container and configure http(s) proxy rule for it to map to your web app.
Docker and proxy rules are available in Plesk Onyx Preview already, you can try it here https://talk.plesk.com/threads/plesk-onyx-preview-and-feedback.337172/
SE
So far this feature is not entirely usable unless the directives issue is adressed. https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/17222720-ability-to-customize-nginx-per-site-template-e-g because we can't use location / directive. Please take another look at it as it is really important. This feature is only partially implemented and very limited in scope