jpapa
Contributor
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on
Jul-13-2017
11:44 AM
I had some testing that was going well up until last week.
https://api-3t.sandbox.paypal.com/nvp gives error:
Secure Connection Failed
Is this a known issue? Need to finish up this project and move into production.
edited to update the correct issue, since I was testing variations in an attempt to troublshoot
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Accepted Solutions
MTS_Justin
Moderator
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug-15-2017
04:54 AM
Hi All,
This issue should now be completely resolved.
The URL should from today show the correct sub-domain "sandbox.paypal.com instead of "sandbox3.paypal.com".
Was my post helpful? If so, please give me a kudos!
This issue should now be completely resolved.
The URL should from today show the correct sub-domain "sandbox.paypal.com instead of "sandbox3.paypal.com".
Was my post helpful? If so, please give me a kudos!
4 REPLIES 4
MTS_Justin
Moderator
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jul-14-2017
03:04 AM
Hello,
This isn't a known issue.
It appears your unable to establish a secure connection to our endpoint. Does your system support TLS v1.2 ?
https://www.paypal-knowledge.com/infocenter/index?page=content&widgetview=true&id=FAQ1914&viewlocale...
You can test and confirm by using the TLS test tool available here - https://github.com/paypal/TLS-update
Was my post helpful? If so, please give me a kudos!
This isn't a known issue.
It appears your unable to establish a secure connection to our endpoint. Does your system support TLS v1.2 ?
https://www.paypal-knowledge.com/infocenter/index?page=content&widgetview=true&id=FAQ1914&viewlocale...
You can test and confirm by using the TLS test tool available here - https://github.com/paypal/TLS-update
Was my post helpful? If so, please give me a kudos!
jpapa
Contributor
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jul-14-2017
04:06 AM
Thanks Justin. TLS was fine. Turns out the removal of GET from NVP/SOAP was the issue. I was quick testing some variations in cURL and browser with GET. Switched to POST and all seems to be good. Leaving this here in case anyone else needs to check up on more security updates https://www.paypal.com/au/webapps/mpp/merchant-security-roadmap
MTS_Justin
Moderator
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jul-14-2017
06:32 AM
Great to hear, thanks for the update !
Was my post helpful? If so, please give me a kudos!
Was my post helpful? If so, please give me a kudos!
MTS_Justin
Moderator
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug-15-2017
04:54 AM
Hi All,
This issue should now be completely resolved.
The URL should from today show the correct sub-domain "sandbox.paypal.com instead of "sandbox3.paypal.com".
Was my post helpful? If so, please give me a kudos!
This issue should now be completely resolved.
The URL should from today show the correct sub-domain "sandbox.paypal.com instead of "sandbox3.paypal.com".
Was my post helpful? If so, please give me a kudos!
Haven't Found your Answer?
It happens. Hit the "Login to Ask the community" button to create a question for the PayPal community.
Related Content
- Ipn PayPal server giving 301 or 302 errors in PayPal Payments Standard
- Trying to connect sandbox credentials in Magento 2.0 returns "Something went wrong." in Sandbox Environment
- need the signature - but can only find the fingerprint in NVP/SOAP APIs
- IPN SHOWS NO HTTP RESPONSE - LISTENER WORKS WITH LOCAL FORM POST in Sandbox Environment
- Connecting PayPal with GiveWP in REST APIs