111 results found

1. DNS record editor for all domains (bulk editing, selective editing)

   Editor for all DNS records in the Plesk system, it is very time consuming to mass check records and alter them eg. SPF, DMARC, autodiscover records.

   Maybe the editor could also have an option to reset records to DNS template.

   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 →
   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
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your idea! 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

2. Support dateext setting for domain logs

   Currently domain logs look like

   541004 -rw-r--r-- 2 root root 0 Mar 2 15:01 accesslog
   562544 -rw-r--r-- 2 root root 0 Mar 2 15:01 accesslog.processed
   538890 -rw-r--r-- 2 root root 827 Mar 2 15:01 accesslog.processed.1.gz
   538922 -rw-r--r-- 2 root root 642 Mar 2 14:59 accesslog.processed.2.gz
   538925 -rw-r--r-- 2 root root 907 Mar 2 14:59 accesslog.processed.3.gz
   538908 -rw-r--r-- 2 root root 582 Mar 2 14:58 accesslog.processed.4.gz
   538915 -rw-r--r-- 2 root root 787 Mar 2 14:57 access_log.processed.5.gz

   If user sets dateext in logrotate config they look more user firendly
   -rw-r--r-- 2 root root 8985 Mar 2 13:25 accesslog
   -rw-r--r-- 2 root root 26020 Mar 2 13:21 accesslog.processed
   -rw-r--r-- 1 root root 20 Feb 12 03:50 accesslog.processed-20170213.gz
   -rw-r--r-- 1 root root 20 Feb 13 03:16 accesslog.processed-20170214.gz
   -rw-r--r-- 1 root root 20 Feb 14 03:23 accesslog.processed-20170215.gz
   -rw-r--r-- 1 root root 20 Feb 15 03:39 accesslog.processed-20170216.gz

   However Plesk would not rotate such logs correctly (old logs are not being deleted from vhost/domain.tld/logs directory.

   Currently domain logs look like

   541004 -rw-r--r-- 2 root root 0 Mar 2 15:01 accesslog
   562544 -rw-r--r-- 2 root root 0 Mar 2 15:01 accesslog.processed
   538890 -rw-r--r-- 2 root root 827 Mar 2 15:01 accesslog.processed.1.gz
   538922 -rw-r--r-- 2 root root 642 Mar 2 14:59 accesslog.processed.2.gz
   538925 -rw-r--r-- 2 root root 907 Mar 2 14:59 accesslog.processed.3.gz
   538908 -rw-r--r-- 2 root root 582 Mar 2 14:58 accesslog.processed.4.gz
   538915 -rw-r--r-- 2 root root 787 Mar 2 14:57 access_log.processed.5.gz

   If user sets dateext in logrotate config they look more user firendly
   -rw-r--r-- 2 root root 8985 Mar 2… 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  ·  Web / HTTP functions  ·  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
   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

3. SSH Terminal access with another administrative user

   The root user is disabled on the server for security reasons.
   It is required to configure SSH Terminal extensions to log in with another administrative user

   9 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  ·  Extensions  ·  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
   already available  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   We assume that this request is based on a typical configuration where "permitrootlogin" in the SSH configuration file is set to "false" and the requirement is to being able to use the SSH extension for Plesk admin accounts anyway. For that case the workround can be applied: Simply add the lines

   Match Address 127.0.0.1
   PermitRootLogin yes

   to the /etc/ssh/sshd_config, then reload SSH service once (# service sshd reload). It will then still not be possible to login with "root" from external sources, but it will allow the extension to log you in with an admin account.  https://support.plesk.com/hc/en-us/articles/4410634559250

   -- PD

4. chrooted shell, new folder strukture (root folders invisible)

   The current folder structure is very unclear if the client has been assigned a new chrooted-environment. Please look at my new suggestion for a folder structure.

   •  

   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 →
   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
   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

5. Allow additional admin staff at the root level

   AFAIK there is only one admin user in Plesk, able to manage the whole system including resellers. It would be helpful if we could assign 'whole system administrators' not just at the domain level.

   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
   already available  ·  AdminSergey L (CTO, Plesk International GmbH) responded

   You can add additional administrators at server level as well. See “Additional Administrators” menu item

6. 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
   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

7. Ability to migrate accounts from one plesk node to another

   It would save huge amounts of time if the admin using the customers plesk account credentials was able to migrate the whole account from the previous hoster without needing to have root access to the server like you can do in cpanel. In order to migrate plesk customers from other companies you need to do it manually !

   21 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

   open discussion  ·  2 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

8. Scan Wordpress through CLI

   To implement the button Scan from user interface, through CLI so that the Plesk Admin (or root) can search newly installed Wordpress on the server.

   7 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  ·  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
   open discussion  ·  IgorG 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

9. Set a senders email address for Plesk notifications

   I am sending mails from an external server, my Plesk Servers do not even have mail setup. Plesk offers the option to send notification mails (like backup errors,...) using an external SMTP server, but all mails get sent using the mail address
   root@servername.domain.tld

   My SMTP server does not have this mail address or even domain setup. I would like to set a custom email address for Plesk to send mails from in order to not have to set up a domain and mail address for every Plesk server.

   194 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

   42 comments  ·  Mail  ·  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
   completed  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   This feature has been added to Plesk version 18.0.45. It can be set in the panel.ini file.

   https://support.plesk.com/hc/en-us/articles/115003223785-How-to-change-from-field-in-Plesk-email-notifications-sent-to-clients-

   --

   PD

10. Disk usage by folders / directory tree

    At this moment, there is only disk usage summary by domains. It would be great, if we could check the disk usage by folders. Best option would be expanding directory tree (just like it was done in the other known "customer Panel").

    Here is my attempt to visualize the idea:

    [-]root (1 GB)
    .|--[+] cgi-bin (0 B)
    .|--[+] etc (5 KB)
    .|--[-] httpdocs (900 MB)
    .....|--[+] folder1 (400 MB)
    .....|--[+] folder2 (500 MB)
    .|--[+] statistics (10 MB)

    22 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

    4 comments  ·  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
    completed  ·  AdminSergey L (CTO, Plesk International GmbH) responded

    The function is already available through “Calculate Size” button in file manager

11. Serverbackups not include to Customer Quota

    There is an issue in the quota calculation in the following point:

    If i create a customer Hosting Plan with 5GB Quota.
    The Customer have 2GB Data in his Hosting, and I create a Serverbackup via the Plesk Backupmanager as root.

    No the Customer Quota are increased to 4GB.

    If the Customer creates self backups - it is okay to include them in the Quota Calculation.

    But i don't think that the root-Serverbackup should be calculated in okay thanks for help

    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  ·  Backup / Restore  ·  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
    already available  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    The feature is available in Plesk 12.0. You can find the settings if you open “Tools & Settings” > “General Settings” > “Server Settings”.

    — ES

12. Don't activate new services by default in existing service plans

    If you add something new to plesk (for example node.js or the mail autodiscover), this function is automatically added to existing service plans. This is not desirable.

    I want to choose if I want to add node.js to a particular service plan afterwards... Now I have to disable it in every service plan where I don't want it.

    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
    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

13. Add Firewall rule to block outgoing mail for non-Postfix / non-qmail

    iptables -A OUTPUT -d 127.0.0.1 -p tcp -m tcp --dport 25 -j ACCEPT
    iptables -A OUTPUT -p tcp -m tcp --dport 25 -m owner --gid-owner postfix -j ACCEPT
    iptables -A OUTPUT -p tcp -m tcp --dport 25 -m owner --gid-owner mailman -j ACCEPT
    iptables -A OUTPUT -p tcp -m tcp --dport 25 -m owner --uid-owner root -j ACCEPT
    iptables -A OUTPUT -p tcp -m tcp --dport 25 -j REJECT --reject-with icmp-port-unreachable

    Would be nice to add this to the Plesk Firewall Module.

    This disables malicious scripts of sending direct mail.

    Other malicious mails sent through localhost (Postfix / qmail) will be scanned first.

    iptables -A OUTPUT -d 127.0.0.1 -p tcp -m tcp --dport 25 -j ACCEPT
    iptables -A OUTPUT -p tcp -m tcp --dport 25 -m owner --gid-owner postfix -j ACCEPT
    iptables -A OUTPUT -p tcp -m tcp --dport 25 -m owner --gid-owner mailman -j ACCEPT
    iptables -A OUTPUT -p tcp -m tcp --dport 25 -m owner --uid-owner root -j ACCEPT
    iptables -A OUTPUT -p tcp -m tcp --dport 25 -j REJECT --reject-with icmp-port-unreachable

    Would be nice to add this to the Plesk Firewall Module.

    This disables malicious scripts of sending direct mail.

    Other malicious mails sent through localhost (Postfix / qmail) will… more

    58 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

    open discussion  ·  7 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

14. a little text area for comand plesk in ssh root

    modificarcategoria2.php

    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  ·  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
    declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    UPD: No reply for the month. Closed.
    —
    IG

15. Adding shortcuts and checks compatibility testing and modifications / repos / scripts etc. Both configurations fcg php2/php5/mod critical ro

    Adding shortcuts and checks compatibility testing and modifications / repos / scripts etc.
    Both configurations fcg php2/php5/mod critical root and etc, to configurations that do to root via ssh and plesk p
    Always use a script checks the somenew with the system, before applying definitely parse type and script applications.
    Checkout with your system before final save.

    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
    declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

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

16. Cloud storage extension for Plesk

    Please make an extension to allow users to have a file storage space, or possibly even a module in WPB, where a location, usernames, passwords, security (SSL or encryption) can be configured. Users can use this space as a logical drive, much like DropBox.
    Expand on this and create an Android and IOS app to allow users to access their files via cell app.
    The location of the physical data would have to be able to be defined by the system admin to an external storage area, off the actual machine, by network name. For instance a server working as a NAS or SAN on the network would have a share that the Plesk server would be setup as a \Root, then within the \Root, UserData would point to their respecitive share within \Root such as \Root<site><username>
    Thank you!
    David

    Please make an extension to allow users to have a file storage space, or possibly even a module in WPB, where a location, usernames, passwords, security (SSL or encryption) can be configured. Users can use this space as a logical drive, much like DropBox.
    Expand on this and create an Android and IOS app to allow users to access their files via cell app.
    The location of the physical data would have to be able to be defined by the system admin to an external storage area, off the actual machine, by network name. For instance a server working as… 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  ·  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
    declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

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

17. Modification of application installation path

    For instance, Joomla installs to a subdirectory called /joomla which makes the URL of the Joomla site: www.domain.com/joomla

    That is not an acceptable path. Our customers are then moving the Joomla files into their root /httpdocs directory for a better URL for the site. After that, the default buttons in the panel no longer work. It would be great if you could make the path editable for the customer to continue to use the installation buttons to get to their site and administrator panel from the panel.

    10 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

    7 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
    completed  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    This feature is already implemented in the upcoming Plesk 12.1 release. We encourage you to check the implementation in one of upcoming Plesk previews and let us know what you think. Everyone, thanks for your input and votes.

    Default installation path for all webapps is ‘/’

18. Custom error documents default settings

    The actual condition is as follow:

    Plesk11.0

    Access to Domains > Open in Control Panel > Websites & Domains > domain.name > Custom error documents

    Plesk12.0

    Domains > Websites & Domains > Hosting Settings > Custom error documents > Custom error documents

    Above mentioned configuration is enabled as a default but
    as for CLI said as follow:

    [root@Plessk11GMO bin]# pwd
    /usr/local/psa/bin
    [root@Plessk11GMO bin]# ./subscription -h

    Usage: subscription command <subscription_name> [options]

    Available options:
    
    -err_docs          <true|false>    Custom error documents support
                                       (default: false)
    

    [root@Plessk11GMO bin]#

    Actual result is enabled but CLI help statement "(default: false)" leads confusion.
    My request is modify from (default: false) to (default: true) in order to avoid
    confusion and also make sense.

    The actual condition is as follow:

    Plesk11.0

    Access to Domains > Open in Control Panel > Websites & Domains > domain.name > Custom error documents

    Plesk12.0

    Domains > Websites & Domains > Hosting Settings > Custom error documents > Custom error documents

    Above mentioned configuration is enabled as a default but
    as for CLI said as follow:

    [root@Plessk11GMO bin]# pwd
    /usr/local/psa/bin
    [root@Plessk11GMO bin]# ./subscription -h

    Usage: subscription command <subscription_name> [options]

    Available options:
    
    -err_docs          <true|false>    Custom error documents support
                                       (default: false)
    

    [root@Plessk11GMO bin]#

    Actual result is enabled but CLI help statement "(default: false)" leads confusion.… 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  ·  Web / HTTP functions  ·  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
    not a feature  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    The default value of this option is used when subscription is created via CLI without specifying any hosting plan and without providing a value for this option. If a subscription is created via Plesk UI, values of hosting options (including “Custom error documents”) are set based on what is specified in the selected hosting plan.
    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

19. Allow creating subdomains by creation of corresponding folder in root domain's folder
    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  ·  Web  ·  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

20. Main directory name as Plesk username.

    Main domain is changed again, customers also want to change the root directory or the old domain /var/www/vhosts/domain.tld/httpdocs not see,

    much better would be /var/www/vhosts/mainusername/httpdocs

    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  ·  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
    declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

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

    —
    
IG