API Timeout issue

Hello!

It looks like the Square syncs we have running on our server are failing from time to time due to time out (connect ECONNREFUSED 74.122.189.132:443). There seems to be no issue when running from a local machine (which has different IP).

Could this be something on the Square side? Are we hitting some sort of threshold? Is there some IP restriction?

Any help would be appreciated.

Thank you!

Hi @john1 welcome to the forums!

Do you have specific date/times when this happened? Also what is your Square app id?

This shouldn’t happen often, but it’s possible a hiccup happened on our server-side and your app was unable to connect. However, since you mention it connects fine from a local machine, is it possible that you have some sort of firewall or other network tool that is blocking the connection?

Thanks for the quick reply!

Our app ID is sq0idp-L2a2QpfEPra8cUP0DwccDA

This has been going on for over 12 hours now. We’re looking into network issues, but nothing so far. It would be great if you can confirm all is good on your side regarding our app.

Thanks for your help

Hey @sjosey, I’ve been having this all day as well, on multiple endpoints. I haven’t been able to track down anything on my end yet. App id: sq0idp-mtW6FLMC5GPLXz6-dbeZbg

Just out of curiosity, do you happen to use some known hosting provider for this, or run it on your own? Thank you

I’m on Digital Ocean

Hmm, so am I… Perhaps it’s worth reporting there as well as it might be something in their network

Good to know, thanks. I’ll report there as well.

Good to know, thank you both for confirming that. I’m following up with our internal network team but so far have not come across anything obvious. Please if either of you hear back from Digital Ocean let me know here if it was an issue, as I’ve received a similar report on another medium (besides forums).

Would you folks be able to share what Digital Ocean region your droplets are in? Are you able to provide any trace routes as well?

We are on FRA1 (Frankfurt)

Assuming this is what you meant:

traceroute 74.122.189.132
traceroute to 74.122.189.132 (74.122.189.132), 30 hops max, 60 byte packets
1 * * *
2 10.68.67.213 (10.68.67.213) 0.806 ms 10.68.67.233 (10.68.67.233) 0.773 ms 10.68.67.213 (10.68.67.213) 0.763 ms
3 138.197.249.32 (138.197.249.32) 5.468 ms 138.197.249.38 (138.197.249.38) 0.921 ms 138.197.249.40 (138.197.249.40) 1.005 ms
4 138.197.250.137 (138.197.250.137) 2.115 ms 138.197.250.149 (138.197.250.149) 2.037 ms 138.197.250.141 (138.197.250.141) 0.815 ms
5 akamai.prolexic.com (80.81.193.70) 1.535 ms 1.533 ms 1.527 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

All is fixed now, thank you!

Our team was able to resolve something on our side, thank you both for reporting.

1 Like