4.24 PayFlowPro SSL_Read()

[hzrdc2]

My host upgraded my servers and now my miva cart is throwing this error when a user tries to process the payment.

Unable to authorize payment: SSL_Read() packet size mismatch

I'm just trying to find out where the breakdown is occuring, in miva? my ssl? paypal?

The support is not helping at the moment... any suggestions?

[ILoveHostasaurus]

Re: 4.24 PayFlowPro SSL_Read()

First thing to check is the payflow settings; I've seen that error before when the settings are not correct in the store. If you're running the latest payflow pro module, you should be using payflowpro.paypal.com as the server name. If that's what you're using, then I'm guessing they have somehow broken openssl on the server, preventing the Miva scripting engine (Empresa) from making outbound SSL-encrypted connections. Unfortunately that's not an issue you'd be able to resolve without admin level access to the server.

[hzrdc2]

Re: 4.24 PayFlowPro SSL_Read()

Thanks... that's the best response I have had yet.

I verified my settings, they appear correct. I do not have the latest module, but I can't upgrade because its only compatible with miva 5.

I know its something the host messed with, because this was all working fine on the 13th of January... they upgraded, broke the store and my perl scripts weren't working either.

Hostway has TERRIBLE support and service... I would move in a second if I know migrating would be easy.

I will go back to them and have a look at the openSSL stuff..

[ILoveHostasaurus]

Re: 4.24 PayFlowPro SSL_Read()

If you don't have access to it, PM me your email address and I'll send you a diagnostic file Miva has that will let you view the OpenSSL configuration, it will you more pointed information you can use to send to Hostway "Here's what's wrong, fix it" instead of just that generic error from the payment mod.

[hzrdc2]

Re: 4.24 PayFlowPro SSL_Read()

I don't think I have the right to send a private message.... or am I missing that somewhere?

[lesliekirk]

Re: 4.24 PayFlowPro SSL_Read()

You "might" have it now. Your first 3 posts have to be moderated before you have PM available.

[hzrdc2]

Re: 4.24 PayFlowPro SSL_Read()

nope... maybe post 4 :)

[hzrdc2]

Re: 4.24 PayFlowPro SSL_Read()

well.. they apparently fixed the SSL error by upgrading the PayFlowPro module to 4.2403...

But I still get the following error at the point when the user tries to process the order:

Unable to authorize payment: Unable to authorize payment.

[d_host]

Re: 4.24 PayFlowPro SSL_Read()

Are you entering a dummy or test card number by any chance, while your Payflow Pro is set to LIVE mode? If so, that is the expected response code. If you try it with a real card, it should go through.

[hzrdc2]

Re: 4.24 PayFlowPro SSL_Read()

Nope, I tried 2 legit credit cards... amex and visa... the payflowpro config was in live mode.

For the host I've used:

payflowpro.paypal.com
payflowpro.verisign.com
payflow.verisign.com - what it was set to a month ago before everything was broke

Any ideas?

[ILoveHostasaurus]

Re: 4.24 PayFlowPro SSL_Read()

Do you have it restricted by IP address on the payflow side?

[hzrdc2]

Re: 4.24 PayFlowPro SSL_Read()

I have no IP addressed set in the "allowed list"... so I assume that means none are restricted.

[hzrdc2]

Re: 4.24 PayFlowPro SSL_Read()

I'm working with PayPal and they keep asking me the following:

I will need the API request and response you received from Payflow when you processed this transaction for further troubleshooting.

how can I give them this?

[ILoveHostasaurus]

Re: 4.24 PayFlowPro SSL_Read()

Unfortunately you can't, Miva's payflow module has no provision for saving that information out for debugging. Are they not seeing the transactions at all?

[hzrdc2]

Re: 4.24 PayFlowPro SSL_Read()

I did find there was an IP address in the "allowed" list... I cleared that out... now the transaction goes through, but I get "payment declined"

I now see the payment in PayPal, but it shows it as declined for "TERM ID ERROR"

But its good that it is actually reaching payflow... and paypal keeps asking for the API request and response...