SellerDeck for Sage Pay v3 12.0.6 not working

[graphicz]

Client has a succesful 12.0.5 site using Sage Pay. He does not have Cover.

He installed 12.0.6 as Sage is his only method of taking payment. He refreshed through Help, Troubleshooting to ensure all new files were uploaded

He correctly registered his IP address and subnet. (https://www.youtube.com/watch?v=chN0...ature=youtu.be)

The integration no longer works, when a customer places and order and goes to payment:

error initialising payment service please try another method

What I find iniquitous is that SellerDeck will not support this upgrade even though it is not asked for by customers but rather essential for SellerDeck to remain competetive by integrating with Sage. Also, by refusing to support this version they will not know of issues that may suggest a problem with their revised integration.

Does anybody know a solution to my client's problem here?

Thank you.

[graphicz]

It seems it may be a Sage Pay issue. Client phoned Sage who said that the 'IP address hadn't taken'. It is likely that Sage did something manually to address the issue.

It does raise another problem though, domestic routers reassign IP addresses from time to time as a security thing, the IP addresses are also reassigned if the router is rebooted, in a power outage for example. This means that this new IP address must be registered with Sage.

Since we do not always know when the router has reissued ip addresses it might be worth considering asigning a static IP adress for your SD PC or laptop (see you Router's instructions for this.) However there may be security considerations to having a static IP address, you would need to seek advice on this.

[Sam Bromley]

Hi Jonathan.

It is the IP of the server, Which by design needs to be static, and a customers router won't effect it.
The reason for this is a new level of security by sage, it needs to know what servers it will receive the information from. ( However after reading the sage article it seems to be a little lacking. so I have passed this information along)

If a server has multi IP addresses associated with it then more IP addresses can be added with the subnet of 255.255.255.255.

In regards to your client I'm afraid as he doesn't have cover than he cannot be supported, but I believe you spoke to a colleague a arrangement has been made.

If you have any questions please feel free to email me.

Thanks.

[saucysal]

Same here

I am getting the same error message after upgrading, and unfortunately just past 5.00 pm!!

Not amused!

I have put all possible ip addresses on Sage.

Sarah

[pmsupport]

Hi all,

It could be that your web server does not have Crypt::SSLeay installed. We have updated our knowledge base article below to explain this here:

http://community.sellerdeck.com/showthread.php?t=56243

[saucysal]

How do I find the right ip addresses?

Before upgrading, I had entered all the ip addresses of my sellerdeck websites into SagePay. However, this did not work. I rang SagePay this evening after doing some trial orders on one site. They had a record of my attempts and gave me the ip address to enter, which was different to any of the ones I had entered previously. I asked her what it was the ip address of, and all she could say that it was of my server, where the instruction was coming from. What is meant by "server"? My sites are hosted by one and one, and I can find no ip addresses on my account there other than the ones that I already had, which are on SagePay. I tried looking up in reverse the ip address that she gave me, which worked correctly for one site, to find out what is was, but only came up with ripe.net in the Netherlands - what is that?

Sarah

[saucysal]

Had to ring SagePay for each

As I could not find out any of the correct ip addresses, I had to place test orders on each site and ring up SagePay after each to find out the ip address that it came from and then enter it on Sagepay. They were helpful.

Sarah

[smilesbest]

On upgrading to SagePay V3 I had the same "Error initialising payment service. Please try another payment method" problem as reported by others AND this was after I had checked that "Crypt::SSLeay" was installed AND after registering three server IP addresses (as provided by http://www.who.is/dns/) with SagePay. Like Sarah I had to contact SagePay support. Fortunately they were able to identify another IP address from a failed test order I had placed earlier and register it for me. Everything now appears to be fine but I really miss the payment confirmation emails - I suspect my buyers do too.

[kev67]

On upgrading to SagePay V3 I had the same "Error initialising payment service. Please try another payment method" problem as reported by others AND this was after I had checked that "Crypt::SSLeay" was installed AND after registering three server IP addresses (as provided by http://www.who.is/dns/) with SagePay. Like Sarah I had to contact SagePay support. Fortunately they were able to identify another IP address from a failed test order I had placed earlier and register it for me. Everything now appears to be fine but I really miss the payment confirmation emails - I suspect my buyers do too.

Here Here !!

[winsbury]

I suspect the issue of IP addresses is going to be another big problem for some:

1. if you run your site on a dedicated server with a static IP you should be okay.
2. If you are on a shared server your IP may change if the hosting company moves you site to another server.
3. If you are on a shared server but have a dedicated IP for your site you should be okay.
4. If you have load balancing or server failover features your IP could change at any time , depending on whether you can get a list of IPs your site may become is important
5. If you host on a dynamic IP address, for example behind your own broadband connection the new system will not work reliably as a new IP is randomly assigned by your isp for a variety of reasons including router reboot or adsl line reset. Even using DDNS service will not fix this.
6. If you have multiple sites using a single sagepay account, each site will probably have different IP addresses unless all hosted on one dedicated server.

Whether there is a limit to the number of IPs that sagepay can register on one account is not clear but if there is, it might come into play in some scenarios.

With the rapidly running out of static IPv4 addresses and greater reliance on virtual and cloud based hosting there is imho a growing need for sagepay to chose a different method to verify the source of payment requests.

[kev67]

Excellent post Dean

It makes a huge amount of sense - even to me

I emailed Sagepay Saturday confirming my fears and also confirming my IP address and got this reply last night

You can add the ip address by logging into My Sagepay then by going to Settings across the top and then valid ip's down the left and from here you can add this ip address

So, I'm going to bite the bullet and see what happens

[winsbury]

A couple of tools you might find handy to discover your server IP address...

http://mxtoolbox.com/DNSLookup.aspx - type in your website address (eg www.mysite.com )and the DNS A record will show the IP address it points to. In nearly all cases this will be the IP address of your web server.

http://mxtoolbox.com/ReverseLookup.aspx - now type the IP address obtained from above here. The reverse (PTR) record will show the host name that the IP address relates to according to the registry which issued the IP address, usually this is your dedicated server name or the name of the shared server your site is hosted on. If it is not, it might lead to problems with email but should not cause any issues with web hosting.

From any windows PC, open a DOS window and type

Ping  www.mysite.com

Assuming the server is alive you will see a series of responses with your IP address visible and a time taken for the response. If all you get is timeouts there might be a problem with your server IP address or the DNS A record from the first step. Some ISPs disable ping responses so this is not a definitive test.

[graphicz]

I resell Heart hosting and they tell me that the server IP address on the shared hosting platform remains constant and that they run Perl v5.10.1 which also has Crypt::SSLeay installed.

[Simon G]

I had the same problems with a Sellerdeck V11, I had the latest patch, the required perl module and registered the domain's IP address of the site (it has a dedicated IP address)

Sagepay told me the IP address was registered properly and assured me that had it been an IP address problem they would be able to see the rejection in their logs.

So I came to this forum and drew a blank. What else could I do? I decided to broaden the range of IP addresses on my Sagepay admin console... and Bingo!

Conclusion, Sagepay support staff are friendly and helpful but not that technical and whilst their server logs would show dropped and rejected connections they do not seem to have access to them even though they claim to.

hope this helps

[kev67]

Stupid question, but how wide did you expand them Simon?

I mean, the support I'm being given is utter shit to be perfectly frank - it's utterly no good