Stefan Brauner
My feedback
31 results found
-
26 votes
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
-
10 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 -
7 votes
Could you clarify that we correctly got the case:
Plesk Admin wants to prohibit an ability for their customers to set up an email forwarding to external emails.
If yes, would it work if the related subscription will have additional permission, which will allow/disallow to manage mail forwarding at all for a particular subscription?SE
-
23 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 -
27 votes
One good reason why it is important to use own DKIM key is that for sending mail from different servers that service the same domain (e.g. during a migration) the key on the target needs to be the same as on the source.
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.
-- PD
-
23 votes
An error occurred while saving the comment -
35 votes
We will consider this functionality in upcoming releases if it will be popular. However, in part of integration with 3rd party, probably it will be faster if you create Plesk extension. Please refer to https://docs.plesk.com/en-US/17.0/extensions-guide/what-are-plesk-extensions%3F.76331/ to know how.
Everyone, please continue voting for this feature if you consider it important.
—
ET -
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.— rk
-
104 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
-
51 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 -
77 votes
The roles that you can set for additional user accounts can help achieve many of the aspects that are mentioned in this feature request. Please see the blog article https://www.plesk.com/blog/product-technology/how-to-grant-access-website-secure-way/ for getting started with roles.
-- PD
-
5 votes
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 -
89 votes
"1. Ability to control [DKIM] key length 1024Bit or 2048Bit (server wide)"
is available since Plesk 18.0.55, published August 29th, 2023
https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18055
"4. Ability to change the [DKIM] selector"
is available since Plesk 18.0.56, published Ocotber 10th, 2023
https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18056
Stay in the loop for more to come.
-- PD
-
25 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 -
4 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.
Thanks in advance!
--
IG
-
160 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 -
58 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
-
135 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 -
195 votes
-
629 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…
It would be great to see that feature in the future. Currently I have to disable HSTS in the Plesk Panel, disable the prefered www and then set the HSTS header with preload and the redirection to www in the nginx for each domain manually, because otherwise there is no HSTS header for the non-www-Page.
It would be great if it would be possible to set the preload directive, max age 1 year (6 years is not enough for preloading and I want to avoid 2 years) and the header set before the redirection to the prefered choicee (www or not)