Authorize.net SIM errors since Server move?

M

microweb

Perch
Is anyone else experiencing server time out issues with authorize.net's SIM method? Ever since our server move, authorize.net is generating a time out error.

I know that authorize is communicating with our relay URL because the code to update our database runs successfully, the page itself just never gets displayed on the screen. Instead, authorize generates an error. The credit card processes normally and all of our data is correct. The end user just sees a plain white page with a notice that an error occurred.

-Carol Paprotna
Microweb Design
 
Haven't you moved your site to the non cloud server now? I know you were getting timestamp issues due to it not really doing timestamp but a tick counter comparison which is thrown off by the hypervisor.

So I am pretty sure that would not be the same issue there, the IP has changed each time, do you have to add an authorized IP in the auth.net gateway setup (sorry I don't have access to such to know myself)
 
I haven't moved it yet because we can't take the entire site down for 24 hours at this time. It also requires reinstalling all SSL certificates and recreating of all FTP accounts. I need to schedule this at a more convenient time.

In the mean time, I wanted to see if the other issue could be related to the servers or something else. If it is happening to other people, then hopefully it will be resolved when we move to the non cloud server. If not, then maybe it is completely unrelated and I need to spend time to resolve it now.

-Carol
 
microweb said:
I haven't moved it yet because we can't take the entire site down for 24 hours at this time. It also requires reinstalling all SSL certificates and recreating of all FTP accounts. I need to schedule this at a more convenient time.

In the mean time, I wanted to see if the other issue could be related to the servers or something else. If it is happening to other people, then hopefully it will be resolved when we move to the non cloud server. If not, then maybe it is completely unrelated and I need to spend time to resolve it now.

-Carol
Click to expand...

There is no down for 24 hours, it simply takes 24 hours - 48 hours from start of move(sites live on both servers till a full DNs handover), reinstalling ssl can be done with an export before it is even live on the new, and FTP accounts are only those added by hand in the past, not with the new framework(last 2 years), if just having one FTP account it will be fine, if having others within hsphere they will move too.


i still think the timeout issue could be something to do with an 'ip whitelist' or something of the sort at the gateway, used as a way to sort legit transaction sources from possibly rogue.
 
But do I need to reinstall the SSL or will whoever is doing the move take care of that for me?

I must have misunderstood their response when they told me what it would entail.

-Carol
 
microweb said:
But do I need to reinstall the SSL or will whoever is doing the move take care of that for me?

I must have misunderstood their response when they told me what it would entail.

-Carol
Click to expand...
We can reimport the SSL for you.
 
Thanks Stephen, I will contact support to ask them to do the move over the weekend.

You have always been so helpful and quick with your responses here. It is much appreciated.
 
You must log in or register to reply here.
Back
Top