Order Accept Encountered Problems Connection Error: Unknown SSL protocol error in connection

[daneshtv]

Dear All,

 

We are facing some SSL error issues in WHMCS order are, please find the scree shot and help us to fix this issue...

 

Regards

Dane

[sentq]

With any of Server Modules this error occurred?

 

possible solutions:

 

add this option to your code:

CURLOPT_SSLVERSION => 3

 

or downgrade/upgrade curl extension to stable version

[daneshtv]

No, I have already configured Auto set up module(while clients placing orders)but it is not happening automatically while clients place orders and it is showing in pending order list. So i have tried to manually accept the orders from pending order area and showing this error: "Order Accept Encountered Problems Connection Error: Unknown SSL protocol error in connection to (My IP address)(35)

[sentq]

maybe my answer wasn't clear, the error message you encounter is related to cURL:

http://stackoverflow.com/questions/26009611/php-curl-returns-35-ssl-connect-error

http://stackoverflow.com/questions/19384161/curl-error-35-unknown-ssl-protocol-error-in-connection-to-api-rkd-reuters-com

 

in these two answers they suggest adding the following option would solve the issue

curl_setopt($ch, CURLOPT_SSLVERSION , 3);

[daneshtv]

Hi,

 

We have updated the same to our hosting team and they have done few things as you told, but still it is showing the same error.

 

1. They have enabled curl. and replied the below:

"Please note that we have made some changes in the server realted to curl settings with SSL. Kindly check now at your end and also the above line which you have mentioned have to add in the file "rest_proxy.php" which is one of the API file.

 

Please note that this is related to the API file which you have installed. This is some thing you need to check from your end. We don't have the access to the client files. AS each and every file under your API has been mapped to another files,we don't no the structure of those files. Hence we advice you to check with your developer and add the above line in the file API file "rest_proxy.php" and proceed further."

 

What to do now??

[sentq]

Looks like the line mentioned wasn't added right?

 

Have you checked with your developer about that issue?

[daneshtv]

We dont have developer, all configuration,installation and set up was done by WHMCS team only, what should I do? even not geting help on this matter from WHMCS tech team ;(

[sentq]

is this file encoded "rest_proxy.php"?

[daneshtv]

Hi this SSL error has been resolved, now it is creating some other error as mentioned below...plz guide me

 

as usual client sign up and payment processing is showing completed, but all the orders showing under pending order and while trying to accept order manually, its is showing the bellow error..

 

Order Accept Encountered Problems

(XID uhk8a7) The domain “jobsoch.com” already exists in the Apache configuration.

 

How to resolve this? We have configured Module Setting as - Automatically setup the product as soon as the first payment is received

[sentq]

if you have the option "Automatically setup the product as soon as the first payment is received" then you don't have to tick or click the "Create" option in this product as it already created.

 

Pending orders is there for you to review

[daneshtv]

Then how it is showing in pending order list as "pending" and in respective client portal Service as "Pending as well?

This should be shown as "acitve" in both places know? and customer would be getting the loging credentials thru mails also?

[sentq]

tried to contact WHMCS support? they can get closer look inside your installation and investigate about all of these issues

[daneshtv]

Yes, raised ticket, waiting for updates

[ragesw]

Please post here what you find out because I am having a similar problem after upgrading to 6.3.1

 

Product is set to;

 

'Automatically setup the product as soon as the first payment is received'

 

but they stay as pending both in the Admin area AND in the client area.

 

This was working properly before the upgrade to 6.3.1 for me.