|
|
 |
|
|
| WHMreseller Frequently Asked Questions: |
- Can WHMreseller be used with Plesk/Ensim?
- Can WHMreseller be used with other WHM Skins?
- How exactly does WHMreseller work?
- Is there any risk of things getting out of control?
- What about FreeBSD and other Unix OS?
- How are Resellers Resources allocated/shared?
- How can you customise New Sub Reseller WHM's priviledges?
- What about overselling?
- What if I don't use the "Resource Limit" method for my WHM Accounts?
- Why can't I get Migrations to work?
- How do you install cURL for WHMreseller?
|
|
|
|
1. Can WHMreseller be used with Plesk/Ensim?
No, WHMreseller is only compatible with WHM/Cpanel
2. Can WHMreseller be used with other WHM Skins?
Yes, however WHMreseller is primarily designed to blend in with the X-Skin's appearance.
3. How exactly does WHMreseller work?
WHMreseller works by adding its own layer of management and record keeping above the normal WHM reseller functions. This allows it to create, terminate, modify and suspend all Sub Reseller Accounts it creates as well as keep track of changes. It is fully secure and operates as an Addon Module of WHM.
4. Is there any risk of things getting out of control?
No, all resource usage is monitored and the limits you set cannot be breached. With 2 limiting methods WHMreseller is both flexible and safe. Also since there is only one level of Reselling, the Sub Resellers that your Master Resellers create CANNOT themselves Resell WHM.
5. What about FreeBSD and other Unix OS?
WHMreseller has not yet been fully tested on any other Unix systems besides Redhat Linux 9 and Redhat Enterprise. However its believed there should be no problems, as long as you have WHM/Cpanel properly installed.
6. How are Resellers Resources allocated/shared?
The way it works is WHMreseller keeps track of the Master Reseller's original allocated resources. For example - say a customer purchases a Reseller Account with 4 GB's Allocated Disk Space and 80 GB's Bandwidth. Under their WHMreseller Panel they would then have a total allocation of 4 GB's Space and 80 GB's Bandwidth and one WHM account (the original) that would be using all these resources. They would then need to reduce this original WHM accounts resources, say to 1 GB Space and 20 GB Bandwidth and they would then have 3 GB Space and 60 GB Bandwidth free to create other WHM accounts - Sub Resellers.
7. How can you customise New Sub Reseller WHM's priviledges?
The settings area of WHMreseller allows 2 Priviledge templates that enforce priviledges on all created Sub Reseller WHM accounts. So whatever features/limits are set in these 2 templates, all subsequent Sub Reseller WHM control panels will be setup with these features/limits.
8. What about overselling?
WHMreseller does not affect normal WHM overselling, you can still allow overselling or if you want, disable it. Note however that a Master Reseller cannot oversell Sub Reseller WHM accounts. What does this mean? It means that while all WHM accounts can have overselling of cpanel accounts Master Reseller cannot oversell WHM accounts. This is to protect the server against runaway resource usage.
9. What if I don't use the "Resource Limit" method for my WHM Accounts?
This is fine, WHMreseller V1.3 onwards permits both resource limiting and number limiting methods.
10. Why can't I get Migrations to work?
Migrations require cURL (with SSL support) and outbound ports 2083 & 2087 to be open. You can test if you have cURL installed (with SSL support) by executing the following command from your server shell
curl https://deasoft.com
If this returns an error then try command
curl -k https://deasoft.com
If it still fails then you'll need to install cURL, see FAQ 11 below for installation instructions. Migrations also require that OUTBOUND ports 2083 & 2087 be left open. Make sure your Firewall keeps these ports open.
11. How do you install cURL for WHMreseller?
Upload to your servers /usr/src/ directory the latest release in source format (".tar.gz") from http://curl.haxx.se/download.html. Execute the following commands (Note: check first yourself that the latest release doesn't have a different method of installation. Also replace x's below with latest release numbers):
cd /usr/src
wget http://curl.haxx.se/download/curl-7.xx.x.tar.gz
gunzip curl-7.xx.x.tar.gz
tar -xvf curl-7.xx.x.tar
cd curl-7.xx.x
./configure --with-ssl
make
make install
That's It!
|
| |
|
