Developers are not necessarily system administrators.I've already had two developers take a look and could not find the issue.
https://www.paypal-knowledge.com/infocenter/index?page=content&id=FAQ1914To ensure the security of our systems and adhere to industry best practices, PayPal is updating its services to require TLS 1.2 for all HTTPS connections. At this time, PayPal will also require HTTP/1.1 for all connections.
Yeah, I'm aware. They know Linux extremely well.Developers are not necessarily system administrators.
Your hosting provider needs to check to confirm that connectivity between your site (the server it is on or the VPS/server itself) is good.
Could this be an issue with your hosting provider? It isn't scheduled to go into effect until 06/2017 - but may be an issue currently.
If you have shell access, you can confirm connection by the following commandYou should see similar to thisCode:
with the timestamp being different.
Are you using the internal functions or something like BD Paygates add-on?
You have some type of DNS lookup error as the "could not resolve host" clearly states. Whether it's permanent or transient is another matter. And if they knew it "extremely well" they should have been able to do a simple test like the above and confirm a connectivity issue.Yeah, I'm aware. They know Linux extremely well.
curl: (6) Couldn't resolve host 'tlstest.paypal.com'
nameserver 22.214.171.124 nameserver 126.96.36.199 nameserver 188.8.131.52