Customizing connect timeout (Failed to connect to Recurly.)

[BobuSumisu]

I was setting up Recurly for the first time and had some problems figuring out why nothing worked.

It turned out to be the (rather low?) connect timeout option to curl. I don't know if there is something wrong with my local setup or recurly is just slow accepting my connection right now, but I changed the 10 seconds to 30 and now everything is working smoothly (slow but smoothly :P).

I do not like editing vendor libraries directly and just wondered why this is so low, and if it was possible to make this customizable in a 'pretty' manner?

[mbeale]

@BobuSumisu

10 seconds should be more than enough to connect to recurly. Most GET requests respond quickly and there might be delays when updating billing information because Recurly is waiting for a response from the gateway you are using to see if you provided a valid card. 10 seconds should provide you with extra cushion. I would say requests probably would not take more that 5 seconds tops.

Currently the only way to edit this would be to manually change the code.

Have you tried manually using curl -v to see where the hold up is? Could be name lookup, transfer time, or connection related issue.

Or you could use this function in PHP to help.
http://php.net/manual/en/function.curl-getinfo.php

[BobuSumisu]

Tested the same application on the same laptop but on another network: it worked instantly.

I suspect there are some hickups with my laptop/router combination at home then.

Thanks for the information though - it will be used to debug my home setup :)