-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Unrejectable invite from oftc room #8091
Comments
By the way: There you can see the server version used on the other server: |
I'm unsure if you have access to the server logs or not, but if you do it would be interesting to see the errors in the above situations. I see three spots that might be useful:
This sounds somewhat like #2181, but that was fixed in 1.17.0. |
Hi @clokep, I am running this server and I will provide the relevant lines from synapse log:
|
I just upgraded to synapse 1.19.0. This changed the error in the log to
|
Trying for a few times the above exception did not occure anymore, but I just get the following log-line
And some minutes later:
|
@clokep it's possible that the matrix.org logs might be enlightening on this issue. |
update: just got the invitation from r3bot (more than 12 hours later). I accepted without problem (no loop like @Flexmaen), but nothing more happens, ie. I am never joined to the |
Looking at the logs from the 520 error:
Is it possible that this response was just really slow (~48 seconds) and that's why Cloudflare returned an error? The 520 error seems to be a Cloudflare error:
It seems Cloudflare is having issues, but that does not seem related since it is recent: https://www.cloudflarestatus.com/incidents/xz2rwk8gsbyp |
It seems that matrix.org had been having some issues handling incoming federation over the past couple of days. I'd be curious if this is working better today. |
That's the log of @Flexmaen's join attempt
|
@clokep I am not sure if this is a general federation problem at matrix.org but just (or at least) with matrix.gemeinsam.jetzt. I joined from another homeserver (matrix.g24.at) without any problems within some seconds. |
I can confirm this issue on matrix.teckids.org, using synapse 1.19.0. |
I had a look at matrix.org's logs and it looks like it's also a case of a timeout before the HS responded:
Can you check your server's logs (if you have access to them) to see if there's a |
It sounds like most of these issues are due to matrix.org responding to |
I am surprised this leads to a stuck invite. Even if the join fails, you ought to be able to reject the invite? |
I've changed the name of the issue because it better matches what the reporter is describing. I don't know for a fact that it causes a stuck invite, as I can't see any On top of that, it's unclear what happens when an attempt to reject the invite is made, @mir06 would you be able to provide logs of what happens then from your side (as clokep asked) please? |
Is increasing the join timeout something I can do on my HS? |
Related: #7671 |
It's really unclear what this issue is about. There seem to be at least three different problems:
since the first issue is known, and @babolivier has changed the summary of the issue to "Timing out on send_join leads to stuck invites", I suggest we use this issue to track the second problem: the stuck invite. @Flexmaen: please share logs from your server when an attempt to reject an invite fails. People struggling to join rooms: sorry :/. We're planning a focus on making joins over federation suck less (#7671) within the next few months. In the meantime, I can't really suggest much other than being patient. |
Since I get the messages in German I don't know the exact message I'd get in English. So my error messages are rough translations that should transport the meaning of the mssage.
It's the server of @mir06 who does not always seem to get the same result. So I'll try to join again and he'll post the log.
Thank you. |
Hi,
|
While searching for the "Not a known user"-related lines in the logs I retried to join myself and got another exception:
|
ok, I'm not seeing any attempts to reject the invite there. As I said earlier:
please note: reject an invite. The fact that a join times out or sometimes fails with a 500 is a known issue. |
It seems that I don't get the accept/reject-dialogue anymore. At the moment i get the error message like shown above but afterwards just get the option to click on a "try again" button. |
ok I'm going to close this because the fact that joins can fail is known, and I'm not seeing any evidence of invite rejections failing. |
Sorry, I could not follow this issue the last days.
Accepting leads to this error in the synapse log:
|
Bye the way, I can leave this loop by clearing the cache in |
@richvdh ok it seems that this is reproducable. That bot is an IRC-Bot. |
please can you share all the logs from the homeserver, between the invite being received and the failure to reject. |
@richvdh yes I can do this but I do not have time before Wednesday. I will post it here! |
I cannot provide the entire logs as my last try to join the room is more than a week ago. And just a couple of minutes ago I got the invitation from r3bot (PM on irc.oftc.net). Clicking Accept or Reject leads to the same behavior as described above (also the server-logs). Probably the bot really does not exist anymore when the invitation takes that long. |
please share the complete server logs between the invite arriving and your attempt to reject. |
closing for lack of useful logs. |
Similar problem via Mozillas Matrix-Server. Maybe a problem of the OFTC bridge? Is it possible to re-open this bug on the right place? |
On |
This issue is super unclear. If you are still seeing problems, I suggest opening new issues. Please note:
|
This bug was reportet here and here.
However it seems to be a server issue, so I report it here:
Description
I'm using a third party matrix server (here) and tried to
join #_oftc_#realraum:matrix.org
which causes an undefined error.However,
@_oftc_r3bot:matrix.org
tries to contact me afterwards. I can neither accept, nor ignore this. ("Denieing failed. Not a known user). So I'll stuck in the invitation loop, and always have 1 unread message.Steps to reproduce
The result was not the same everywhere, but it caused different issues:
/join #_oftc_#realraum:matrix.org
Describe how what happens differs from what you expected.
You'd be able to join the room.
However if this does not work because of some server issues (maybe this is a synapse bug?), Element-Web should not be stuck in this kind of invitation-look.
Version information
For the web app:
The text was updated successfully, but these errors were encountered: