node-slack-sdk: 404 when attempting to use sendMessage in RTMClient
Description
Issue when sending messages using the rtm.start()
function. 404 being raised.
What type of issue is this? (place an x
in one of the [ ]
)
- bug
- enhancement (feature request)
- question
- documentation related
- testing related
- discussion
Requirements (place an x
in each of the [ ]
)
- I’ve read and understood the Contributing guidelines and have done my best effort to follow them.
- I’ve read and agree to the Code of Conduct.
- I’ve searched for any related issues and avoided creating a duplicate issue.
Bug Report
As of yesterday the rtm-client seems @slack/rtm-api
seems to be returning a 404 each time it attempts to connect to slack.
const {RTMClient} = require('@slack/rtm-api');
const rtm = new RTMClient(SLACK_TOKEN);
rtm.start();
Packages:
Select all that apply:
-
@slack/web-api
-
@slack/events-api
-
@slack/interactive-messages
-
@slack/rtm-api
-
@slack/webhooks
- I don’t know
Reproducible in:
package version: 5.0.3
node version: 10.15.3
OS version(s): Linux
Steps to reproduce:
Run the following code.
const {RTMClient} = require('@slack/rtm-api');
const rtm = new RTMClient(SLACK_TOKEN);
rtm.start();
Expected result:
Expect for us to be able to use the RTMClient
Actual result:
404 is raised.
[ERROR] RTMClient:1 A websocket error occurred: Unexpected server response: 404
[ERROR] RTMClient:1 A websocket error occurred: Unexpected server response: 404
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 4
- Comments: 17 (6 by maintainers)
We’re sorry for the errors and thank you very much for your patience. As it seems to be all good, please allow me to close this issue.
We believe we’ve identified the issue on the Slack server side. I’ll update this comment when the fix is rolled out.
Update: We rolled back a change we think caused this issue. Please retry now and report back what you find so we can get some more confidence in the fix.
cc @elbuo8 @piyushgupta27 @thepont
@piyushgupta27 @thepont are you guys deploying by any chance in Australia?
We are facing this same issue exclusively in AU.