Problem with DirectAdmin's IP management

[jim.thornton]

I have recently purchased WHMCS and have just setup an account to test it. Everything worked well except for the IP that was chosen. For some reason it set the new account on my main server IP which I'm using for my web hosting site. This is a problem because I have an SSL cert configured for this site.

I went into the DA panel and I looked at the IP Management and everything looked fine. It gave the following:

IP Status User(s) Nameserver Select
74.63.67.146 server 2 ns1.extra6.com
74.63.67.147 free ns2.extra6.com
74.63.67.148 shared 11
74.63.67.149 owned moneytim

I don't know why it is saying that there are 2 users on the first IP (which is my main site). When I list users, there are no users that are using this IP.

I contacted WHMCS and they said that it was Direct Admin that chooses the IP and not WHMCS.

I then went into DA and started to setup a new user and when the screen came up to enter in the information, I noticed that where you can select the IP there were 2 IP's that said shared... 146 and 148 but only 148 is suppose to be shared and 146 is suppose to me dedicated to my web hosting site.

How can I fix this??

 

[nobaloney]

The server IP# is always shared (because all admin users use it). Using it for a Secure Site is probably not a good idea.

I'm guessing that WHMCS doesn't attempt to set an IP# (I don't know enough about the DirectAdmin API to know if it can or not) but just allows DirectAdmin to use the default shared IP#, which is most likely the first.

Can DirectAdmin change the default? I don't know; you might want to ask DirectAdmin Support.

Otherwise the only way WHMCS is going to work for you is if they'll make some code changes to request a specific IP# (if the API even allows this) or if you move your Secure Site to a different IP#. To do that you may have to move it to a different user.

Jeff

 

[DirectAdmin Support]

Hello,

I contacted WHMCS and they said that it was Direct Admin that chooses the IP and not WHMCS.

Not true.

DirectAdmin is always given the IP to create an account on when the account is created. Any API used to create a User will be passing the IP to DA. So if you want WHMCS to create Users on a specific IP, WHMCS must be passing that IP to DA with the rest of the User creation info (username, password, email, package, etc). API user create is identical to normal browser user creation. The only difference is that it's CMD_API_ not CMD_, and the output is parseable, not html.

Regarding the count, DA uses a simple +1 or -1 for keeping track of how many users are on a shared IP (includeing server IP). So if it's off you can just fix it by editing the IP file itself:
/usr/local/directadmin/data/admin/ips/1.2.3.4
where 1.2.3.4 is the IP you want to fix.

John

 

[jim.thornton]

Hello,

Not true.

DirectAdmin is always given the IP to create an account on when the account is created. Any API used to create a User will be passing the IP to DA. So if you want WHMCS to create Users on a specific IP, WHMCS must be passing that IP to DA with the rest of the User creation info (username, password, email, package, etc). API user create is identical to normal browser user creation. The only difference is that it's CMD_API_ not CMD_, and the output is parseable, not html.

Regarding the count, DA uses a simple +1 or -1 for keeping track of how many users are on a shared IP (includeing server IP). So if it's off you can just fix it by editing the IP file itself:
/usr/local/directadmin/data/admin/ips/1.2.3.4
where 1.2.3.4 is the IP you want to fix.

John

Great! Thank you... Can you please tell me which file is the IP file?

 

[DirectAdmin Support]

Hello,

/usr/local/directadmin/data/admin/ips/1.2.3.4

where 1.2.3.4 is the IP you want to fix.

John