28 Operation timed out after 15000 milliseconds with 0 bytes received (eProcessing)

[DrByte]

Okay, so that was a successful transaction. No "Operation Timed Out" or any other error messages, not a declined transaction. All looks fine.

[donnyb]

Okay, so that was a successful transaction. No "Operation Timed Out" or any other error messages, not a declined transaction. All looks fine.

Correct as my host has increased the timeout from 15 seconds to 30 seconds. So should I just live with transactions taking up to to 15 to 20 seconds to process? I had one last week that took 26 seconds to successfully process. Is that a problem or could it become one?

They did suggest the VPS I am on may not be well suited for my cart, the specs are below

75 GB Disk Storage
2 TB Bandwidth Transfer
880 MB RAM
1 CPU

From what I have been able to read on google, there are a lot of variables, but some people say that should be fine while others suggest 1 GB of RAM or more.

Thank you for taking the time to look at this and respond.
donnyb

[DrByte]

If it's taking an excessively long time to connect, then that's something that needs to be fixed by the people involved in that part of the communication. Since the communication starts from your webserver, and ends at the eProcessing server, the people to fix the problem are those who look after the servers on both ends, the routers in both locations, and the firewalls that manage the interaction on both ends, and maybe the internet connection your hosting company uses to handle the communications.

15 seconds is indeed unnecessarily long, and most customers will already be confused and worried long before 15 seconds transpires. But some lesser equipped processing gateways are slower. If they're providing the service you want, then stay. If not, find someone who can do it better.

[donnyb]

If it's taking an excessively long time to connect, then that's something that needs to be fixed by the people involved in that part of the communication. Since the communication starts from your webserver, and ends at the eProcessing server, the people to fix the problem are those who look after the servers on both ends, the routers in both locations, and the firewalls that manage the interaction on both ends, and maybe the internet connection your hosting company uses to handle the communications.

Thanks again for your help DrByte.
donnyb