• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Bug in subdomain.sh

A

ashopandreas

Guest
The --hard-quota parameter for the subdomain.sh Plesk API script doesn't work in 8.2.1. No matter what you set it to you always sets the quota to unlimited.
 
Originally posted by ashopandreas
The --hard-quota parameter for the subdomain.sh Plesk API script doesn't work in 8.2.1. No matter what you set it to you always sets the quota to unlimited.

Plesk CLI subdomain sets user quota according to system block size. If one specifies kilobytes value of hard_quota less then 1024, Plesk CLI sets hard quota to 0 (unlimited).
Also pay attention to hard quota type specification:

~# /usr/local/psa/bin/subdomain --help | grep -A 3 -- -hard_quota
-hard_quota <number>[K|M|G] hard disk quota (use 0 for
"unlimited", which is set by default.
You can specify this option when using
a separate FTP account)
~#

If you fail attend specification of the hard quota type, subdomain considers it to be in 'K', i.e. kilobytes.

./anb
 
Thank you for your help! I had missed the new K|M|G part of the parameter. It works just fine with those.
 
Back
Top