search

alphanodes / redmine_messenger

Messenger plugin for Redmine with Slack, Discord, Rocket.Chat and Mattermost support
https://www.redmine.org/plugins/redmine_messenger
Other
174 stars 58 forks source link

Rocketchat integration no longer working #95

Closed Trans-IP closed 2 years ago

Trans-IP commented 2 years ago

For a few months now my plugin has stopped working and I have just started looking into it more deeply.

See: https://github.com/RocketChat/Rocket.Chat/issues/23208 for context.

I keep getting"status":400 on the response from the server once the payload is sent. I upgraded to the latest version of the plugin and upgraded the rocketchat server serveral times with no change in behaviour.

Rocketchat Version 4.3.0 Apps Engine Version 1.29.0 Node Version v12.18.4 Database Migration 252 (December 29, 2021 4:12 PM) MongoDB 5.0.5 / wiredTiger (oplog Enabled)

alexandermeindl commented 2 years ago

I cannot reproduce this problem. I use Rocket.Chat 4.3.0 with latest redmine_messenger without problems. Please check your settings for incoming hooks in your Rocket.Chat configuration (e.g. permissions).

Trans-IP commented 2 years ago

Thanks for the reply. I hadn't changed anything when it broke, only did an upgrade of the Rocketchat server. The integration seems standard and the users etc all exist. Let me see if I can find something else.

alexandermeindl commented 2 years ago

Some Rocket.Chat updates before, we had to adjust permissions in our Rocket.Chat settings - because it did not work anymore for incoming hooks. Don't ask me what permission that was. On redmine_messenger side we cannot solve your problem. Maybe you find something in Rocket.Chat Changelog about it.

Trans-IP commented 2 years ago

This is what I see as Permissions (the user is a bot and doesn't have the first 2):

image

And this is what I see as Settings:

image

Trans-IP commented 2 years ago

Thanks for the hint. I found the solution based on a release note:

https://github.com/RocketChat/Rocket.Chat/releases/tag/4.0.0-rc.4

Basically the user controling the webhook needs to be part of the channel and in my case that wasn't so.

All fixed!