Auto Setup Error

[Derek]

I am all of a sudden getting this error for my auto setup with webhosting (cpanel).

 

(Curl Error) Couldn't resolve host '' - code: 6

[BullsoftHosting - Tom]

Make sure the package has a default server assigned to it.

[Derek]

Make sure the package has a default server assigned to it.

 

Seems like it does...

[stuthemoo]

Hi,

 

I've recently got the same problem.

Have you fixed it? If so how?

 

Thanks a lot,

Stuart

[xantian]

I have the same problem after update to 4.1.1

 

14/10/2009 00:00 Module Create Failed - Service ID: 43 - Error: CURL Error: 6 - Couldn't resolve host ''

 

Standard server is selected and auto setup after reg. is on

 

WHMCS don´t select any server!

Need FIX pls Help!

[WHMCS John]

Ensure you have a default server selected in Setup > Servers. The default is denoted by an asterisk (*).

[adtastichosting]

I found myself to be having the same problem after upgrading. After fiddling and fiddling I think I figured out the problem and in light of how the upgrade works in relation to how I need it to work at least for the autocreate function for the way my hosting is setup if this is the correct configuration it makes me very displeased over the old way. (let me say for the record, there are many new features I DO like (but also some other than the one I am discussing now that I don't like)

Let me explain.

I have many servers. The servers are for different situations. For example, I have some clients with dedicated servers that we manage the server and thus they do not have WHM or Root access. However, we have it set up whereby they can click a link to come into a hidden product on WHMCS and go through the checkout process and have a domain instantly setup on the server, get the cpanel email telling them the details and they are good to go. We simply have it set up as a free hosting account and everyone is happy.

 

Under the new system in order for the autocreate to work you have to create a server group. Then you have to append it appears the default server into it or at least more than one server or it will NOT autocreate. SO now, you have to monkey around with the numbers if you want to make sure it only sets up the hosting on the ONE server you want it to set it up on. For example we tell it to set up on the least full server first and then we take the server we want it to autosetup the hosting on and say it can have 50000 accounts or some huge number versus all the others in the group and now we know for sure it will always be the least full you might call that a "workaround" but we shouldn't need to "workaround" in this area, in my opinion. Am I wrong about this?

In some cases though, this might be difficult to mess with and we have some servers that we need to keep at about the same usage numbers as say the default server but for which we have exclusive shared hosting packages for such as our PCI compliant ecommerce server which we push all of our ecommerce hosting accounts towards so now we are in a quandary about how to go about reconfiguring our autocreate.

We really should be able to design a hosting package and make it specific to only one server in our group of servers and not necessarily the default one.