CiviCRM Community Forums (archive)

I'm having some strange issues with Authorize.net and I'm a bit panicked because this is our biggest online fundraising week of the year, and I think we're already losing donations. Ahhh!

This is a new problem that, as far as I can tell, has started this morning:

• Our server and website are humming along just fine and all pages are zippy
• BUT when donor clicks the "Make contribution" button at the final step, the button turns to "Processing..." and sometimes stays there for a very long time before completing. Sometimes it completes right away, like normal. But I've spoken to multiple donors on the phone this morning who say they have waited up to 2 minutes before it has finally completed.
• This delay leads many people to press the back button or start over. And then they end up being charged twice. When I look through our unsettled transactions from this morning, there are lots of duplicate names. I've spot checked some of them in Civi, and sometimes the duplicate transactions end up getting recorded back in CiviCRM, but sometimes they don't. So, people are noticing already that they're getting duplciate email receipts for their donation and calling in, confused.

I tried a few live transactions myself that I will later void, just to test it out. One went through, without any issues, and on another one, I got a very strange error message after I clicked "Make contribution":

Payment processor error
56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104

This message showed up at the top of the form to make the contribution, so I never got to the thank-you screen. AND the payment went through in spite of the above error message. Very strange. Do you think that message is coming from Authorize.net or from Civi?

Can anyone help me figure out what might be happening here?

I've called Authorize.net and they've escalated a ticket but they seem to think the issue is on my end. They tell me that the strange error message above did not come from Authorize.net but must have come from Civi. But I have nothing abnormal in my Civi log file.

Authorize.net is asking me if there's a way I can find the exact response I'm getting from Authorize.net for these strange transactions. Is there a way I can quickly hack Civi to log the error message?

Update for anyone else who may be curious about this...

Now it's day 2 and it seems that this issue was (thankfully) isolated to yesterday morning. I still can't explain it, but I think it was probably Authorize.net's fault. Despite my numerous calls, they have been frustratingly taciturn and just keep telling me they're "looking into it". I had to void about a dozen extraneous transactions and talk on the phone with several donors to mollify their frustrations.

Quite a mess, but at least the issue seems to have stopped!