BigBlock Studios
My feedback
6 results found
-
1 vote
BigBlock Studios shared this idea ·
-
98 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
BigBlock Studios supported this idea ·
-
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
BigBlock Studios supported this idea ·
-
2 votes
An error occurred while saving the comment -
3 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!
-- SH
BigBlock Studios supported this idea ·
An error occurred while saving the comment BigBlock Studios commented
I ran into this issue during a migration where bugs in the ***** DNS manager required me to manually update DNS for all migrations using the CLI. Something like this would be useful.
I would suggest 2 updates,
- --list option for the domalias utility
- --list-alias for the site utilityor something like plesk bin domalias <domain>
-
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 BigBlock Studios commented
Will it be possible to prevent plesk customers from changing their usernames as well - this causes issues with the blesta billing portal.
BigBlock Studios supported this idea ·
Ran into this issue on an Amazon lightsail container ... AWS does not actually provide the root password, requiring it to be changed.
Amazon default keys also seem to be starting to use a different key type or encryption, could not use the root keys I generated because they were 'incompatible' migrator did not say why they were incompatible....