>
>>>This problem is a little vague, but I'm hoping maybe someone has had the
>>>same problem and knows what the solution is.
>>>
>>>I have a BQ Centos server in which a customer is processing credit card
>>>payments through Authorize Net's AIM method. Suddenly about a week ago
>>>it stopped working. There is no error message, the process just hangs
>>>for a while and then eventually goes to the next page but without any
>>>reponse from Authorize Net.
>>>
>>>It might seem that the problem is with Auth. Net, especially since
>>>nothing has changed on the server. But we tried running a script from
>>>another server that also uses auth net (a separate auth net account), It
>>>works fine on the other server, but didn't work on the problem server.
>>>So this would seem to indicate that the problem is with the server.
>>>
>>>I had a similar problem a few years ago on a Windows server and don't
>>>recall the resolution. I do recall that Authorize Net wasn't much help
>>>except to say that the request wasn't reaching their server.
>>>
>>>I realize there isn't much to go on, but I'm hoping just from the
>>>description that someone might have gone through this before and knows
>>>what to do.
>>>
>>
>>Maybe your PHP does not have curl.
>>
>>Maybe the authorize.net account has their Fraud Settings set to only allow
>>connections from a specific IP.
>
>Also, make sure that your transaction key is current. If its been changed
>at authorize.net but notin your scripts, it will fail.
It does have cURL, otherwise it wouldn't have worked before last week. But
I did run curl from the command line to make sure it was still working.
We thought of the key as well. We went into Auth Net and created a new one.
Still no luck.
Strange.