PsyberMind Posted April 14, 2010 Share Posted April 14, 2010 Alright, I'm about fully stumped right now. Everything is as it should 2068/7 is open both in and out, Shell_Exec() is enabled, yet I'm still getting CURL timeouts on WHM Account Creation. What else could the problem be? 0 Quote Link to comment Share on other sites More sharing options...
bear Posted April 14, 2010 Share Posted April 14, 2010 Alright, I'm about fully stumped right now. Everything is as it should 2068/7 is open both in and out, Shell_Exec() is enabled, yet I'm still getting CURL timeouts on WHM Account Creation. It's 2086 and 2087, but I'm guessing that's a typo. What is the error message you receive, if any? 0 Quote Link to comment Share on other sites More sharing options...
PsyberMind Posted April 14, 2010 Author Share Posted April 14, 2010 The usual: 13/04/2010 00:19 Module Create Failed - Service ID: 12 - Error: (Curl Error) connect() timed out! - code: 28 administrator 0 Quote Link to comment Share on other sites More sharing options...
bear Posted April 14, 2010 Share Posted April 14, 2010 One possible solution: http://forum.whmcs.com/showpost.php?p=145023&postcount=7 You might also try totally disabling the firewall for a minute while you try again. Did you restart the firewall after adding the additional ports (which are correct, and this is cpanel, right?)? 0 Quote Link to comment Share on other sites More sharing options...
PsyberMind Posted April 14, 2010 Author Share Posted April 14, 2010 I looked at that solution, and tried it both ways, with IP and with HostName.. neither worked. As far as the firewall goes, yes.. when we isntalled cPanel/WHM the firewall was restarted after the ports were opened.. When my partner comes back online, I'll try disabling the firewall and see what happens 0 Quote Link to comment Share on other sites More sharing options...
bear Posted April 14, 2010 Share Posted April 14, 2010 In the meantime, you could just add the connecting server's IP into the allow list (assuming CSF firewall), and remove that from the equation without opening up the whole server. You might also watch both sides of the connection attempt via shell if you have it on both, or at least on the gaining server to see if the sending server's IP shows up at all during the attempt. Log files on each server may hold info, too. 0 Quote Link to comment Share on other sites More sharing options...
PsyberMind Posted April 20, 2010 Author Share Posted April 20, 2010 Ok, well.. now I'm lost.. We've disabled firewall, added the IP to the CSF allow list, and I'm even on another IP address, and it's STILL Not working 0 Quote Link to comment Share on other sites More sharing options...
bear Posted April 20, 2010 Share Posted April 20, 2010 Ok, well.. now I'm lost.. We've disabled firewall, added the IP to the CSF allow list, and I'm even on another IP address, and it's STILL Not working The IP you added is the server that's trying to connect, right? I'd suggest you consider asking WHMCS for help via ticket. Providing them with more info and possibly allowing them to investigate should help more than me guessing with no access to try things. 0 Quote Link to comment Share on other sites More sharing options...
PsyberMind Posted April 20, 2010 Author Share Posted April 20, 2010 (edited) Correct. In this instance, WHMCS and WHM are on the same server.. I'm going to dig through the Apache logs, and open a support ticket The funny thing is, I can connect to my remote WHM with no problems Edited April 20, 2010 by PsyberMind 0 Quote Link to comment Share on other sites More sharing options...
PsyberMind Posted April 24, 2010 Author Share Posted April 24, 2010 Problem resolved.. I had forgotton to add the server to the server group, so WHMCS had no idea what server to use.. 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.