Open tuncbkose opened 3 years ago
I think I'm also seeing this issue
It may be worth checking to see if your user regex in your registration file matches https://github.com/matrix-org/matrix-appservice-slack/blob/develop/config/config.sample.yaml#L30, as that would cause the error linked.
The logs also indicate that you are looking for @slackbot:localhost
which doesn't map to Loading room entry !********:domain.tld
, so your domain in your config might be wrong.
I was seeing similar behavior, and I finally figured out the problem. In my case it was because I had specified the homeserver.server_name
parameter as matrix.example.com
, when what works is instead to set this to the domain associated with the slackbot Matrix ID, which is example.com
(assuming you have configured your homeserver in the typical way such that Matrix IDs do not include the matrix.
prefix people typically prepend to their homeserver URL). The similar error messages I see about the slackbot username being already taken and messages about failing to load the user profile do not seem to prevent the bridge from working.
Not sure what labels to give to this as it seem to be an issue with the configuration.
I'd call it a documentation bug, given this could probably be solved with more specific language
Describe the bug Slackbot doesn't accept invites.
Expected behavior Slackbot accepts the invite.
The last info message is in response to invitation/disinvitation so the app is working. Thinking that this and "User ID already taken" are related, I tried editing
slack-registration.yaml
to change the name from slackbot to something else but it gave a different error:Edit: This is with the latest release.