Nico Wiedemann
My feedback
35 results found
-
599 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…
-
84 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
-
70 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 -
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
-
1 vote
Thank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
6 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 -
6 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 -
396 votes
An error occurred while saving the comment -
208 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 rspamd's performance is far superior to SpamAssassin. Please make it available for use with Plesk.
-
2 votes
An error occurred while saving the comment Of course this would work, but that argument is applicable to most of the feature suggestions mentioned in this category. I was suggesting making this feature accessible in the Plesk interface.
-
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
-
13 votes
-
18 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.— rk
-
291 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.
—
AAAn error occurred while saving the comment +1 for CouchDB
-
30 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
The workarounds in the Knowledge Base (https://support.plesk.com/hc/en-us/articles/360000921073-How-to-add-an-alias-for-subdomain-in-Plesk-for-Linux-) are fine, but the first one lacks the organizational benefit of subdomains while the second fails when you are trying to use any of the SSL-certificate services provided by Plesk.