Skip to content
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

Slack Bridge (via Slack App) not working but Legacy API works in one way (from RocketChat to Slack) #32322

Closed
tamasgal opened this issue Apr 29, 2024 · 1 comment

Comments

@tamasgal
Copy link

Description:

We struggle to get the Slack bridge running using the recommended Slack App (cf. #30630). The Slack application works fine according to the Slack testing tools but none of the messages are sent/received on either sides.

We also tried the Legacy API and we are able to see messages on Slack (sent from RocketChat) but no messages on the RocketChat side (when sent from Slack).

Is there any way to debug this? The logs are pretty silent on both sides.

We configured everything as described in #30630 and again, the Slack app testing tool successfully communicates with the app on Slack and test messages are arriving.

We have an HTTP/HTTPS load balancer in front of the RocketChat instance. Is there any other socket communication needed maybe?

We are kind of clueless...

Steps to reproduce:

(create the Slack app as described in #30630)

  1. Enable Slack Bridge
  2. Make sure "Legacy API" is turned OFF
  3. Enter the "Signing Secret" of the Slack app
  4. Enter the "App Token" of the Slack app under "App Tokens"
  5. Enable sending messages in both ways

Expected behavior:

Slack bridge mirrors messages in both ways.

Actual behavior:

No messages are mirrored.

Server Setup Information:

  • Version of Rocket.Chat Server: 6.7.0
  • Operating System: Debian 22
  • Deployment Method: Docker (in a Swarm, behind an HAProxy load balancer)
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: v14.21.3
  • MongoDB Version: 4.4.15 / wiredTiger (oplog Enabled)

Client Setup Information

  • Desktop App or Browser Version:
  • Operating System:

Additional context

Relevant logs:

@tamasgal
Copy link
Author

tamasgal commented May 2, 2024

The missing ingredient was giving app-level token in slack enough permissions.

authorizations:read -> connections:write, authorizations:read

One issue remains: whatever channels are put in SlackBridge Out Channels, those disappear when the settings are opened again. But the connections remain functional.

Another issue: "SlackBridge Out All" lets all users on the IceCube side join all channels on the RocketChat side, no matter if the channels exist on both sides or not. That caused a lot of confusion.

@tamasgal tamasgal closed this as completed May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant