-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep getting ETIMEDOUT errors / warning messages #2185
Comments
Hi, @SEEWON! Thanks for submitting this 😄 To confirm - you're getting the |
Hi @hello-ashleyintech 😊 Correct. My code is just normally using axios to call HTTP POST method as below:
In fact, same code as above had no problem during times from last year, Strange thing is that request is not always failing, it fails like once when i make 10 to 20 request in 10 minutes.
|
Hi, @SEEWON! 😄 thanks for sending that additional info over. Based on the code provided, as well as it seeming that the timeout errors are intermittent and usually occur after a large amount of requests are placed in a short span, I would suggest trying to add a Hopefully that should help with the timeout failures! Let me know if you continue to run into issues! 🙌 |
Hello @hello-ashleyintech, Diane here from @SEEWON's team. Thanks for letting us know about the I have modified the
as you can see, I have added the After this modification, the Right now, I am reusing the Here is the full error log:
Is this simply an issue of too many requests being thrown? Two things that are also bothering me is that What could be the issue here? |
Hello @hello-ashleyintech, to follow up - I got this error message this morning. along with the |
👋 Marked this as I shared a few troubleshooting suggestions in #2212 but the one I am most curious about is updating the Bolt version to |
Hello, checking in here. Is this still a problem for you @SEEWON @dianexjeong ? Another idea here: are you using a proxy? |
I believe we can combine / merge this issue with #2212 :) |
Yes that makes sense to me as well. Closing and let's continue in #2212. |
Hi there, I'm getting warnings / errors from bolt.js.
@slack/bolt
version^3.19.0
Your
App
and Receiver ConfigurationNode.js runtime version
v18.17.1
Steps to reproduce:
Just by sending HTTP POST request to Slack API Webhook URL, with axios (like "https://hooks.slack.com/services/TXXXXXXXXXX/BXXXXXXXXXX/abcd1234": details masked)
Expected result:
No warnings, nor errors while sending HTTP POST request, message sent to slack.
Actual result:
Getting warnings, then ETIMEDOUT errors. (No message sent that should be sent)
Errors are all from
35.73.126.78:443
/35.74.58.174:443
/52.192.46.121:443
/52.196.128.139:443
IPs.Just figured out those IPs are from AWS, Tokyo region (seem to be slack's, same with result of
nslookup https://hooks.slack.com
)Logs below are example for the warning, errors i've got from my server.
2024-08-05 19:07:13: [WARN] bolt-app http request failed connect ETIMEDOUT 52.192.46.121:443
2024-08-05 18:49:53: [WARN] bolt-app http request failed connect ETIMEDOUT 35.74.58.174:443
AxiosError: connect ETIMEDOUT 35.74.58.174:443
...
This warnings/errors are keep coming out since July 25th.
(fyi. There was no problem before July 25th, same code with was running since January, but the error started coming out since July 25th)
Is something broken with bolt.js or Slack API?
Requirements
For general questions/issues about Slack API platform or its server-side, could you submit questions at https://my.slack.com/help/requests/new instead. 🙇
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
The text was updated successfully, but these errors were encountered: