Matrix-appservice-irc: unsafeClient not ready yet error

[jasonblewis]

at LCA2020 we have a few people seeing this message when they try and connect to the bridge to freenode.

The bridge reports unsafeClient not ready yet

this issue results in riot being able to join the irc channel and see what is happening on the channel but unable to send to the channel. when you send a message it appears to send correctly, but it never arrives in the irc channel, with no visible error message.

see attached screen shot

[jasonblewis]

[madduck]

I should note that this happens both with the explicit integration in #linux.conf.au:matrix.org, as well as the implicitly bridged froom #freenode_#linux.conf.au:matrix.org, and it's a problem for a couple of people, while it works for plenty others at the same time.

A little bit more context: we used to have issues with err_reggednick until I removed +r from the IRC channel yesterday. Before that, @appservice-irc:matrix.org would report err_reggednick to some users, but not to others. It's possible that there's a correlation here too, i.e. only those for whom the bridge held a connection to IRC would get the error, whereas those who weren't connected, consequently wouldn't see the error.

Is there a way to force (re-)connection? The screenshot shows various different responses, but there's no !connect or !reconnect, according to the source code.

I should also point out that in the case of @jasonblewis (k-man), we tried !quit, subsequently got kicked out of the implicitly-bridged room, left the chat with @appservice-irc:matrix.org, and started from scratch (having to manually start a new chat with appservice-irc:matrix.org), but nothing seems to have changed.

[mattcen]

I'm experiencing the same issue.

[nazunalika]

I am having the same issues here as well.

14:05 -!- There is no such nick Sokel[m]
14:05 -!- There is no such nick nazunalika

[jasonblewis]

See also #926

[tilosp]

The same is happening to me

[Gnurou]

Same problem, happened as soon as I tried using the bridge. There doesn't seem to be any workaround besides restarting the service, which is not an option unless you are running your own instance.

[vs49688]

Same issue happened to me last night.
In my case I changed my !storepass using a grouped nick instead of a primary one. After this, NickServ stopped responding. Further investigation yielded the same responses seen here.

Various combinations of !removepass and !quit yield no change.

Strangely, !nick is still returning the old grouped (non-primary) username. I can verify it's not in use via logging in with a native IRC client and talking to NickServ that way.

When talking to the appservice user:

$ !nick
Format: '!nick DesiredNick' or '!nick irc.server.name DesiredNick'
Currently connected to IRC networks:
chat.freenode.net as mynick

$ !nick primarynick
You are not connected to the network.

$ !whois mynick
unsafeClient not ready yet

$ !listrooms
You are connected, but not joined to any channels.

$ !cmd DISCONNECT
Error: Possibly disconnected

$ !bridgeversion
BridgeVersion: 0.16.0

It also appears this bloke's been hit by the same issue: https://github.com/matrix-org/matrix-appservice-irc/issues/1006

[ocdtrekkie]

Definitely unable to get the IRC bridge working with Freenode as a new user. Seeing the exact behaviors described here.

[tionebrr]

I tried, and tried, and tried, and tried...

At least I'm not alone :)

[Gnurou]

For me it started working again a few days ago (I guess because the bridge has been restarted or something?). I have been able to use the service normally since then.

The issue mentioned above ("Reconnect after !storepass, even if the user isn't in any channels") seems to imply that the service will reconnect if you are in a channel, maybe try to join any channel and do a storepass again?

[tionebrr]

I cannot join any IRC channel. I get kicked with Reason: IRC connection failure.

[tionebrr]

Found where my problem might have been coming from. I had two '!' exclamation points in my password. It was also causing problems with weechat. I changed my pass to something simpler and was able to connect on Riot also.
This password was working with kiwi and pidgin.

[benbullard79]

I'm experiencing the issue exactly as described in first two posts.

[benbullard79]

!cmd chat.freenode.net PING
Error: Possibly disconnected

So far !quit command will not force bridge to quit. It returns nothing exactly as is it were "Possibly disconnected"

And the other commands in second post bring the same results.

[benbullard79]

My problem seems to have healed itself.

Faith healing?

[ailin-nemui]

this is still happening. the missing failure indication of sending messages is most confusing. sometimes it self-heals after many hours...

[jchv]

Looks like it's still happening. Unfortunately, it hit me as a very new Matrix user, the first time I tried to use the IRC bridge. Is it possible I did something wrong?

[nekr0z]

Still an issue.

[tilosp]

@nekr0z does !quit output anything?

[jchv]

I can say that !quit does not work or output anything in my case.

[nekr0z]

@nekr0z does !quit output anything?

Nope, no reaction to !quit at all.

[tilosp]

Then this will remain broken for you until the next restart of the bridge, normally !quit should output You are not connected to any networks. the second time you run it.

I have a PR open, that should at least allow you to disconnect using !quit and reconnect afterwards.

[nekr0z]

So, this morning I tried to check if the bridge got restarted and I could use IRC in Matrix.

Oops, that makes sense, let me log out of the IRC client first and try again...

Hmm... Really?

Again? Yes. Again. Since this, all the same symptoms as yesterday.

Is it some kind of prank?

[Nuc1eoN]

I just installed Riot and I am hitting the same issue.

The real PITA however is, that messages appear to be send!

I was lucky to still have hexchat open aside, which allowed me to notice that my message are actually not being sent to the IRC channel.

This means that we can never be sure if Riot actually sends our messages, because there is literally no indicator.

[slondr]

Can confirm that I also am having this issue now

EDIT: Specifically, I am getting this error when I try to set a nickname. I'm not getting any further than that.

[Half-Shot]

This should hopefully have been fixed in #1098, is anyone still experiencing this on matrix.org?

[Half-Shot]

The voices in my head say no.