Remitur
Verified User
Note: this is an issue mainly about WHMCS; I just posted it also in WHMCS forum ( https://whmcs.community/topic/298118-whmcs-email-only-directadmin-server/ ), but I guess it may be interesting for DirectAdmin's users too, and so I post it here too.
Intro:
If I configure a "plain" DirectAdmin hosting server, as explained here: https://help.whmcs.com/m/getting_started/l/1076211-creating-your-first-directadmin-server , everything works fine.
But I want to manage in WHMCS a DirectAdmin email-only server; to do it previously (using cPanel) I used to do so:
(1) Why "Other" type? Because if you configure it as "shared hosting", WHMCS will not allow you to create two different services for the same domain, one for web hosting and the second one for email.
So, web hosting services are created in "shared hosting" product type, and email services in "other" product type.
If I try to do the same using DirectAdmin, it happens that it's not able to create a new service (and, I guess, is neither able to manage existing services, even if I did not tried it yet).
Looking in module log, I found that:
- to create a new service, WHMCS should issue a command like this:
CMD_API_ACCOUNT_USER?action=create&add=Submit&username=[...]
(and it's what WHMCS does to create a new service which is a "shared hosting type")
But to create a new "email only" service, WHMCS issues this command:
CMD_ACCOUNT_RESELLER?action=create&add=Submit&username=[...]
And the full, frantic answer I can find in WHMCS module log is:
Array
(
[<!doctype html>
<html class] => "vue-app">
<head>
<meta http-equiv
)
So, there're two issues:
1 - WHMCS issues a CMD_ACCOUNT_RESELLER instead of a CMD_API_ACCOUNT_USER
2 - the answer WHMCS can retrieve from DirectAdmin is nonsense (parsing error, I guess...)
Any idea about this strange behavior from WHMCS?
Intro:
If I configure a "plain" DirectAdmin hosting server, as explained here: https://help.whmcs.com/m/getting_started/l/1076211-creating-your-first-directadmin-server , everything works fine.
But I want to manage in WHMCS a DirectAdmin email-only server; to do it previously (using cPanel) I used to do so:
- created in WHMCS a "server group" as "email shared servers"
- created in WHMCS a new product as follows:
Product Type: Other (1)
Product Group: Email Services
Product name: myfabolousemailservice - configured pricing and "module settings" in order to connect to "email shared servers" groups
(1) Why "Other" type? Because if you configure it as "shared hosting", WHMCS will not allow you to create two different services for the same domain, one for web hosting and the second one for email.
So, web hosting services are created in "shared hosting" product type, and email services in "other" product type.
If I try to do the same using DirectAdmin, it happens that it's not able to create a new service (and, I guess, is neither able to manage existing services, even if I did not tried it yet).
Looking in module log, I found that:
- to create a new service, WHMCS should issue a command like this:
CMD_API_ACCOUNT_USER?action=create&add=Submit&username=[...]
(and it's what WHMCS does to create a new service which is a "shared hosting type")
But to create a new "email only" service, WHMCS issues this command:
CMD_ACCOUNT_RESELLER?action=create&add=Submit&username=[...]
And the full, frantic answer I can find in WHMCS module log is:
Array
(
[<!doctype html>
<html class] => "vue-app">
<head>
<meta http-equiv
)
So, there're two issues:
1 - WHMCS issues a CMD_ACCOUNT_RESELLER instead of a CMD_API_ACCOUNT_USER
2 - the answer WHMCS can retrieve from DirectAdmin is nonsense (parsing error, I guess...)
Any idea about this strange behavior from WHMCS?