kirchenbauer Posted August 31, 2005 Share Posted August 31, 2005 I am having problems setting up my Authorize.net and I suspect that I have the wrong cURL path. My host (webhost4life) gave me a path c:\\PHP\extensions which has a file in it called php_curl.dll. This path is not working, and I have read that 1) The "curl" file needs to be in the path 2) The path isn't in PHP. I have not been able to get the answer from webhost4life, and I have been working on this for nearly a week now. These are the settings: HTTP Server: Microsoft-IIS/6.0 PHP Version: 4.3.11-dev (Zend: 1.3.0) CURL support enabled CURL Information libcurl/7.11.2 OpenSSL/0.9.7c zlib/1.1.4 Does anyone else have cURL in the IIS environment? What path are you using for Authorize.net? Thank you! Sherry Link to comment Share on other sites More sharing options...
♥Vger Posted August 31, 2005 Share Posted August 31, 2005 In your osC admin panel. under Tools --> Server Info run a page search for cURL and it should locate all of the entries on that page for cURL and one of them will give the pathway. Vger Link to comment Share on other sites More sharing options...
kirchenbauer Posted August 31, 2005 Author Share Posted August 31, 2005 Thank you for the reply. I went to Server Info and did a search (Edit, Find from top menu), but the only reference to cURL on the page was here: Is there another way that I should be searching? Thank you, Sherry Link to comment Share on other sites More sharing options...
♥Vger Posted September 1, 2005 Share Posted September 1, 2005 Sorry, think I made an error there. I've been looking through my system and on one server I find cURL is at usr/bin/curl - but I think you're probably going to have to look through all your folders to find out where it is on your server. But the bottom line is that cURL should work without you having to specify a particular path to it, as it's compiled on the server. Your host should not be using this version of PHP "PHP Version: 4.3.11-dev". The 'dev' version was full of bugs and was superceeded many months ago by a stable 4.3.11 No hosting company should have installed a development version of php on customer websites - but I know that some did. Vger Link to comment Share on other sites More sharing options...
kirchenbauer Posted September 1, 2005 Author Share Posted September 1, 2005 I will need to check with them about the "Dev" version. We are actually on a Windows environment, so our cURL is not compiled. From what I read in Austin's Authorize.net contributions, if your server is on a Windows environment, then you need to have a path that looks like this: c:/curl/curl Austin also wrote in the contribution that the "curl" file should be in the path. My host has given me the path c:/PHP/extension without the "curl" file in it. There is a file called "php_curl.dll" in the directory c:/PHP/extension. Of course, Authorize.net isnt' working. I am getting the "Unable to connect. Check your cURL and server settings" error. I am just assuming that my path is wrong because Austin's documentation says that there should be a "curl" file at the end of the path. I have tried c:/PHP/extension, c:/PHP/extension/php_curl.dll, c:/PHP/extension/curl, c:/windows/system32/curl, c:/curl/curl, c:/curl None of them are working. I guess it is possible that the c:/PHP/extension is right, but then I need to figure out what the real problem is. Thanks again for your assistance. I checked out your website. It's very nice. Sherry Link to comment Share on other sites More sharing options...
kirchenbauer Posted September 1, 2005 Author Share Posted September 1, 2005 I wanted to post a follow up to this because the problem has been resolved. If anyone else happens to have this same problem, my host changed the setting to "Compiled", even though it is on a Windows server. From what I have read, cURL on a Windows server should set it to "Not Compiled", but I guess this isn't the case 100% of the time. Thank you to everyone who read this post and tried to help. Sherry Link to comment Share on other sites More sharing options...
JONGEB Posted June 5, 2009 Share Posted June 5, 2009 I wanted to post a follow up to this because the problem has been resolved. If anyone else happens to have this same problem, my host changed the setting to "Compiled", even though it is on a Windows server. From what I have read, cURL on a Windows server should set it to "Not Compiled", but I guess this isn't the case 100% of the time. Thank you to everyone who read this post and tried to help. Sherry Sherry, I know this was a long time ago but I too am using webhost4life and they have given me the same info you posted, which is not helping me connect to authorize.net via the "AIM" module. You mentioned that webhost4life had to change the setting for curl to "compiled" which I have put in a request for them to do but, I was wondering what you ended up using a proxy path once cURL was set to "compiled"? Did you use "none" or was there a path that you used? Thanks for any help, Jon Link to comment Share on other sites More sharing options...
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.