1194 results found

1. Block client IP for SQL Server for multiple failed logins remote connection

   When database remote connections are allowed from any host, there are numerous failed login (hacking) attempts.
   Database logs show failed attempts are usually for multiple login Ids and from multiple IPs at the same time.
   Although strong passwords ensure safety to a level, it would be better if such attempts could be blocked to some more extent by configurations/settings like:
   * Blocking an IP after n failed login attempts.
   * Manually block/unblock an IP like a Blacklist/Whitelist IP option.
   * Unblocking can be auto after a configurable time span e.g. 30 min, 6 hours, 24 hours etc.
   * Database server logs in Plesk with filtering options.
   * Reporting mechanism in Plesk by IP for count of blocks, unblocks with timestamp etc.

   When database remote connections are allowed from any host, there are numerous failed login (hacking) attempts.
   Database logs show failed attempts are usually for multiple login Ids and from multiple IPs at the same time.
   Although strong passwords ensure safety to a level, it would be better if such attempts could be blocked to some more extent by configurations/settings like:
   * Blocking an IP after n failed login attempts.
   * Manually block/unblock an IP like a Blacklist/Whitelist IP option.
   * Unblocking can be auto after a configurable time span e.g. 30 min, 6 hours, 24 hours etc.
   * Database… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Security  ·  Delete…  ·  Admin →
   already available  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   You can use Plesk fail2ban feature with special mysql jail. More details you can find here https://talk.plesk.com/threads/fail2ban-for-mysql.343704/
   —
   IG

2. URL-based branding logos

   I suggest enabling Plesk to allow different branding logos in the login screen and the top left corner of the session, depending on the full-qualified hostname used to reach the server. For example, if a server can be reached through 2 different names, the idea would be to be able to set a default branding logo and have alternative ones depending on the URL used to connect to the server. Here's an example:

   plesk.domain1.com -> main logo (default)
   plesk.domain2.net -> alternative logo 1
   hosting.domain3.co -> alternative logo 2
   any other aliases/URLs -> main logo (default)

   •  

   •  

   •  

   •  

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

   Everyone, please continue voting for this feature if you consider it important.

   -- SH

3. Set maximum folder size.

   Divide your space better.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Databases  ·  Delete…  ·  Admin →
   declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input!
   Unfortunately, we have to close your request, because over the years it has not become quite popular for further implementation.
   —
   IG

4. An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

   An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Web / HTTP functions  ·  Delete…  ·  Admin →
   not a feature  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   This is a known issue having a solution, which is described in the knowledge base: http://kb.odin.com/en/123076

   We are closing this item, because it is not a feature request. If you want to continue discussion or get advice from the community, please continue at http://forum.odin.com

   — ES

5. DNS Views available by plesk

   Some users like me, likely have a server in an internal network (192.168.x.0, for example). I know how to configure bind to resolve internally and externally my domains, implementing views. In one of the views that will only be avilable for internals, the domain will resolve only an internal ip, and in the other view it will resolve the public IP. This is a feature that webmin/virtualmin supports from not far ago. I'm migrating everything to a new server and I decided to install plesk to create the same environment than in our production server, in OVH. I've set the views manually in the old server, not through webmin, so I don't know if that feature works well enough, but it would be really, really great if you do it.

   Some users like me, likely have a server in an internal network (192.168.x.0, for example). I know how to configure bind to resolve internally and externally my domains, implementing views. In one of the views that will only be avilable for internals, the domain will resolve only an internal ip, and in the other view it will resolve the public IP. This is a feature that webmin/virtualmin supports from not far ago. I'm migrating everything to a new server and I decided to install plesk to create the same environment than in our production server, in OVH. I've set the… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  DNS  ·  Delete…  ·  Admin →
   declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input!

   Unfortunately, we have to close your request, because over the years it has not become quite popular for further implementation.

   
— AY

6. Scheduled tasks Add user dropdown

   When logged in with the main admin/root account click in the right hand column on "Scheduled Tasks" takes me to the Cron jobs that I can setup.

   There is no indication as what system user will run the task? This has cuased a couple of my crons to fail and struggled to find the issue.

   Eventually I found I needed to under Main nav - Server tab then to Scheduled Tasks.. this takes me to the users lists that I can set cons for specific users.

   Very confusing!

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Usability and UI  ·  Delete…  ·  Admin →
   already available  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   In Plesk 12.5, you can select the system user while creating a scheduled task. A drop-down menu was added for that purpose.

   Note: You can specify a system user only for server-wide scheduled tasks, but not for scheduled tasks of a webspace (subscription). The system user of a webspace is used to run scheduled tasks of a webspace, and that user cannot be changed.

   —ES

7. Add ability to remove last IP address on the network interface via Plesk

   For example, the customer has 2 network interfaces: Ethernet1 and Ethernet2. On the Ethernet 2 network interface only one (203.0.113.3 ) IP address can be found.

   In an attempt to remove 203.0.113.3 IP address via Plesk > Tools & Settings > IP Addresses the following error is shown:
   Error: Cannot remove the IP address 203.0.113.3 because it is the last IP address present on a network interface.

   Please add the possibility in Plesk to remove the IP address via a Plesk > Tools & Settings > IP Addresses, even if it is the latest IP address on the network interface.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Usability and UI  ·  Delete…  ·  Admin →
   declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Upd: Sorry, we are closing the request as no information was provided for over a month.

   —
   
IG

8. Add possibility to set "Can be used to log in to Plesk" unchecked by default during mail account creation

   Creating mail account In Plesk panel Domains > example.com > Mail accounts > Create Email Address has an option "Can be used to log in to Plesk" which is checked by default.
   There can be a situation when you can by mistake leave the option checked but you don't plan to permit to log in to Plesk with created mail account.
   So it would be convenient to have this option unchecked by default.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Plesk (general)  ·  Delete…  ·  Admin →
   declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Logging in to Plesk as the mailbox user will only allow that user to edit his own settings of that mailbox, e.g. the password. The effect of this option is marginal. We are also only talking about a preset change from "checked" to "unchecked". It's only a mouseclick to uncheck the box, and when the default is changed to "unchecked" other users will complain that they now need to check this box each time they add a mailbox.

   As this feature did not become popular and as the setting is already optional we must decline it.

   -- PD

9. Change (or add option to select) value that is used for the customer’s account root

   Currently, when a subscription is created and the customer adds new domains, the following physical structure is created on a server:

   C:\vhosts\primary.domain\new.domain

   where primary.domain is the primary domain of the subscription and new.domain is another domain, created by the customer.

   Sometimes, in this scenario, a number of new domains created by the customer might be quite big, so physical structure becomes something like this:

   C:\vhosts\primary.domain\new.domain

   C:\vhosts\primary.domain\new1.domain

   ...

   C:\vhosts\primary.domain\new199.domain

   C:\vhosts\primary.domain\new200.domain

   In these circumstances, when the primary domain's name is changed, for example:

   primary.domain changed to newprimary.domain so physical structure is changed to C:\vhosts\newprimary.domain*

   There is a lot of data that has to be updated in Plesk database and IIS (new locations have to be applied to every domain, every user etc). This process takes some noticeable amount of time depending on the number of domains. This might be especially important when changes are made through API, since response time is quite long.

   Here is the following suggestion on the improvement:

   A customer sets up an account with a primary domain primary.domain, and a “account root” id of “x31430a42” is associated to the account [the x is purely to ensure that this value does not start with a number]

   a. “C:\vhosts\x31430a42\primary.domain is created

   b. The IIS website “primary.domain” is created and configured to point to C:\vhosts\x31430a42\primary.domain\

   2) A second domain is created called “new.domain”

   a. “C:\vhosts\x31430a42\new.domain is created

   b. The IIS website “new.domain” is created and configured to point to C:\vhosts\x31430a42\httpdocs

   3) Repeat step 2 200 more times

   a. Each folder path is created, and IIS sites are created and pointed to the relevant folder

   4) Change the primary domain to “newprimary.domain”

   a. Impact 1: only the impacted site “mydomain.com” gets change from C:\vhosts\x31430a42\primary.domain to C:\vhosts\x31430a42\newprimary.domain

   b. Impact 2: the only update to IIS would be to update the primary.domain site to reflect the change to newprimary.domain (updated settings to reflect the new name and new file path)

   This will reduce the amount of data to-be-updated and increase process efficiency.

   Currently, when a subscription is created and the customer adds new domains, the following physical structure is created on a server:

   C:\vhosts\primary.domain\new.domain

   where primary.domain is the primary domain of the subscription and new.domain is another domain, created by the customer.

   Sometimes, in this scenario, a number of new domains created by the customer might be quite big, so physical structure becomes something like this:

   C:\vhosts\primary.domain\new.domain

   C:\vhosts\primary.domain\new1.domain

   ...

   C:\vhosts\primary.domain\new199.domain

   C:\vhosts\primary.domain\new200.domain

   In these circumstances, when the primary domain's name is changed, for example:

   primary.domain changed to newprimary.domain so physical structure is changed to C:\vhosts\newprimary.domain*

   There is a lot of data that has… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   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

10. Pre-schedule setting to set the sending of out of office message on [dd/MM/yy] and auto cut off the out of office on [dd/MM/yy].

    Hi, our users inform me that they will be out of office on next month 1 June to 10 June, because I will be on leave on the same period and go to deep sea diving without internet.

    Please add feature in the Linux email server out of office function, to allow pre-schedule setting to set the sending of out of office message on [dd/MM/yy] and auto cut off the out of office message on [dd/MM/yy].

    Thank you.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Mail  ·  Delete…  ·  Admin →
    not a feature  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    You need to use Scheduled Task of webmail calendar for this purpose. We are closing your request as it doesn’t include any proposal.
    -
    IG

11. Allow Plugin sets to add plugins from wordpress.org catalog via WordPress Toolkit CLI

    Please, implement a feature for adding plugins to plugin sets from wordpress.org catalog via WordPress Toolkit CLI

    The CLI command 'plesk ext wp-toolkit --sets -operation add-plugin' requires a plugin to first be installed either in GUI or CLI using 'plesk ext wp-toolkit --plugins'.

    The issue here is that the 'plesk ext wp-toolkit --plugins' command is currently unable to install plugins from wordpress.org in the same way that you can via the GUI.

    As an example, look at this set which contains 2 plugins, one added using the command 'plesk ext wp-toolkit --plugins -operation add -source-url https://downloads.wordpress.org/plugin/w3-total-cache.0.9.7.zip'; and the other added using the GUI to search wordpress.org for Wordfence.

    =====================================================

    plesk ext wp-toolkit --sets -operation info -set-id 9

    Set:
    ID Owner GUID Name
    9 7c5241ec-7ab7-12e9-a537-006056813f14 Standard

    Plugins:
    ID Name Slug Source Version
    11 W3 Total Cache w3-total-cache direct upload 0.9.7

    13 Wordfence Security – Firewall & Malware Scan wordfence wordpress.org latest

    As you can see, the one installed via CLI is version locked and does not count as being sourced from wordpress.org. The one installed via GUI will use the latest version from wordpress.org.

    To be clear, this feature request is asking for the ability to add a plugin to the server so that it ends up like plugin 13 in the example, not plugin 11.

    I note that Plesk Staff closed a similar Feature Request, which appears to be asking for the same thing.

    https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/38062978-installing-plugins-from-wordpress-org-catalog-via

    Please, implement a feature for adding plugins to plugin sets from wordpress.org catalog via WordPress Toolkit CLI

    The CLI command 'plesk ext wp-toolkit --sets -operation add-plugin' requires a plugin to first be installed either in GUI or CLI using 'plesk ext wp-toolkit --plugins'.

    The issue here is that the 'plesk ext wp-toolkit --plugins' command is currently unable to install plugins from wordpress.org in the same way that you can via the GUI.

    As an example, look at this set which contains 2 plugins, one added using the command 'plesk ext wp-toolkit --plugins -operation add -source-url https://downloads.wordpress.org/plugin/w3-total-cache.0.9.7.zip'; and the other… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
    declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    We are closing the current request due to lack of demand over the years. Please note that just because the source of the set appears as "direct upload" it doesn't mean the plugin/theme in question will not be updated on the WordPress instance(s) upon an available new version. As long as the plugin/theme in question have the same name as a plugin/theme hosted in the wordpress.org repository you should get updates without an issue.

    -- SH

12. Limiting access to Plesk panel by specifying the allowed dst addresses

    It is required to control the accessibility of the Plesk panel by having an option to permit access only by the specified server's IP's. For example:
    Let's say there are 172.16.1.10 & 172.16.1.11 IPs on the server both assigned with a domain name panel.example.com.
    Option "Specified domain" is set in Tools&Settings > Customize Plesk URL.
    Any other IP address on that should NOT serve the login procedure.

    However, when this server has a full subnet 172.16.1.32/27 added as the secondary IP addresses, it is possible to open any of them via the Web Browser, afterward press "Log in to Plesk" and you'll get redirected to
    https://172.16.1.*/login_up.php?* and will end up facing a Plesk Login page on that IP which is something that should NOT happen.

    Thus, there has to be an option to make all IPs from the 172.16.1.32/27 network pool to stop serving as authorization ways.

    It is required to control the accessibility of the Plesk panel by having an option to permit access only by the specified server's IP's. For example:
    Let's say there are 172.16.1.10 & 172.16.1.11 IPs on the server both assigned with a domain name panel.example.com.
    Option "Specified domain" is set in Tools&Settings > Customize Plesk URL.
    Any other IP address on that should NOT serve the login procedure.

    However, when this server has a full subnet 172.16.1.32/27 added as the secondary IP addresses, it is possible to open any of them via the Web Browser, afterward press "Log in to… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Plesk (general)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    To let the Plesk login react only on a single IP address or a defined address range is a valid request. 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

13. Resource usage report per Service plan

    Please implement an option in Plesk to generate a resource usage report per Service plan.

    For example, the report in Tools & Settings > Summary Report could have a section that provides the usage data per Service plan.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Do not automatically delete non-Plesk Route 53 records

    When making any update to a DNS zone, all records that were not created/synched with Plesk are automatically deleted. This prevents users from using advanced Route 53 functionality, such as aliases (for CDN, load balancer, etc). Because Plesk does not support AWS aliases (which is fair enough), this specific functionality MUST be configured directly in Route 53. That would only be a minor inconvenience, if Plesk didn't actively delete any record not synched with Plesk on any unrelated DNS update. This means Plesk-managed domains can't really use any advanced AWS functionality or Plesk will take the site offline.
    If Plesk simply leaves either non-Plesk synched records alone, or even just those set as a Route 53 alias, this would enable a world of possibilities!

    When making any update to a DNS zone, all records that were not created/synched with Plesk are automatically deleted. This prevents users from using advanced Route 53 functionality, such as aliases (for CDN, load balancer, etc). Because Plesk does not support AWS aliases (which is fair enough), this specific functionality MUST be configured directly in Route 53. That would only be a minor inconvenience, if Plesk didn't actively delete any record not synched with Plesk on any unrelated DNS update. This means Plesk-managed domains can't really use any advanced AWS functionality or Plesk will take the site offline.
    If Plesk… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  DNS  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    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

15. Setting to lock a service plan for new customers/domains.

    Hey there,

    I just wanted to change the default php version in all our service plans, but then all customers would have the new php version too. I can't just change it, 50% of the websites would be offline for sure.
    Can you add a setting to lock a service plan for new customers? So i can just clone the service plan and change the php version. You shouldn't be able to chose the old service plans, just the new ones.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Usability and UI  ·  Delete…  ·  Admin →
    declined  ·  IgorG responded

    Thank you for your input!
    Unfortunately, we have to close your request, because over the years it has not become quite popular for further implementation.
    —
    IG

16. Add the ability to manage the default WordPress Toolkit Security Measures before setting up the instance

    Add the ability to manage the default WordPress Toolkit Security Measures before setting up the instance, e.g. via some options in panel.ini.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    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

17. Regenerate cron jobs when performing dist-upgrade

    When performing dist-upgrade, following recommended KB procedure, the list of PHP handlers shown under Scheduled Tasks > Use PHP version is not updated tor reflect the new PHP version from OS vendor.

    For example, after upgrading from Ubuntu 14 to 16, such list still shows "PHP 5.5.9 from OS vendor". This is not just a visual glitch but a serious problem that stops from working all cronjobs that was set to be run with PHP 5 from OS vendor and that version is unavailable anymore.

    In the example above, after upgrading to Ubuntu 16, PHP 5 is not available anymore and these cronjobs fails with "/bin/sh: /usr/bin/php5: No such file or directory" with no warnings during update process. You should fix them manually, opening one by one and saving settings again (this will regenerate cronjobs).

    Also plesk repair wasn't helpful as it does not regenerate cronjobs

    When performing dist-upgrade, following recommended KB procedure, the list of PHP handlers shown under Scheduled Tasks > Use PHP version is not updated tor reflect the new PHP version from OS vendor.

    For example, after upgrading from Ubuntu 14 to 16, such list still shows "PHP 5.5.9 from OS vendor". This is not just a visual glitch but a serious problem that stops from working all cronjobs that was set to be run with PHP 5 from OS vendor and that version is unavailable anymore.

    In the example above, after upgrading to Ubuntu 16, PHP 5 is not available anymore… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Plesk (general)  ·  Delete…  ·  Admin →
    not a feature  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for reporting this bug, we have forwarded it to developers.

    Note: only feature requests are allowed here, so we would appreciate if you post bugs and issues on our forum at https://talk.plesk.com. We are closing this request, since it does not contain any feature suggestions.

    — AY

    Upd: Bug was confirmed and submitted by developers as PPPM-7371

18. Lock DNS records | Disable Reset to default

    We have the "dmarc"- record in our template having a placeholder for the value. At the time the Record "dmarc" was edited by adding the value, mostly every DNS record is no more in the state of the DNS template.

    Therefore it is important to have some policies:
    - The button "Reset to default" can be disabled on Admin and Reseller level.
    - The button "Master/*****" can be disabled. Usually this functionality is not needed.
    - For certain very important DNS setting, a "Lock" button might make sense. If applied, this record can not be edited anymore by resellers or customers.

    DNS is one of the most important parts and therefore it needs to be protected from people, which dnon't know, what their are doing.

    We have the "dmarc"- record in our template having a placeholder for the value. At the time the Record "dmarc" was edited by adding the value, mostly every DNS record is no more in the state of the DNS template.

    Therefore it is important to have some policies:
    - The button "Reset to default" can be disabled on Admin and Reseller level.
    - The button "Master/*****" can be disabled. Usually this functionality is not needed.
    - For certain very important DNS setting, a "Lock" button might make sense. If applied, this record can not be edited anymore by… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    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

19. Vertical menus should optionally look like folders with + sign, not CSS-Flyouts.

    If you have a vertical menu in PresenceBuilder (left or right), it should automatically (or at least offer the choice to) look like a folder-structure which can be additionally set to "always show the current level opened", not just this CSS-Flyout-thingy when hoovering over the arrow to the right you have to catch with your mousepointer.

    It would be more intuitive, if folders with submenus have a "+" sign prefixing it or inside them, and the current open/active folder has a "-" sign prefixing or in there and shows all submenus (if available).

    And those submenus or entries should be of course intended. Just the usual look a normal Windows or Linux/Mac user would expect when working with folders/files on his PC.

    Cheers,
    Eric

    If you have a vertical menu in PresenceBuilder (left or right), it should automatically (or at least offer the choice to) look like a folder-structure which can be additionally set to "always show the current level opened", not just this CSS-Flyout-thingy when hoovering over the arrow to the right you have to catch with your mousepointer.

    It would be more intuitive, if folders with submenus have a "+" sign prefixing it or inside them, and the current open/active folder has a "-" sign prefixing or in there and shows all submenus (if available).

    And those submenus or entries should be… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    We do not plan on introducing major changes to Web Presence Builder at the moment.

    —AK

20. Add abilty to set the main subscription domain as sender address for the subscription cronjob notiffications

    Add abilty to set the main subscription domain as sender address for the subscription cronjob notiffications. For example sysuser.@example.com instead of sysuser@hostname

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    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