How To automatically Limit Bandwidth Usage Per IP in Cpanel
Needs Feedback
How is automatically limited bandwidth based on IP?
If one IP per day, more than the amount determined by the bandwidth of website use. Their IP is blocked.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
This sounds like it would produce a very complex and confusing experience for both cPanel users and their website visitors.
cPanel users tend to get frustrated as it is when they exceed their designated bandwidth limit. This is of course understandable when it effectively causes "downtime" for their site. That's just with tracking one limit. Now they have to consider going from a situation where there's ONE limit to a situation where is theoretically trillions upon trillions of individually maintained limits? (considering both IPv4 and IPv6) each which may be breached?
How do you convey that information in a clear and concise manner? As a customer, I can't imagine wanting to have to track or troubleshoot this limitation when a visitor says they can't get to my store and I have to explain to them they visited it too many times this month.
I can't think of an effective implementation, let alone I am very nervous at the amount of support tickets this would generate for hosting providers.
I do not see this as a viable limitation to design into a system.
Perhaps with more discussion something can come from this, but I do not see a viable feature at this time with such a variable and complex limitation.
Is there demand for something like this?
It would seem like a nightmare to design hosting plans around if the limit is no longer xGB per month, but xGB per-IP which could be anywhere from dozens to tens of thousands for the average shared hosting site. If you enforce both limits (overall + per-IP) it becomes even more complex and confusing as an end user.
This sounds like it would produce a very complex and confusing experience for both cPanel users and their website visitors.
cPanel users tend to get frustrated as it is when they exceed their designated bandwidth limit. This is of course understandable when it effectively causes "downtime" for their site. That's just with tracking one limit. Now they have to consider going from a situation where there's ONE limit to a situation where is theoretically trillions upon trillions of individually maintained limits? (considering both IPv4 and IPv6) each which may be breached?
How do you convey that information in a clear and concise manner? As a customer, I can't imagine wanting to have to track or troubleshoot this limitation when a visitor says they can't get to my store and I have to explain to them they visited it too many times this month.
I can't think of an effective implementation, let alone I am very nervous at the amount of support tickets this would generate for hosting providers.
I do not see this as a viable limitation to design into a system.
Perhaps with more discussion something can come from this, but I do not see a viable feature at this time with such a variable and complex limitation.
Is there demand for something like this?
It would seem like a nightmare to design hosting plans around if the limit is no longer xGB per month, but xGB per-IP which could be anywhere from dozens to tens of thousands for the average shared hosting site. If you enforce both limits (overall + per-IP) it becomes even more complex and confusing as an end user.
This sounds like it would produce a very complex and confusing experience for both cPanel users and their website visitors.
cPanel users tend to get frustrated as it is when they exceed their designated bandwidth limit. This is of course understandable when it effectively causes "downtime" for their site. That's just with tracking one limit. Now they have to consider going from a situation where there's ONE limit to a situation where is theoretically trillions upon trillions of individually maintained limits? (considering both IPv4 and IPv6) each which may be breached?
How do you convey that information in a clear and concise manner? As a customer, I can't imagine wanting to have to track or troubleshoot this limitation when a visitor says they can't get to my store and I have to explain to them they visited it too many times this month.
I can't think of an effective implementation, let alone I am very nervous at the amount of support tickets this would generate for hosting providers.
I do not see this as a viable limitation to design into a system.
Perhaps with more discussion something can come from this, but I do not see a viable feature at this time with such a variable and complex limitation.
Is there demand for something like this?
It would seem like a nightmare to design hosting plans around if the limit is no longer xGB per month, but xGB per-IP which could be anywhere from dozens to tens of thousands for the average shared hosting site. If you enforce both limits (overall + per-IP) it becomes even more complex and confusing as an end user.
This sounds like it would produce a very complex and confusing experience for both cPanel users and their website visitors.
cPanel users tend to get frustrated as it is when they exceed their designated bandwidth limit. This is of course understandable when it effectively causes "downtime" for their site. That's just with tracking one limit. Now they have to consider going from a situation where there's ONE limit to a situation where is theoretically trillions upon trillions of individually maintained limits? (considering both IPv4 and IPv6) each which may be breached?
How do you convey that information in a clear and concise manner? As a customer, I can't imagine wanting to have to track or troubleshoot this limitation when a visitor says they can't get to my store and I have to explain to them they visited it too many times this month.
I can't think of an effective implementation, let alone I am very nervous at the amount of support tickets this would generate for hosting providers.
I do not see this as a viable limitation to design into a system.
Perhaps with more discussion something can come from this, but I do not see a viable feature at this time with such a variable and complex limitation.
Is there demand for something like this?
It would seem like a nightmare to design hosting plans around if the limit is no longer xGB per month, but xGB per-IP which could be anywhere from dozens to tens of thousands for the average shared hosting site. If you enforce both limits (overall + per-IP) it becomes even more complex and confusing as an end user.
Great idea. You could add to this an email warning for the site owner that someone is consuming a lot of bandwidth, with limits for the day, week, maybe.
Great idea. You could add to this an email warning for the site owner that someone is consuming a lot of bandwidth, with limits for the day, week, maybe.
Replies have been locked on this page!