Bandwidth exceeder mechanism : Features lacking...

[mpierre]

I have a BIG question...

I have lots of problems with customers busting their bandwidth,
and frankly, I DO NOT LIKE AT ALL the way CPanel deals with it.
1 - I get notifications that the Bandwidth exceeds 80%, not I don't get an e-mail saying it is suspended !
2 - The only way to unsuspend him is either

A) unsuspend everyone ( via "Unsuspent ALL bandwidth exeeder" ) or
B) increase his limit.

The Limit is then increased permanently, so I have to remember to reduce him next month if he paid for only 1 month...

Plus, sometimes I will simply want to suspend a client on the 29th who has 1 MB over his limit. It is not worth it to try to bill him for only such a small amount : he will unsuspend on the 1st anyway.

3 - in the bandwidth usage page, the actual limit isn't even listed !!!

4 - The account suspended for bandwidth abuse are not even listed in the suspended accounts page !

I CANNOT KNOW AN ACCOUNT IS SUSPENDED UNTIL THE CLIENT WARNS ME !!!

 

[hormigo]

2 - The only way to unsuspend him is either

A) unsuspend everyone ( via "Unsuspent ALL bandwidth exeeder" )

You can unsuspend single account

see these features

Suspend or Unsuspend an Account

List Suspended Accounts

 

[mpierre]

Nope...

I tried...

In list Suspended accounts, it doesn't list bandwidth exceeders, only accounts manually suspended.

And unsuspending a bandwidth exceeder doesn't work.

 

[hormigo]

send an e-mail to Nick (nickATdarkorb.net)

 

[mpierre]

done...

I'll post here replies if I get any, for the benefit of other readers of the board.

 

[Website Rob]

This is definitely an area where improvements can be made. If WHM can send notice of 80% Data Transfer usage, it would make sense that it can also send a notice when account has been Suspended for overage. The rest just follows from there.

 

[brandonk]

bump...

We need features here!

 

[Website Rob]

If I understand correctly, if a Client has not inputted an eMail address for the "Contact Email", they will not receive it.

 

[GordonH]

Hello

We also need a fix to the bandwidth abuse problem:

Users on shared IP's can link to files using xx.xx.xx.xx/~username
and the bandwidth is recirded in access_log which does not count towards their limit.

We have had serious problems with people using huge amounts of bandwidth this way.
I have to copy access_log to a web readable folder and manually go through it every few days to check up on this.
We have lots of servers and its a real pain.

Oh, and please nobody suggest using unique IP's for all sites because we are bound by RIPE regulations on IP usage.

Gordon

 

[silversurfer]

Cpanel does have a solution to this. Go to your http.conf and enable the mod_bwlimited and the users will no longer be able to access http://www.yourdomain.com/~username.

Do note however this is with some compromise:

1. You can no longer give them a temp directory to work with while the DNS resolves

2. You can no longer offer sharedssl.

 

[Website Rob]

This is an Apache situation, not Cpanel. Therefore, Cpanel has nothing to do with this.

If one does not want to download/install "mod_bwlimited" then just make a change in the httpd.conf file.

Maximum protection could be achieved by disabling “UserDir” directive

Find this in /usr/local/apache/conf/httpd.conf

<IfModule mod_userdir.c>
UserDir public_html
</IfModule>

And replace UserDir with this one:

UserDir disabled

But, as already mentioned, if you disable UserDir then /~username/ can not be used on that server and Shared SSL can no longer be provided.

You can also enable or disable UserDir on a per user basis.

UserDir disabled

no one can use /~user/ on the server.

If you use:

UserDir disabled
UserDir enabled user1 user2 user3

Then except for user1, 2 & 3, the others can’t use /~username/ on your server.

 

[jcsolutions]

Originally posted by silversurfer
Cpanel does have a solution to this. Go to your http.conf and enable the mod_bwlimited and the users will no longer be able to access http://www.yourdomain.com/~username.

Do note however this is with some compromise:

1. You can no longer give them a temp directory to work with while the DNS resolves
2. You can no longer offer sharedssl.

Actually, that's not quite true. Now, I'm definately no expert at this, but with the help of "itf", I have my server setup with mod_bwlimited, my users can access their site via http://ServerFQDN/~username (which I can disable at any time for everyone or individual users), and I can offer shared SSL.

If I'm not mistaken, more info on this can be found at the following post: http://forums.cpanel.net/showthread.php?s=&postid=13057#post13057

Hope this helps.

 

[Website Rob]

Yeah, that's probably the link I got my info from -- I have the info saved on file so didn't have to hunt for back-links.

Using the method I described above and without having 'mod_bwlimited' installed, I have effectively shutdown any use of the tilde for access.