The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

How to limit reseller features (mysql, etc)

Discussion in 'General Discussion' started by Sunrex, May 8, 2010.

  1. Sunrex

    Sunrex Member

    Joined:
    Apr 28, 2010
    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    1
    I don't feel this warrants a support ticket so I'll post it here;

    If the reseller owns their own account (not the reseller account, just the shared account), how do I limit the number of MySQL databases they can create, etc?.

    Thanks!.
     
  2. Spiral

    Spiral BANNED

    Joined:
    Jun 24, 2005
    Messages:
    2,023
    Likes Received:
    7
    Trophy Points:
    0
    Don't allow the reseller to create their own account packages ....

    Instead create pre-defined packages for them they are allowed to select from when setting up new hosting accounts.

    You can also create custom plans for specific resellers by prefixing the package with the reseller's username (IE: username_package)
     
  3. Sunrex

    Sunrex Member

    Joined:
    Apr 28, 2010
    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    1
    I'm sorry but I don't see how what you said answers my question - on direct admin the administrator has the ability to limit reseller features, basically as the client uses a mysql database then the reseller uses it and it counts towards their feature quota.

    Is this not possible with cpanel?.
     
  4. Spiral

    Spiral BANNED

    Joined:
    Jun 24, 2005
    Messages:
    2,023
    Likes Received:
    7
    Trophy Points:
    0
    You are not really understanding the system differences it sounds like ...

    Under Cpanel, resold accounts have nothing to do with the reseller's own account and has no bearing on the reseller's own personal limits.

    In other systems, the reseller is often sharing their own resources so for example they may have 5 GB on their own hosting account and can split that up with different hosting accounts. This is no different than a regular typical Cpanel account under Cpanel and is not how a reseller account works.

    Under Cpanel, a reseller has their OWN acccount with their OWN limits which has absolutely nothing to do with the amount of accounts they can setup or what features is on those accounts as that is all independent of their own personal web site account.

    This way, a reseller might have a small site for themselves only using what they actually need yet at the same time might have hundreds of clients resold by them each on their own accounts.

    A reseller OWNS the resold accounts but those accounts are distinctly separate from the reseller's own account and have no bearing on the reseller's own web hosting account.

    I suppose another way to put that is that the reseller's own web site and limits are separate and distinct from the reseller's reselling account and the only thing those two have in common is just the login name which which when used in WHM is the reseller account and when used in Cpanel is the reseller's own web hosting account.

    You can have one set of limits for the reseller's own account and another set or limits for what accounts they can create limited by the number of accounts, account types, or by the storage space and bandwidth usage.

    Now for individual features like MySQL databases and such, these are set at the plan (package) level and you can limit a reseller by simply predefining the plans they are permitted to setup and don't give them the ability to override individual settings which is basically what I told you in the previous post.

    Check out the Cpanel documentation and also "Reseller Center" in WHM
     
  5. Sunrex

    Sunrex Member

    Joined:
    Apr 28, 2010
    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    1
    That's a bad system then =/. What if I don't want to restrict what packages the reseller can setup and just limit the total overall features the reseller can create max in general, without editing their own created packages?.
     
  6. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    That's a bit contradictory. By letting a reseller own their own account, they can change any limit on their shared account.

    If you want to limit how many MySQL databases they can create etc. for their shared account (not necessarily their child accounts), make sure you don't let them own their own account.
     
  7. Sunrex

    Sunrex Member

    Joined:
    Apr 28, 2010
    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    1
    I was talking about their clients, not the resellers shared account ;). Is there no way to limit it?.
     
  8. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    To limit those resources, create packages for your reseller and limit the reseller to only issuing accounts from those packages. Also, limit the number of accounts per package.

    Note, this limitation will be negated if you grant the reseller any "Super Privs."
     
  9. Sunrex

    Sunrex Member

    Joined:
    Apr 28, 2010
    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    1
    Thus, my dilemma. I do not want to restrict the amount of accounts they can create or what their packages contain. I want a global reseller feature limit so if the clients go over the resellers total quota they can't create anymore as the reseller is maxed.

    DA has this feature, which is why I am unsure why Cpanel doesn't have it. I'm not trying to turn this into a cpanel vs DA argument, I am just wondering why such a important feature was overlooked.
     
  10. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    Well let's talk about how this should be implemented. Should the limits apply to provisioning, meaning the reseller is incapable of provisioning more MySQL accounts than they are allowed? Alternatively, should the limits apply to actual databases created instead, a process some people call overselling?
     
  11. Sunrex

    Sunrex Member

    Joined:
    Apr 28, 2010
    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    1
    Both options would be nice.
     
  12. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    In the overselling scenario, let's say there's user A and user B under a reseller. User B creates a database, putting the reseller over their overselling quota. Should this work like existing overselling limits (enforced only when a reseller tries to create a new account)? If not, what do you recommend? Should User A be penalized by means of account suspension because, unknown to User A, User B created a database?
     
  13. furquan

    furquan Well-Known Member

    Joined:
    Jul 27, 2002
    Messages:
    425
    Likes Received:
    0
    Trophy Points:
    16
    restrict mysql privileges to reseller !!!

    Guys.. I have a similar situation, BUT with a twist.

    I have resellers on my server and i need to restrict privileges on his account, namely MYSQL.

    How can i let the user create package but NOT GIVE mysql OR USE mysql to his clients in turn.

    SIMPLY NO MYSQL SUPPORT FOR THE RESELLER, If he demands we should be able to enable it later.

    Some assistance please ???
     
    #13 furquan, Aug 3, 2010
    Last edited: Aug 3, 2010
Loading...

Share This Page