Tyler Jacobson Posted May 23, 2011 Share Posted May 23, 2011 Hey there - Since I upgraded to 4.5.1 my clients domains already registered with Resellerclub are getting this error: CURL Error: 7 - couldn't connect to host When you order a domain name, it appears to work just fine. It's a problem that appears to be exclusive to domains once they are registered. Has anyone else experienced this or have any recommendations for resolving this? 0 Quote Link to comment Share on other sites More sharing options...
Tyler Jacobson Posted May 23, 2011 Author Share Posted May 23, 2011 SCRATCH THAT: Actually, I can't register domains either. It's no longer connecting to resellerclub 0 Quote Link to comment Share on other sites More sharing options...
Tyler Jacobson Posted May 23, 2011 Author Share Posted May 23, 2011 UPDATE: Enom appears to work just fine. This is resellerclub only from what I can tell. 0 Quote Link to comment Share on other sites More sharing options...
papa_face Posted May 23, 2011 Share Posted May 23, 2011 You need to add your server IPs to the API section in the reseller club control panel. 0 Quote Link to comment Share on other sites More sharing options...
Tyler Jacobson Posted May 23, 2011 Author Share Posted May 23, 2011 Thanks for the reply. We gave the a shot but we are still getting the error. Any other suggestions? 0 Quote Link to comment Share on other sites More sharing options...
Daniel Posted May 23, 2011 Share Posted May 23, 2011 Are you sure you've added the main server IP address? It's not necessarily the shared IP. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS CEO Matt Posted May 23, 2011 WHMCS CEO Share Posted May 23, 2011 Please check the documentation first: http://docs.whmcs.com/ResellerClub#CURL_Error:_7_-_couldn.27t_connect_to_host 0 Quote Link to comment Share on other sites More sharing options...
sleepybaby Posted May 24, 2011 Share Posted May 24, 2011 i have added the main server IP address。 also showing the error 0 Quote Link to comment Share on other sites More sharing options...
Tyler Jacobson Posted May 24, 2011 Author Share Posted May 24, 2011 Yes, I've added the server's IP. I have an open ticket with Resellerclub based on Matt's link above, but so far I haven't heard back. 0 Quote Link to comment Share on other sites More sharing options...
Tyler Jacobson Posted May 26, 2011 Author Share Posted May 26, 2011 We got this up and running. Matt's instruction was correct. We had a problem finding which IP was reporting when we connected to ResellerClub. The way to easily discover which IP your server is reporting is to run the following shell command (per resellerclub): lynx --dump http://www.whatismyip.com/ | grep -o '[0-9].*\.[0-9].*\.[0-9].*\.[0-9].*' -m1 Hope this helps anyone having the same troubles. 0 Quote Link to comment Share on other sites More sharing options...
hostleet Posted May 26, 2011 Share Posted May 26, 2011 If you use a dedicated IP for your website (whmcs), you need to NOT use this IP.. Instead use the server's main shared IP as this is what RC sees. Also, you can add multiple IPs, but make sure the first one is your server's main shared IP. 0 Quote Link to comment Share on other sites More sharing options...
xlibris Posted May 26, 2011 Share Posted May 26, 2011 (edited) to me happen the same im using the same ip to verify my license here at whmcs, and still dont works!! and is working with enom ok im gonna try what hosteet says... Edited May 26, 2011 by xlibris 0 Quote Link to comment Share on other sites More sharing options...
xlibris Posted May 26, 2011 Share Posted May 26, 2011 Now is working Hosteet was right, the main shared ip did the trick.! thanks 0 Quote Link to comment Share on other sites More sharing options...
GGWH-James Posted May 27, 2011 Share Posted May 27, 2011 If you use a dedicated IP for your website (whmcs), you need to NOT use this IP.. Instead use the server's main shared IP as this is what RC sees. Also, you can add multiple IPs, but make sure the first one is your server's main shared IP. This depends upon how the server is configured. 0 Quote Link to comment Share on other sites More sharing options...
hostleet Posted September 17, 2011 Share Posted September 17, 2011 Now is working Hosteet was right, the main shared ip did the trick.! thanks Glad to hear that, and you're welcome! 0 Quote Link to comment Share on other sites More sharing options...
knipper Posted November 2, 2011 Share Posted November 2, 2011 Oddly, a few days ago after I upgraded WHMCS for the security release I started getting this Curl 7 error that night, the first time the cron ran. Per the wiki I added both my main shared server IP, as well as my dedicated IP in the resellerclub API area. After I placed the shared IP first, I get a different error... it just says "an unexpected error has occurred". If I remove the shared IP... it goes back to "Curl Error 7". Any tips? 0 Quote Link to comment Share on other sites More sharing options...
knipper Posted November 3, 2011 Share Posted November 3, 2011 After some investigation and looking around here is what corrected it for me. All these corrections were based on the ResellerClub FAQ database or Wiki. First I double checked IP addresses to ensure they were correct within the ResellerClub API ... they were. Then I made sure both ports 2086 & 2087 were open. Still got the errors... THEN, I checked the domain registrar info within WHMCS.... guess what? It must have been overwritten during the upgrade process, as the User ID was missing. (Oddly the password appeared to be intact.) I edited the info for my ResellerClub Domain Registrar.... Ran the cron job and Woo Hoo!! No errors! Hope this info helps! 0 Quote Link to comment Share on other sites More sharing options...
BobC Posted November 4, 2011 Share Posted November 4, 2011 I am also receiving this error when running the Domain Syncronisation Cron for NetEarthOne. The odd thing is, it seems to happen every other day and, when it does occur, connection fails for only half the domains. Other days, there are no problems. Some of the domains are on shared IPs and some not, regardless of whether or not the connection succeeds. What would cause this intermittent problem? 0 Quote Link to comment Share on other sites More sharing options...
brianr Posted November 5, 2011 Share Posted November 5, 2011 I'm also having this problem... Sometimes the 1st half of a sync will be fine, and the bottom half full of error 7 messages, other times, no errors, or all errors... Using the Stargate module here.... 0 Quote Link to comment Share on other sites More sharing options...
Sunzila Posted November 7, 2011 Share Posted November 7, 2011 (edited) After updating from 4.4.2 to 4.5.2 I have the same problem. Edited November 7, 2011 by Sunzila 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Support Manager WHMCS John Posted November 7, 2011 WHMCS Support Manager Share Posted November 7, 2011 If you're seeing some successes please try scheduling the cron a different time of the day in case the ResellerClub API is busy, and ensure it's only scheduled to run once per week in case you're being blocked by ResellerClub for too many API requests. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.