Matrix-appservice-irc: (IRC) Bridged channel not showing bridge attachment -- impossible to "un-bridge"

Created on 20 May 2021  路  11Comments  路  Source: matrix-org/matrix-appservice-irc

Describe the bug

The #ledgersmb:matrix.org channel is bridged to FreeNode/#ledgersmb, but when going through "Widgets, bridges & bots", the "Existing integrations" don't list IRC integration.
Additionally, selecting "Add Integrations" > "Bridges" > "#IRC" shows a dialog which says "No IRC channels integrated".

To Reproduce

See above.

Expected behavior

I would have expected "#IRC" to be listed under "Existing integrations" or I would have expected the existing integration to be listed as an existing integration while adding a new integration.

Desktop (please complete the following information):

  • OS: Linux
  • Browser Firefox
  • Version 88.0.1

Additional context

None

bug needs-investigation

All 11 comments

It's possible that this might be a alias channel originally / not created via the integration manager OR you might not have permissions. I'll double check for you.

We're in the same boat with #calyxos:matrix.org (bridged to freenode #calyxos)

I do see #freenode_#calyxos:matrix.org listed under "Local Addresses" on this.

Additionally, the only Admin is @appservice-irc:matrix.org

@Half-Shot You are correct.

ledgersmb:matrix.org was created long before the integration manager

Looks like I have the same issue with #sbts

Same for https://app.element.io/#/room/#prometheus-dev:matrix.org and https://app.element.io/#/room/#prometheus:matrix.org. We would like to un-bridge both rooms from Freenode (before later bridging to Libera once that's set up), but I think @Half-Shot set this up for us initially in a way that we can't undo ourselves. Could you help us out again? :)

I'm not sure my problem is exactly the same but it was similar--I was unable to remove the freenode bridge because it said "channel is not public".

The freenode takeover had propagated permissions over from freenode and made my matrix channel invite-only. Once I fixed it away from being invite-only, the integrations manager started working again. I was able to unlink the freenode bridge. This might be a useful workaround for others affected. Even if it doesn't fix the integrations manager, you probably at least want to fix the invite-only bit; I missed that this had gotten set in the takeover.

Hope that helps.

FYI: On our (Prometheus') side, we got some helpful private assistance by the Matrix team, so we're all good and unbridged now.

I was able to send a tombstone event to the bridged room using the script at https://gitea.blesmrt.net/mikaela/scripts/src/branch/master/bash/matrix-tombstone-room.bash and then have everyone migrate to a new room.

appservice-irc did join the new room but I was able to ban it, however somehow even this new room is still bridged to freenode (messages got across, users showed up on both sides) - I muted the freenode channel for now.

however somehow even this new room is still bridged to freenode

I confirm that. I kicked appservice-irc but messages were still coming in.

@Half-Shot I have the same problem with the #common-lisp.net channel. It's my understanding that the LiberaChat bridge is now operational, so pressure may now be dropping a little bit. I hope you can find some time to look at this issue. If so, that would be greatly appreciated.

@Half-Shot I appreciate these are busy times, any news though?

Was this page helpful?
0 / 5 - 0 ratings