Cloudflare with SSL & SagePay Server 5006 Error

We have been battling with an issue where I've been getting a 5006 error using "SagePay Server" for 24 hours after moving a nopcommerce site to a new server with a different IP address.

We use a free cloudflare service with SSL enabled on Cloudflare in Full SSL mode and then a self signed certificate on our server so the connection is always secured end to end. This was also the same on the old server.

When moving servers we simply updated the IP address in couldflare to point at the new IP address but we started getting 5006 errors during the checkout process...

SagePay support told us they could not connect to our notification URL which was using SSL. Our server showed no attempt from their server to connect to ours yet SapePays log files show an "internal_error" with no more useful information.

However it is possible to the call the notification URL passed to SagePay from a browser and it works without issue.


After talking with SagePay on several occasions it would seem the SagePay system does not support websites / traffic using SSL with SNI which means they can not connect to the notification URL over SSL.

In a time when IPv4 addresses are fast running out I would imagine more and more people will start to use SNI for SSL so they can run multiple sites using SSL from one IPv4 address - a massive oversight on SagePay's part me thinks.


Contrary to JaxUK, I can confirm SagePay does support SSL/TLS with SNI. Hope this helps someone

链接地址: http://www.djcxy.com/p/32466.html

上一篇: Heroku用CloudFlare ssl托管RoR站点不起作用

下一篇: Cloudflare与SSL&SagePay Server 5006错误