How to connect WHMCS to my Webway reseller account

Choose the correct WHMCS module

Use the standard WHMCS module for your hosting panel:

Reseller service	WHMCS module
cPanel and WHM	cPanel
DirectAdmin	DirectAdmin

Do not use Webway's own WHMCS module for hosting accounts. That module provisions Webway Chat products only.

Before connecting the server

You need:

• A working WHMCS installation with HTTPS
• Your reseller server hostname
• Your reseller username
• An API token or login key
• At least one hosting package in WHM or DirectAdmin
• Webway's nameservers: dns1.webway.host and dns2.webway.host
• The public IP of the server running WHMCS

Use the server hostname rather than its raw IP so WHMCS can validate the SSL certificate.

Connect a cPanel and WHM reseller server

Create an API token

1. Sign in to WHM on port 2087.
2. Open Development.
3. Select Manage API Tokens.
4. Create a token for WHMCS.
5. Copy the token and store it securely.

If you can't see Manage API Tokens, open a support ticket.

Add the server in WHMCS

1. Sign in to the WHMCS administration area.
2. Open System Settings → Servers.
3. Select Add New Server.
4. Enter a descriptive name.
5. Enter the WHM server hostname.
6. Select cPanel as the module.
7. Enter the WHM reseller username.
8. Enter the API token in the API token field.
9. Enable secure connections.
10. Enter dns1.webway.host and dns2.webway.host as the nameservers.
11. Select Test Connection.
12. Save the server.

Connect a DirectAdmin reseller server

Create a login key

Where supported, use a restricted DirectAdmin login key instead of storing the main reseller password.

1. Sign in to DirectAdmin on port 2222.
2. Open Advanced Features → Login Keys.
3. Create a key for WHMCS.
4. Restrict it to the required reseller actions.
5. Restrict its source IP to the WHMCS server where practical.
6. Copy and store the key securely.

Add the server in WHMCS

1. Open the WHMCS server settings.
2. Select Add New Server.
3. Enter the DirectAdmin server hostname.
4. Select DirectAdmin as the module.
5. Enter port 2222 if requested.
6. Enter the reseller username.
7. Enter the login key in the password field.
8. Enable secure connections.
9. Add Webway's nameservers.
10. Test and save the connection.

Add the server to a group

Create a server group if you have more than one server or want WHMCS to choose where new accounts are provisioned. Review the fill method carefully: it controls how WHMCS distributes new accounts.

Link a WHMCS product to a hosting package

1. Open Products/Services in WHMCS.
2. Create or edit the hosting product.
3. Open Module Settings.
4. Select the cPanel or DirectAdmin module.
5. Choose the server group.
6. Enter or select the exact package name.
7. Choose when the account should be created.
8. Save the product.

WHM package names contain the reseller username as a prefix. The WHMCS value must match the complete package name.

Test provisioning safely

Create a test order using a domain reserved for testing. Confirm that WHMCS can create the account, apply the correct package, set the username and password, suspend and unsuspend it, and terminate it.

Termination deletes hosting data. Use only a disposable test account.

Common connection errors

Error	What to check
Connection failed	Hostname, port, HTTPS and firewall access
Authentication failed	Username, token, login key and permissions
SSL error	Use the hostname covered by the server certificate
Package not found	Complete package name and reseller prefix
Account limit exceeded	Reseller disk, bandwidth or account allocation
Username already exists	Existing account or conflicting generated username
Domain already exists	The domain is already configured on the server
Timeout	Network access or a firewall block

Repeated failed API logins can cause the Webway firewall to block the WHMCS server's public IP. Customers cannot view or remove firewall blocks.

Still stuck?

Open a support ticket and include:

• Whether you use WHM or DirectAdmin
• Your reseller username
• The server hostname
• The WHMCS module selected
• Your WHMCS server's public IP
• The exact test-connection or module error
• The package name being used
• The date and approximate time of the failed request
• Relevant WHMCS module-log entries with secrets removed