Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Failed to join room" against Synapse 1.12.0 #40

Open
cvincent opened this issue Mar 27, 2020 · 7 comments
Open

"Failed to join room" against Synapse 1.12.0 #40

cvincent opened this issue Mar 27, 2020 · 7 comments

Comments

@cvincent
Copy link
Contributor

Last night I began the process of moving my homeserver off my media server to a new server dedicated to various cloud applications (so the media server can dedicate all its resources to transcoding). This meant getting my lovely iMessage bridge moved as well.

I ended up in a situation where I could receive but not send messages. After many frustrating hours of debugging, I realized my new homeserver installation was of course using the latest version (1.12.0 as of this writing), while the previous installation which had been working was on 1.9.1. So I rolled back to 1.9.1, started everything from scratch, and now I'm back in business.

Here's the error I see (phone number edited out) when running against 1.12.0: failed to join ghost +XXXXXXXXXXX Error: Failed to join room.

I don't know which precise Synapse version breaks it, only that 1.9.1 works and 1.12.0 doesn't. It's possible the issue isn't in the iMessage bridge itself, but in the underlying library it uses to connect with Matrix.

@cvincent
Copy link
Contributor Author

@nr23730
Copy link
Member

nr23730 commented Mar 30, 2020

Did you use the latest commit 1bb0385? I fixed the issue there...

@Philantrop
Copy link

Did you use the latest commit 1bb0385? I fixed the issue there...

I'm using a checkout of that commit and am seeing the same symptoms as cvincent. Messages from Matrix are never sent to iMessage but the inverse way works just fine. It started with Synapse 1.12.0 for me, too. It worked with v1.11.0.

@cwmke
Copy link

cwmke commented Apr 2, 2020

Is this for new or existing conversations? I'm on 1.12.0 and haven't noticed any problems with existing conversations. I haven't had any new conversations to test with.

@Philantrop
Copy link

Is this for new or existing conversations? I'm on 1.12.0 and haven't noticed any problems with existing conversations. I haven't had any new conversations to test with.

Both in my case.

@cvincent
Copy link
Contributor Author

Yeah this is a separate issue from what was fixed in 1bb0385 (which is merging in my fix for the other issue).

@cvincent
Copy link
Contributor Author

From a little sleuthing starting from the above matrix.to link, it appears to be related to this issue: matrix-org/matrix-spec-proposals#2261

I'm wondering if simply updating the underlying matrix-puppet-bridge library will make it work against the latest Synapse version. Can anyone confirm? I'd try it but I do rely on my existing setup and don't want to end up in a weird situation that's hard to come back from. Would be great to get some kind of automated testing around bridge integration in general.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants