I suggest you ...

Overuse Policy: Overuse is not allowed + Grace Period

Right now there are 3 options:

- Overuse is not allowed (this is preferred but will disable customers site once limit is hit)
- Overuse of disk space and traffic is allowed
- Overuse is allowed (not recommended)

Scenario:

A resellers Overuse Policy is set to:
Overuse is not allowed

That reseller has his warning set to 90% of his 10GB package.
But on 1 day, one of his customers uploads 2GB.

Effect: His total package has 12GB and the nightly run will disable his package, without warning.

Result: The reseller is angry because all of his customers are offline,
only because one person (unknowingly) made the reseller go over his limits.
We are the "bad guys".

Wanted effect:

Plesk notice a sudden increase, but knows that it has not yet sent any warnings.
Plesk sends a warning first, and waits x days untill it has sent x warnings to the reseller or customer. (grace period)

In this way, we can tell a suspended reseller or customer that we have warned them, multiple days, before suspending anything.
This helps us in not being the "bad guys".

The way I see it would be like:

- Overuse is not allowed
- Overuse is not allowed (Grace Period)
Allow the customer X days to be in overuse
Notify customer by email in cases of overuse.
- Overuse of disk space and traffic is allowed
Notify customer by email in cases of overuse.
- Overuse is allowed (not recommended)
Notify customer by email in cases of overuse.

See attached screenshot of Google Chrome Live Edit Concept.

32 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)

We’ll send you updates on this idea

Stéphan S shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

5 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
  • Jurgen Bruggeman commented  ·   ·  Flag as inappropriate

    I think this feature is a must. We get more and more complaints of users getting suspended for overusage. Te best way is to allow a automatic grace period instead of blocking it directly.

  • [Deleted User] commented  ·   ·  Flag as inappropriate

    This should have been added YEARS ago. Our customers always complain about this, that their account is "suddenly" offline. Though it's mainly there fault, but I completely understand their concern. It's 2017, not 2007! And customer is king.

    Furthermore; make the above available or do the quota checks several times a day, so customers get an email early on instead...

    Sidenote; we had quite a few complaints about this in the past 1,5 - 2 years about this. 80% were fed up with this and we moved them to DirectAdmin instead. So Plesk, take notice of this and take action... As I said this should have been added years ago...

  • TheSurge commented  ·   ·  Flag as inappropriate

    We already lost several customers, who's website went offline, because;

    1) someone send them several big emails with pictures
    2) wordpress updates and created backups
    3) installatron updates and created backups

    We already ditched almost half our Plesk licenses for alternatives (for example DirectAdmin and cPanel).

    Unless something is going to be done, we will be moving all our Plesk licenses....

  • Avrosh commented  ·   ·  Flag as inappropriate

    Is there a way to get the sit back up if the suspension has happened?

  • Dave commented  ·   ·  Flag as inappropriate

    This has happened numerous times on several of our servers. Customer might get lots of new emails with large attachments; this causes the their resources to be over their allowed limit. But instead of getting the warning email it goes straight to suspending the account.

    There should always be a warning email sent out before suspending a domain / account. The way Stephan explains it is very good. Or a simpler version is for the suspension script to check if a warning email has gone out. If not send the warning email instead. Then the following night suspend.

Feedback and Knowledge Base