Gabriel T
My feedback
45 results found
-
2 votes
Thank you for your input! We will consider this functionality for the upcoming releases if it becomes popular enough.
Everyone, please continue voting for this feature if you consider it important.
—AS
Gabriel T supported this idea · -
11 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.—
IGAn error occurred while saving the comment Gabriel T supported this idea · -
11 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.
—
IGGabriel T supported this idea · -
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.
—
IGGabriel T shared this idea · -
15 votes
An error occurred while saving the comment Gabriel T commented+100 for this. We currently install it on all our servers and it's a great tool. I'd love to see it ship with a PLESK installation.
Gabriel T supported this idea · -
11 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.BTW, we have following solution for Plesk – https://talk.plesk.com/resources/blocking-extra-bots-using-nginx.6/
—
IGAn error occurred while saving the comment Gabriel T commentedI just noticed your comment however adding manually a huge list of bad bots when there is a community maintained list is a tedious to say the least. I would think that making PLESK servers as secure as possible should be top concern out of the box. So far I haven't seen a single PLESK installation that hasn't at least suffered into the hands of bad bots at least once.
Gabriel T shared this idea · -
32 votes
Thank you for your input. We will consider the possibility of implementing this feature in upcoming releases.
— ES
Gabriel T supported this idea · -
1,295 votesGabriel T supported this idea ·
An error occurred while saving the comment Gabriel T commentedAdditionally you can load custom signatures in clamav and locate some very interesting malware other premium solutions ignore
-
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.
—
IGGabriel T supported this idea · -
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
Gabriel T supported this idea · -
196 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
Gabriel T supported this idea · -
54 votes
An error occurred while saving the comment Gabriel T commentedSince 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 Gabriel T commentedAs 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.
Gabriel T 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.
—
IGAn error occurred while saving the comment Gabriel T commentedThe 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 Gabriel T commentedI'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 Gabriel T commentedI'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.
Gabriel T shared this idea · -
110 votesGabriel T supported this idea ·
-
283 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
Gabriel T supported this idea · -
476 votesGabriel T supported this idea ·
-
451 votesGabriel T supported this idea ·
-
92 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 Gabriel T commented@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.
Gabriel T supported this idea · -
124 votesGabriel T supported this idea ·
-
544 votesGabriel T supported this idea ·
I think this should be considered as a very important task because service interruptions is the main reason hosting providers lose clients