Marketplace in 5.4 - Curl Error
Permalink 2 users found helpful
Hi,
I'm using Concrete 5 since 2 years now on different sites and I'm quite happy, but:
After I upgrade from 5.3.3.1 where Marketplace works fine, now i get an Error:
"Error establishing connection to the concrete5 community. Please check that curl and other required libraries are enabled. "
Curl is insalled correctly, so wich other libraries are required since 5.4?
Thanks for any hints
I'm using Concrete 5 since 2 years now on different sites and I'm quite happy, but:
After I upgrade from 5.3.3.1 where Marketplace works fine, now i get an Error:
"Error establishing connection to the concrete5 community. Please check that curl and other required libraries are enabled. "
Curl is insalled correctly, so wich other libraries are required since 5.4?
[root@www ~]# yum list | grep curl curl.x86_64 7.15.5-2.1.el5_3.5 installed curl.i386 7.15.5-2.1.el5_3.5 base curl-devel.i386 7.15.5-2.1.el5_3.5 base curl-devel.x86_64 7.15.5-2.1.el5_3.5 base [root@www ~]#
Thanks for any hints
phpinfo(); please
http://concrete.itsd.de/phpinfo.php
just our testsite... but some other concrete5 sites on the same server
thanks!
just our testsite... but some other concrete5 sites on the same server
thanks!
Hi Segro, we're having the same problem - we've just done a fresh install of 5.4 on our dev server to give it a whirl.
Only difference is that we proxy to our dev server, although I can't see this being an issue.
I'll let you know if we make a breakthrough!
Only difference is that we proxy to our dev server, although I can't see this being an issue.
I'll let you know if we make a breakthrough!
Hi s8design,
i've also tried a fresh install with a domain on same server, same result.
Cant see any errors in http log or even http-error-log.
The strange thing: even @home on my qnap NAS-Server c5.4 with marketplace works fine! for testing.
Could anybody from the development-team please post some infos about the required libraries, perhaps curl version?
Thx!
i've also tried a fresh install with a domain on same server, same result.
Cant see any errors in http log or even http-error-log.
The strange thing: even @home on my qnap NAS-Server c5.4 with marketplace works fine! for testing.
Could anybody from the development-team please post some infos about the required libraries, perhaps curl version?
Thx!
My Curl info:
libcurl/7.19.7 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.4 libssh2/1.2.2
Yours:
libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5
have your host update your curl/zlib/etc
libcurl/7.19.7 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.4 libssh2/1.2.2
Yours:
libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5
have your host update your curl/zlib/etc
Having the same problem. It's the "other required libraries" I suspect since curl is installed and functioning. Investigating further.
Hi @all,
on all our servers we're using CentOS /RHLE and there is still php5.1 in the repository. I installed a newer version of curl and the other required libraries, but i need to re-compile PHP. Thats no good idea for security reasons, because one is loosing the ability to update the systemm through the packet-manager (yum)/ std. repositories.
Worse is, that Marketplace integration was working well with 5.3.3.1 and stopped working now...
on all our servers we're using CentOS /RHLE and there is still php5.1 in the repository. I installed a newer version of curl and the other required libraries, but i need to re-compile PHP. Thats no good idea for security reasons, because one is loosing the ability to update the systemm through the packet-manager (yum)/ std. repositories.
Worse is, that Marketplace integration was working well with 5.3.3.1 and stopped working now...
hi,
in most cases this error message has nothing to do with curl, actually. if you have allow_url_fopen set to "on" in php.ini (which is the default), then concrete tries to fetch things with file_get_contents() first before resorting to curl functions.
do you run concrete from your virtual host's root directory or from a subdirectory likehttp://www.domain.com/concrete? for the latter, market place validation will fail for some reason - i guess we have to ask concrete devs to fix it.
for now, just go to file concrete/libraries/marketplace.php line 43 and change "false" to "true" - this should fix it. ugly but working :)
hth,
jakob
in most cases this error message has nothing to do with curl, actually. if you have allow_url_fopen set to "on" in php.ini (which is the default), then concrete tries to fetch things with file_get_contents() first before resorting to curl functions.
do you run concrete from your virtual host's root directory or from a subdirectory likehttp://www.domain.com/concrete? for the latter, market place validation will fail for some reason - i guess we have to ask concrete devs to fix it.
for now, just go to file concrete/libraries/marketplace.php line 43 and change "false" to "true" - this should fix it. ugly but working :)
hth,
jakob
Thanks Jakob - Your fixed worked for us perfectly. FYI we're also running from a centralized core install.
The fix unfortunately didn't work for me. Line 43 being the following after the fix:
$this->isConnected = true;
My setup as follows:
Concrete 5.4.0.5
Running on turnkey-lamp-2009.10-2-hardy-x86
Which is running as a VM on VirtualBox-3.2.6-63112-Win.
server includes curl libcurl3 libcurl3-dev php5-curl libcurl4-openssl-dev
browser cache cleared
"allow_url_fopen" is ON
server restarted
However on my new install when I try to connect to the community, I am consistently receiving the error message "Your site token must be 64 characters."
Any other suggestions?
$this->isConnected = true;
My setup as follows:
Concrete 5.4.0.5
Running on turnkey-lamp-2009.10-2-hardy-x86
Which is running as a VM on VirtualBox-3.2.6-63112-Win.
server includes curl libcurl3 libcurl3-dev php5-curl libcurl4-openssl-dev
browser cache cleared
"allow_url_fopen" is ON
server restarted
However on my new install when I try to connect to the community, I am consistently receiving the error message "Your site token must be 64 characters."
Any other suggestions?
Hi Jakob,
Your fix works fine for me. Thank you.
My env.
concrete 5.4.1.1
CentOS 5.2
PHP 5.1.6
Snufkinski
Your fix works fine for me. Thank you.
My env.
concrete 5.4.1.1
CentOS 5.2
PHP 5.1.6
Snufkinski
Thanks, worked fine!
My marketplace.php only has 3 lines.
My marketplace.php only has 3 lines.
Hi,
Just wondered if anyone has come up with a workable fix to this this problem. I've tried the suggested solutions from this and other threads and none seem to work for me.
I've tried Jakob's suggestion, but the site seems to run incredibly slowly from the Dashboard. I've tried re-registering with the Marketplace after removing the two database variables but the problem persists, on the one hand saying that there is an 'Error communicating with...' and on the other that the site is already connected. I've also tried setting the http_proxy environment variable, both in my httpd startup and by using SetEnv within the Apache configuration.
I'm assuming that the slowness is either due to the failure to get out through our Squid proxy server or receiving no response back.
Does anyone have any other ideas or have come up with a solution recently or is this a bug which needs fixing? I do have cURL installed BTW.
Regards
Ray
Just wondered if anyone has come up with a workable fix to this this problem. I've tried the suggested solutions from this and other threads and none seem to work for me.
I've tried Jakob's suggestion, but the site seems to run incredibly slowly from the Dashboard. I've tried re-registering with the Marketplace after removing the two database variables but the problem persists, on the one hand saying that there is an 'Error communicating with...' and on the other that the site is already connected. I've also tried setting the http_proxy environment variable, both in my httpd startup and by using SetEnv within the Apache configuration.
I'm assuming that the slowness is either due to the failure to get out through our Squid proxy server or receiving no response back.
Does anyone have any other ideas or have come up with a solution recently or is this a bug which needs fixing? I do have cURL installed BTW.
Regards
Ray
I'm seeing the same problem. Can anyone help resolve this.
