Hello
we are working with DA on centos 6.x and we keep having problems with curl.
Centos installs its own ancient version of curl in
and Direct Admin its own new version in
Our latest problem was with lets encrypt not working, errors:
and
the letsencrypt script seems to look and use /usr/bin/curl
which is always the wrong version and not DA's curl!
On top of that in the latest DA Curl compile the command
seems to point to /usr/lib64/libcurl.so....
and this is not what I expected as that is the centos repo curl, DA curl ilbs are in:
!
To get it to work I symlinked all the centos repo libcurls (/usr/bin and /usr/lib64) to the DA libcurls and excluded curl from updating in yum.conf.
But with my limited knowledge this seems hack?
Can Direct Admins libcurl just keep to itself on Centos without causing conflicts, if so how do I do that?
Is this okay what I did? Joris
we are working with DA on centos 6.x and we keep having problems with curl.
Centos installs its own ancient version of curl in
Code:
/usr/bin
/usr/lib64
Code:
/usr/local/bin/
/usr/local/lib/
Code:
curl: (2) Failed initialization
Code:
Nonce is empty (https://help.directadmin.com/item.php?id=664)which is always the wrong version and not DA's curl!
On top of that in the latest DA Curl compile the command
Code:
ldd /usr/local/bin/curland this is not what I expected as that is the centos repo curl, DA curl ilbs are in:
Code:
/usr/local/lib/libcurl.so...To get it to work I symlinked all the centos repo libcurls (/usr/bin and /usr/lib64) to the DA libcurls and excluded curl from updating in yum.conf.
But with my limited knowledge this seems hack?
Can Direct Admins libcurl just keep to itself on Centos without causing conflicts, if so how do I do that?
Is this okay what I did? Joris