xboss Posted February 23, 2012 Share Posted February 23, 2012 Hi guys! I have the whmcs setup on my domain I have a ded IP for SSL SSL works fine. and whmcs switches to it no problem The problem / question I have: When I use the enom module to run tests I supplied my IP and it didnt work. Said IP not added to system etc. and it shows the IP that whmcs is using and it's my shared hosting IP! So I add the shared hosting IP and boom it works. I have checked in WHM and my host site domain with the ssl is listed as the only domain using that IP and it uses no other IP. I do have a nameserver on that IP but I was told that a ssl would work with the IP being used as a nameserver and it does. Anyway, if I run an IP check on the website it does in fact show my dedicated IP but enom is only recognizing the shared hosting IP. Any ideas? 0 Quote Link to comment Share on other sites More sharing options...
Daniel Posted February 23, 2012 Share Posted February 23, 2012 It's normal, it would always use the servers main IP address regardless of dedicated IP status (at least on cPanel). 0 Quote Link to comment Share on other sites More sharing options...
xboss Posted February 23, 2012 Author Share Posted February 23, 2012 Tx Daniel, That brings a problem I think. It means anybody on my shared host is whitlisted to interact with the enom api right? Is it a terrible idea to have my hosting site hosted right alongside the other shared accounts? 0 Quote Link to comment Share on other sites More sharing options...
tripler Posted February 23, 2012 Share Posted February 23, 2012 The way I think it usualy works: Your shared ip is for you. The dedicated ip is where your clients sit. >>That brings a problem I think. It means anybody on my shared host is whitlisted to interact with the enom api right? Not unless they know your enom username and password 0 Quote Link to comment Share on other sites More sharing options...
laszlof Posted February 23, 2012 Share Posted February 23, 2012 Unfortunately there is not an easy way around it. The system is going to use the server's primary IP address for outgoing communication. The only way that I can think of to fix that is to setup static routes or use a source IP in the curl call to the registrar: curl_setopt($ch, CURLOPT_INTERFACE, '1.2.3.4'); Unfortunately thats not really possible with an encoded module. 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.