Slackbridge Messages going to non-existant channelID

Description

Messages posted to the Slack channel are coming to Rocket.Chat server as can be seen above but they are posting to a channelID: C015ZJEUKLZ. That channel does not exist (where is it trying to post?) and it can’t add the channel. The bot shows offline even though auth is obviously happening and the bot is in (though offline) a channel.


Jul 1 22:17:09 localhost rocketchat[1000]: server.js:199 SlackBridge ➔ Slack.debug OnSlackEvent-MESSAGE: { client_msg_id: ‘03bf3170-7a80-4661-9d35-681ad9d8e3ed’,
Jul 1 22:17:10 localhost rocketchat[1000]: suppress_notification: false,
Jul 1 22:17:10 localhost rocketchat[1000]: type: ‘message’,
Jul 1 22:17:10 localhost rocketchat[1000]: text: ‘some day’,
Jul 1 22:17:10 localhost rocketchat[1000]: user: ‘U015PA9VC1H’,
Jul 1 22:17:10 localhost rocketchat[1000]: team: ‘T011RV6FE67’,
Jul 1 22:17:10 localhost rocketchat[1000]: blocks: [ { type: ‘rich_text’, block_id: ‘CWEN’, elements: [Array] } ],
Jul 1 22:17:10 localhost rocketchat[1000]: source_team: ‘T011RV6FE67’,
Jul 1 22:17:10 localhost rocketchat[1000]: user_team: ‘T011RV6FE67’,
Jul 1 22:17:10 localhost rocketchat[1000]: channel: ‘C015ZJEUKLZ’,
Jul 1 22:17:10 localhost rocketchat[1000]: event_ts: ‘1593641829.080300’,
Jul 1 22:17:10 localhost rocketchat[1000]: ts: ‘1593641829.080300’ }
Jul 1 22:17:10 localhost rocketchat[1000]: server.js:199 SlackBridge ➔ Rocket.debug Adding Rocket.Chat channel from Slack C015ZJEUKLZ
Jul 1 22:17:10 localhost rocketchat[1000]: server.js:199 SlackBridge ➔ Rocket.debug Channel not added
`

Server Setup Information

  • Version of Rocket.Chat Server: 0.74.3
  • Operating System: Linux
  • Deployment Method: tar
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Disabled
  • NodeJS Version: v8.11.3
  • MongoDB Version: 3.6.3
  • Proxy: apache
  • Firewalls involved: no

Any additional Information

Followed standard guide. This at one point worked for a different Slackbridge however could only receive but not send from Rocket.Chat. That Slack instance changed and I am using the new API key and bot username.