cPanel & WHM Version 94 has been released, and brings a slew of great updates. Take a look at what is included, and then upgrade today!

Bandwidth overruns - notify only, don't suspend account

spaceman shared this idea 8 years ago
Open Discussion

My understanding is that there's no opportunity to have WHM auto-notify account holders who have exceeded their bandwidth without also auto-suspending their account. This has been well discussed here:


http://forums.cpanel.net/f5/bandwidth-overage-notify-only-130809.html


It's essential that we should be able to auto-notify accounts that are exceed their bandwidth *without* also suspending their accounts.


Thanks,


Ross

Comments (13)

photo
5

I agree, this is essential.


In my opinion, the default setting (disable HTTP without notifying anyone) represents horrible customer service.

photo
3

Needs to have a per-package setting of "delay before suspending on overages" so we can set 1 day or 1 hour or never or immediate

photo
3

It would be great to have this setting on a per user basis. Soft-limits would be helpful as well as hard-limits.

photo
3

+1 for soft limits :)

photo
3

Any improvement in this area would be very welcomed. Right now it is "All or Nothing". I would like to have bandwidth limits, but having my customers' sites suddenly become unavailable is not acceptable.

photo
3

That is needed for sure!

Highly appreciated...

What do you think cPanel? When can we get it?

photo
3

I would like this very much. Maybe give users the choice of either being suspended or accepting possible overage fees (I'm pretty sure this is already a feature in whmcs).


The warning could be customised to include upgrade instructions and a warning of the possible overage fees.

photo
3

+1 for soft limits or similar.

Users or admins need to be notified even if limits are not really honored. Server global or individual package level, don't care as long as it can be done.

Please, please make this happen.

photo
3

We should have both soft limits and hard limits, some hosts might want to set the hard limit to twice the softlimit. This would allow us to increase the quality of our service. We don't like having accounts stop working when they hit their limit and want customers to be warned and see in cPanel that they are over their limit without being blocked. We still want to set a hard limit to prevent an account from taking down the server

photo
2

+1 essential, actually really surprised this wasn't one of the first functions built..

photo
3

+1 There really needs to be the option for soft limits. I wanted to just give the option to charge users for going over. I disabled bandwidth account suspension, but the only notice they will get is a bill at the end of the month.

photo
4

+1 we need soft and hard bandwidth limits. WHMCS already supports this (It's even there in package creation for cPanel-type servers) but it doesn't seem to do anything because cPanel doesn't do it.

photo
2

This seems like a simple feature, a quick if then statement in the bandwidth module, to correct a terrible user experience issue. Why was suspending users accounts ever considered a good thing?

photo
1

I definitely hear you, and I know it seems like a simple adjustment. Unfortunately it hasn't been picked up by any of our feature teams yet, so I can't tell you that it will be implemented. As soon as there is an update, I will be back to let everyone know!

photo
3

It really is disappointing that such an important and almost essential feature is not even on a road map. I know there are hundreds of priorities all fighting for dev attention, but it seems other trivial things get by when this has caused us to have some very angry customers. Now we just have to manually check bandwidth or set it very high (which produces inacurate numbers in their cPanel)

photo
2

Agreed, 100% essential. #1 reason we won't use cpanel as a primary hosting platform.

When looking at some of the other features implemented over the last 4 years it is extremely disappointing to hear that this hasn't even been picked up by a feature team.

photo
2

I definitely hear the frustration, but I do want to remind folks: I'll be bringing this up at our next planning session.

Replies have been locked on this page!