Well, it looks like we might need to switch hosting service. Before I do that, I want to try one more time.
Here is an email I got back from Authorize.net.
Greetings from Authorize.Net!
When Authorize.Net is responding back to a script on your server our system waits 10 seconds for a response. If we do not get a response in 10 seconds, our server will time out and display an error page. In this case the customer will see the transaction results on an error page that Authorize.net generates.
If this happens we will either send an email to you indicating: "An error occurred while trying to report this transaction to the merchant. An email has been sent to the merchant informing them of the error. The following is a result of the attempt to charge your credit card"
or
The transaction will be declined within your Merchant Interface. The transaction detail will display (Unable to send notification to Customer).
If the customer closes the browser window before we receive data from your script to print to the screen we will change the transaction response reason code to 52.
To prevent these errors the first thing that you will need to look for is the order that your script executes. It is very important that something is printed to the screen before any other process is started. If your script prints to the screen first, we will recognize that you have received the transaction results.
To resolve this issue:
- Before doing anything else start writing to your receipt page. For example: print your page headers and the first part of the page body.
- Check that your script permissions are correct and that it can accept an HTTPS POST.
- Check that the script is not completing other functions before writing to the screen, such as writing to a database or sending emails.
- Please check to see if there are different processes that are used in your script for approvals, declines, or errors. Check each process to be sure that they will write to the screen before any other functions.
- Verify that your script is not using redirects upon receipt of the response from our servers. Redirects strongly are discouraged because they can potentially interfere with the process.
Does any of this make sense?
The only thing I can possibly think of is that it might have something to do with the Permissions I have set. As I said earlier the server would not let me change the Permissions to 777 (as the installation instructions say to), they are currently at 775. It still won't let me change them. Could this be a factor?