Posted: November 8, 2023 at 6:16 pm
|
Hi – at around 4pm people who try to purchase a ticket when they click the Proceed to Finalize button it jumps to the top of the page or does nothing. In the EE authorize.net logs it just says Error connecting to Authorize.net. I tried logging into authorize.net and renewing the Transaction key and Signature Key with no joy. WordPress Version: 6.3.2 |
|
I see that you tried to purchase a ticket, I have authorize.net set to sandbox mode so you can try with [09-Nov-2023 05:17:18 UTC] PHP Warning: session_start(): open(/var/cpanel/php/sessions/alt-php74/sess_8d4fc57c7ca1175c4109210830c4dc2f, O_RDWR) failed: No such file or directory (2) in /home/pathlight/public_html/wp-content/plugins/event-espresso-core-reg/core/services/session/SessionStartHandler.php on line 65 The hosting company said there was a DDoS attack but my programmer doesn’t think that’s related. |
|
The web host has corrected the sessions saving issue, but the authorize.net connection is still failing. |
Hi there, Your using Auth.net AIM so the communication between your site and Auth.net is don’t in the background via your server using a POST request, that request is failing completely with no response at all for you to get the above error. Before we start troubleshooting that further, may I ask why you have chose to use AIM? There’s 2 reasons I ask, firstly onsite payment method integrations like AIM have the highest PCI Compliance lvl requirement. Second Auth.net hav Deprecated the AIM integration method and whilst they have stated it should continue to work, they are no longer actively developing that integration which means I would recommend switching to the Auth.net Accept payment method: |
|
|
I purchased and installed the plugin, set it up in sandbox mode and it goes to failed without giving me the option to add credit card info 🙁 |
|
It’s fixed, the problem was a setting in the data center. I would like to get a refund for the Auth.net Accept plugin, that didn’t work at all. |
I have submitted your refund request to our sales team. If the data center were blocking/blocked connections to Auth.net’s servers the Auth.net Accept payment method also wouldn’t be able to connect, which may explain why it didn’t work for you. I still recommend switching over to Accept as the AIM integration method has been deprecated by Auth.net themselves, once its becomes end of life the integration will not long function (although there is no currently clear indication of when Auth.net will do that). |
|
The support post ‘Authorize.net suddenly not working’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.