CURL doesn't seem to work.

tmsrepub

Registered
Oct 26, 2007
2
0
51
All the curl scripts were working before I rebuilt my apache and php build using easyapache3 to install SOAP. When I finished with the update CURL doesn't work anymore. Even though in the phpinfo curl was enabled.

Did I miss anything?
 

romulob

Active Member
PartnerNOC
Apr 29, 2008
38
0
56
Maybe a corrupted recompilation. Try recompiling it once more.
 
Last edited:

Doctor

Well-Known Member
Apr 26, 2003
180
0
166
Recompiled multiple times using EasyApache but failed. Basic cURL connection still fails.
 

jols

Well-Known Member
Mar 13, 2004
1,110
3
168
Did this every get resolved? We have some requests for SOAP, but we also have many cURL users. So I'm wondering...
 

BottersInc

Registered
Sep 11, 2008
3
0
51
I have this problem too. Did this get resolved?

When I go to recompile I get this error:

The last time Cpanel::Easy::PHP5::CurlSSL was run; step returned 0.

That just caused Cpanel::Easy::PHP5::CurlSSL to be skipped.

The message it gave was:
Command failed in '/home/cpeasyapache/src/curl-7.19.0': './configure --prefix=/opt/curlssl/ --without-libssh2 --with-ssl=/usr/local'

You might want to take that into consideration when choosing options and troubleshooting.

The log for that build is here: /usr/local/cpanel/logs/easy/apache/build.1221111310


When I go to compile the error says the dryrun failed because it could not find the openssl lib directory.

So I went back and recompiled with openssl first, then I recompiled the curlSSL and still get same error.




configure: error: OpenSSL libs and/or directories were not found where specified!
dryrun test 'Find Curl SSL path for PHP 5' did not return true

!! Dry run failed for 'Cpanel::Easy::PHP5::CurlSSL' skipping option !!
 
Last edited:

cPanelDavidG

Technical Product Specialist
Nov 29, 2006
11,216
11
313
Houston, TX
cPanel Access Level
Root Administrator
I have this problem too. Did this get resolved?

When I go to recompile I get this error:

The last time Cpanel::Easy::PHP5::CurlSSL was run; step returned 0.

That just caused Cpanel::Easy::PHP5::CurlSSL to be skipped.

The message it gave was:
Command failed in '/home/cpeasyapache/src/curl-7.19.0': './configure --prefix=/opt/curlssl/ --without-libssh2 --with-ssl=/usr/local'

You might want to take that into consideration when choosing options and troubleshooting.

The log for that build is here: /usr/local/cpanel/logs/easy/apache/build.1221111310


When I go to compile the error says the dryrun failed because it could not find the openssl lib directory.

So I went back and recompiled with openssl first, then I recompiled the curlSSL and still get same error.




configure: error: OpenSSL libs and/or directories were not found where specified!
dryrun test 'Find Curl SSL path for PHP 5' did not return true

!! Dry run failed for 'Cpanel::Easy::PHP5::CurlSSL' skipping option !!
I recommend submitting a support ticket regarding this issues so our technical analysts can render assistance.
 

jols

Well-Known Member
Mar 13, 2004
1,110
3
168
I have this problem too. Did this get resolved?

When I go to recompile I get this error:

The last time Cpanel::Easy::PHP5::CurlSSL was run; step returned 0.

That just caused Cpanel::Easy::PHP5::CurlSSL to be skipped.

The message it gave was:
Command failed in '/home/cpeasyapache/src/curl-7.19.0': './configure --prefix=/opt/curlssl/ --without-libssh2 --with-ssl=/usr/local'

You might want to take that into consideration when choosing options and troubleshooting.

The log for that build is here: /usr/local/cpanel/logs/easy/apache/build.1221111310


When I go to compile the error says the dryrun failed because it could not find the openssl lib directory.

So I went back and recompiled with openssl first, then I recompiled the curlSSL and still get same error.




configure: error: OpenSSL libs and/or directories were not found where specified!
dryrun test 'Find Curl SSL path for PHP 5' did not return true

!! Dry run failed for 'Cpanel::Easy::PHP5::CurlSSL' skipping option !!
Does this only occur when you also select SOAP in Easy Apache?
 

BottersInc

Registered
Sep 11, 2008
3
0
51
I cant submit a support ticket because this is a VPS server and I am not the hosting company. They keep telling me for two days they were going to talk to you but they never do.

Amerihosting has really gone downhill since I joined with them about two years ago. I submitted an emergency thicket about this because no one was helping me and I got a nice kiss off email back how they were going to charge me for submitting to their [email protected] email address.


My reply well if you can get it fixed I dont mind paying so go ahead and charge me!

I went to another company and order a server and they told me they would have it up in an hour. That was 6 hours ago and their excuse was cpanel has problems.

I dont know where to start when it come to believing people with hosting anymore. My last three days have been worth less I have lost thousands in sales and the more I talk to people the more I feel like someone is lying.

So sick of the internet based support!
 

deathy

Active Member
Apr 11, 2003
31
0
156
i now have this same problem, my site wont take payments until this is fixed grrr.
 

jols

Well-Known Member
Mar 13, 2004
1,110
3
168
i now have this same problem, my site wont take payments until this is fixed grrr.
So, just to be clear; you recompiled Apache (using easyapache) including support for SOAP, and now your cURL capabilities went down. Yes?
 

Jeewhizz

Well-Known Member
Mar 12, 2003
51
0
156
London, England
To add to this, we experienced this problem when updating PHP via easy apache. Curl was rebuilt by easy apache in /opt/curlssl and this was used to compile PHP against.

However, whenever we did a POST with curl, it would never do the POST. It would only ever do a GET. This was working fine before the re-compile with easyapache.

In the end, after lots of debugging, we narrowed it down to that install.

So, we recompiled PHP against the operating system RPM binaries for curl (curl & curl-devel) and installed this. This worked fine, and functionality was restored...

Jee