#12430 Automatically invited ChanServ channel is unjoinable.
Closed: Fixed with Explanation 17 days ago by kevin. Opened 17 days ago by rokejulianlockhart.

Problem

As matrix.to/#/!vufZJPUoXUExEXBPbA:matrix.org/$Gbqj81W_SJshe6_jaOabKFtUPDyFKADaN_pMqx5MJN4?via=fedora.im and its predecessors explain:

I saw at accounts.fedoraproject.org/group/fedora-join that this chat has a libera.chat IRC counterpart, and see in my invites here in Element that I've been invited by ChanServ to a bridge between them. I'll presume it's courteous for me to accept it because those using IRC can participate, but I'm not actually able to:

MatrixError: [502] Failed to make_join via any server (https://fedora.ems.host/_matrix/client/v3/join/!RoPGRJHCGVTyEkFheh%3Alibera.chat)

A screenshot is available at discussion.fedoraproject.org/t/146323.

If of use, the channel is chat.fedoraproject.org/#/room/!RoPGRJHCGVTyEkFheh:libera.chat, and I am @rokejulianlockhart:fedora.im.

Describe what you would like us to do:

Investigate whether this is widespread, and if so, remediate it.

When do you need this to be done by?

(YYYY/MM/DD)

≥ 2025

(Lack of) Duplicates

issues?status=Open&search_pattern=chanserv&priority=0&close_status= returned 0 results at +2025-02-28T15:412:06+00:00[Europe/London][u-ca=iso8601].


/4 states:

There is no IRC bridge to libera.chat anymore.

Right, bridges were removed a while back. If there's anything mentioning them it needs to be fixed.

I have fixed the join channel mention in the account system.

See https://communityblog.fedoraproject.org/matrix-to-libera-chat-irc-bridge-unavailable/

Metadata Update from @kevin:
- Issue assigned to kevin
- Issue tagged with: low-gain, low-trouble, ops

17 days ago

Metadata Update from @kevin:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

17 days ago

If there's anything mentioning them it needs to be fixed.

@kevin, in my case, I presume that I was invited a while ago (Element's GUI doesn't appear to expose when) but I didn't notice it until now, after the bridge has become unavailable.

Perhaps it'd better to suggest that Element improve the error message, but I doubt I know enough to write an actionabnle report.

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog