A client had their server moved and the magento cron.php was never set back up. When I enabled them, I found that Magento was posting to paypal:
Cron /usr/bin/php -q /home/dev/public_html/cron.php
* About to connect() to api-3t.paypal.com port 443 (#0)
* Trying 173.0.88.69...
* connected
* Connected to api-3t.paypal.com (173.0.88.69) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using DES-CBC3-SHA
* Server certificate:
* subject: C=US; ST=California; L=San Jose; O=PayPal, Inc.; OU=PayPal Production; CN=api-3t.paypal.com
* start date: 2013-07-03 00:00:00 GMT
* expire date: 2015-09-18 23:59:59 GMT
* subjectAltName: api-3t.paypal.com matched
* issuer: C=US; O=VeriSign, Inc.; OU=VeriSign Trust Network; OU=Terms of use at https://www.verisign.com/rpa (c)10; CN=VeriSign Class 3 Secure Server CA - G3
* SSL certificate verify ok.
> POST /nvp HTTP/1.1
Host: api-3t.paypal.com
Accept: */*
Content-Length: 225
Content-Type: application/x-www-form-urlencoded
* upload completely sent off: 225 out of 225 bytes
< HTTP/1.1 200 OK
< Date: Tue, 25 Mar 2014 01:45:04 GMT
< Server: Apache
< Content-Length: 240
< Connection: close
< Content-Type: text/plain; charset=utf-8
<
* Closing connection #0
There were a bunch of these that were output from the cron job. I immediately disabled the cron.
I can’t, for the life of me, find:
1: any reason for magento to contact paypal (this is a dev server that hasn’t had a complete order since it was set up [from copy of the production server])
2: any logs in Magento or Payal that could tell me what exactly it’s posting.
Can anyone shed some light? We really need to get the cron working so we can get the sitemap generation running but I am not comfortable having it talk to Paypal for no reason.
We currently are using Paypal Payments Pro and Express Checkout
Thanks,
Mike
This is standard Magento cron job for getting reports from paypal, no worries. You are right - it's paypal_fetch_settlement_reports job. It placed in app/code/core/Mage/Paypal/etc/config.xml:
<crontab>
<jobs>
<paypal_fetch_settlement_reports>
<run>
<model>paypal/observer::fetchReports</model>
</run>
</paypal_fetch_settlement_reports>
</jobs>
</crontab>
Related
I'm trying to integrate authorize.net (AIM) using the official PHP SDK v2.0.0 and I'm seeing some strange behaviors:
curl_exec() returns false even when the request is successful and CURLOPT_RETURNTRANSFER is set to true.
curl_errno is returns 7 (Failed to connect() to host or proxy) for the same request.
I know request is successful since:
I can see the transaction is successfully recorded at authorize.net
Setting CURLOPT_RETURNTRANSFER to false causes the JSON response from authorize.net to be printed
curl_getinfo() shows HTTP status code = 200
Anyone experience this type of behavior with cURL? I'm not sure what I'm missing.
EDIT: Added output with CURLOPT_VERBOSE set
* Trying 198.241.206.22:443...
* Connected to apitest.authorize.net (198.241.206.22) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /home/app/demo/assets/lib/anet_sdk_2.0.0/lib/ssl/cert.pem
CApath: none
* SSL connection using TLSv1.2 / AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: C=US; ST=California; L=Foster City; O=Authorize.Net; CN=*.authorize.net
* start date: Feb 5 20:44:08 2020 GMT
* expire date: Mar 15 21:14:08 2021 GMT
* subjectAltName: host "apitest.authorize.net" matched cert's "*.authorize.net"
* issuer: C=US; O=Entrust, Inc.; OU=See www.entrust.net/legal-terms; OU=(c) 2012 Entrust, Inc. - for authorized use only; CN=Entrust Certification Authority - L1K
* SSL certificate verify ok.
> POST /xml/v1/request.api HTTP/1.1
Host: apitest.authorize.net
Accept: */*
Content-Type: text/json
Content-Length: 1458
* upload completely sent off: 1458 out of 1458 bytes
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Cache-Control: no-store
< Pragma: no-cache
< Content-Type: application/json; charset=utf-8
< X-OPNET-Transaction-Trace: a2_fe4a070f-cf07-47d7-8e9e-c8a703920de5-5628-7089051
< Access-Control-Allow-Credentials: true
< Access-Control-Allow-Headers: x-requested-with,cache-control,content-type,origin,method,SOAPAction
< Access-Control-Allow-Methods: PUT,OPTIONS,POST,GET
< Access-Control-Allow-Origin: *
< Strict-Transport-Security: max-age=31536000
< X-Cnection: close
< Date: Sat, 12 Sep 2020 10:40:48 GMT
< Content-Length: 512
<
* Connection #0 to host apitest.authorize.net left intact
Good Evening Everyone.
Have been searching for a week to try and find a way of connecting using guzzle.
curl -v https://go.paytraq.com/api/{APICall}?APIToken={APIToken}&APIKey={APIKey} \
-H "Content-Type:text/xml" \
-d "{RequestBody}"
I tried all methods and keep getting unauthorised access and not sure the best way to pass APIToken and APIKey.
I have used the above from terminal and it works fine.
$client = new \GuzzleHttp\Client(['base_uri'=>'https://go.paytraq.com']);
$request = $client->request('GET','/api/clients',['debug'=>true],[ 'headers'=>
'APIToken=XXXXXX&APIKey=XXXX'
]);
The above is the last version of my code which gives me the below error
GuzzleHttp\Exception\ClientException
Client error: GET https://go.paytraq.com/api/clients resulted in a 401 Unauthorized response: API key or token is not provided
And below is the guzzle debug
Trying 52.16.7.7:443... * Connected to go.paytraq.com (52.16.7.7) port 443 (#0) * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /usr/local/etc/openssl#1.1/cert.pem CApath: /usr/local/etc/openssl#1.1/certs * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 * ALPN, server did not agree to a protocol * Server certificate: * subject: CN=go.paytraq.com * start date: Oct 14 00:00:00 2019 GMT * expire date: Nov 14 12:00:00 2020 GMT * subjectAltName: host "go.paytraq.com" matched cert's "go.paytraq.com" * issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon * SSL certificate verify ok. > GET /api/clients HTTP/1.1 Host: go.paytraq.com User-Agent: GuzzleHttp/7 * Mark bundle as not supporting multiuse < HTTP/1.1 401 Unauthorized < Content-Type: text/plain; charset=utf-8 < Date: Sat, 01 Aug 2020 21:03:49 GMT < Request-Time: 1 < Server: nginx/1.4.6 (Ubuntu) < Content-Length: 32 < Connection: keep-alive < * Connection #0 to host go.paytraq.com left intact
This should work:
$client->request('GET', '/api/clients', ['query' => [
'APIToken' => $APIToken,
'APIKey' => $APIkey]
]);
In my php website the page redirection associated with paypal is not working by giving the following in the apache error log. I have exposed port 80 as well as 443 in Dockerfile. Rest of the things are working fine in the site and the site with the same code is running fine in my local apache server.
* Trying 173.0.82.83...
* Connected to api-3t.sandbox.paypal.com (173.0.82.83) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection:
ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:#STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* SSL connection using TLSv1.2 / AES256-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: C=US; ST=California; L=San Jose; O=PayPal, Inc.; OU=PayPal
Production; CN=api-3t.sandbox.paypal.com
* start date: Jan 14 00:00:00 2016 GMT
* expire date: Jan 14 23:59:59 2018 GMT
* subjectAltName: api-3t.sandbox.paypal.com matched
* issuer: C=US; O=Symantec Corporation; OU=Symantec Trust Network;
CN=Symantec Class 3 Secure Server CA - G4
* SSL certificate verify ok.
> POST /nvp HTTP/1.1
Host: api-3t.sandbox.paypal.com
Accept: */*
Content-Length: 655
Content-Type: application/x-www-form-urlencoded
* upload completely sent off: 655 out of 655 bytes
< HTTP/1.1 200 OK
< Date: Mon, 04 Sep 2017 08:07:48 GMT
< Server: Apache
< X-SLR-RETRY-API: SetExpressCheckout
< X-PAYPAL-OPERATION-NAME: SetExpressCheckout
< X-PAYPAL-API-RC:
< Connection: close
< HTTP_X_PP_AZ_LOCATOR: sandbox.slc
< Paypal-Debug-Id: 6692e8ec22b4a
< Set-Cookie: X-PP SILOVER=name%3DSANDBOX3.API.1%26silo_version%3D1880%26app%3Dappdispatcher_apit%26TIME%3D3691621721%26HTTP_X_PP_AZ_LOCATOR%3Dsandbox.slc; Expires=Mon, 04 Sep 2017 08:37:56 GMT; domain=.paypal.com; path=/; Secure; HttpOnly
< Set-Cookie: X-PP-SILOVER=; Expires=Thu, 01 Jan 1970 00:00:01 GMT
< Content-Length: 137
< Content-Type: text/plain; charset=utf-8
<
* Closing connection 0
Please help me in fixing this error.
I can find error logs under apache in my local and in case of success scenarios nothing is being logged
I am using Ubuntu 17.04 installed in oracle VM. I am not able to ping paypal sandbox URL from my server in VM. If I am trying to ping the URL from my local commandprompt, I am getting Request Timed out inspite of successful paypal connection in my local apache (from XAMP).
I have developped functions to use PayPal NVP method for a website (I still use the Paypal Sandbox). All was working perfectly but since a week I can't make a request (setExpressCheckout), I have always an errcode 10054.
Here is the CURL log :
Trying 173.0.82.83...
Connected to api-3t.sandbox.paypal.com (173.0.82.83) port 443 (#0)
Cipher selection: TLSv1
successfully set certificate verify locations:
CAfile: C:\data\pem\cacert.pem
CApath: none
SSL connection using TLSv1.2 / AES256-SHA
Server certificate:
subject: C=US; ST=California; L=San Jose; O=PayPal, Inc.; OU=PayPal Production; CN=api-3t.sandbox.paypal.com
start date: 2016-01-14 00:00:00 GMT
expire date: 2018-01-14 23:59:59 GMT
issuer: C=US; O=Symantec Corporation; OU=Symantec Trust Network; CN=Symantec Class 3 Secure Server CA - G4
SSL certificate verify ok.
GET /nvp?VERSION=124.0&USER=xxxxxxxxxxxxxxxxxxxxx&PWD=xxxxxxxxxxxxx&SIGNATURE=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&METHOD=SetExpressCheckout&CANCELURL=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&RETURNURL=xxxxxxxxxxxxxxxxxxxx&L_PAYMENTREQUEST_0_NAME0=Panier&L_PAYMENTREQUEST_0_NUMBER0=100&L_PAYMENTREQUEST_0_DESC0=Panier&L_PAYMENTREQUEST_0_QTY0=1&L_PAYMENTREQUEST_0_AMT0=96.20&PAYMENTREQUEST_0_PAYMENTACTION=Sale&PAYMENTREQUEST_0_AMT=96.20&PAYMENTREQUEST_0_CURRENCYCODE=EUR&DESC=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&LOCALECODE=FR&USERACTION=COMMIT&BRANDNAME=xxxxxxxxxxxxxxxx HTTP/1.1
Host: api-3t.sandbox.paypal.com
User-Agent: PayPal-PHP-SDK
Accept: */*
SSL read: error:00000000:lib(0):func(0):reason(0), errno 10054
Closing connection 0
The SSL connection seems ok, but I have always this error.
I tried from a Windows server and a Linux server (both with Apache) with same results.
I really don't know how to solve my problem ...
Any help will be appreciated.
Regards.
PS:sorry for my bad english.
The trouble showed itself yesterday - getting following answer from curl (called in php script by curl_exec):
$<errno>35</errno>
$<error>Unknown SSL protocol error in connection to w3s.webmoney.ru:443 </error>
That bug happens only sometimes, something around 4-5 valid responses to one invalid with 35 error. Before yesterday application was handling those requests correctly for a very long time.
Hope someone will give me a hint about possible reasons of that bug.
P.S. We are suffering from internet connection problems lately, can it be somehow connected to that bug?
Upd:
Setting verbose output to true made curl to write following log:
* About to connect() to w3s.webmoney.ru port 443 (#0)
* Trying 82.198.171.158... * connected
* Connected to w3s.webmoney.ru (82.198.171.158) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: ${path}/WebMoneyCA.crt
CApath: /etc/ssl/certs
* SSL connection using RC4-MD5
* Server certificate:
* subject: C=RU; O=WebMoney Transfer; OU=WebMoney Web Service; CN=w3s.webmoney.ru
* start date: 2010-06-07 10:03:43 GMT
* expire date: 2012-06-07 10:13:43 GMT
* common name: w3s.webmoney.ru (matched)
* issuer: OU=WM Transfer Certification Services; O=WM Transfer Ltd; CN=WebMoney Transfer Root CA
* SSL certificate verify ok.
> POST /asp/XMLPurses.asp HTTP/1.1
Host: w3s.webmoney.ru
Accept: */*
Content-Length: 281
Content-Type: application/x-www-form-urlencoded
< HTTP/1.1 200 OK
< Date: Fri, 10 Dec 2010 13:00:04 GMT
< Server: Microsoft-IIS/6.0
< X-Powered-By: ASP.NET
< Content-Length: 4423
< Content-Type: text/xml; Charset=windows-1251
< Expires: Fri, 10 Dec 2010 13:00:04 GMT
< Set-Cookie: ASPSESSIONIDQADQDTAQ=FJMNECHBENFFAADHEHPFOKAE; path=/
< Cache-control: private
<
* Connection #0 to host w3s.webmoney.ru left intact
* Closing connection #0
* About to connect() to w3s.webmoney.ru port 443 (#0)
* Trying 212.158.173.158... * connected
* Connected to w3s.webmoney.ru (212.158.173.158) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: ${path}/WebMoneyCA.crt
CApath: /etc/ssl/certs
* Unknown SSL protocol error in connection to w3s.webmoney.ru:443
* Closing connection #0
Upd:
The trouble was not on our side. The problem was hidden somewhere in w3s.webmoney.ru, in 212.158.173.158 server. I'll add more details about the bug if information will be available.
Got the following response from WM support people:
"There are four IP addresses on hostname w3s.webmoney.ru. When a request ends up on 212.158.173.158, SSL is getting killed by a piece of anti-DDoS hardware at the provider's. The problem was localized, they're now trying to fix it."