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

matrix.org reports failures #20

Open
richvdh opened this issue Jan 19, 2021 · 5 comments
Open

matrix.org reports failures #20

richvdh opened this issue Jan 19, 2021 · 5 comments

Comments

@richvdh
Copy link
Member

richvdh commented Jan 19, 2021

I'm not really sure if this is matrix.org's fault or the voip tester's; if it's the former then it seems pretty bad if the primary public server isn't getting this right:

On Chrome:

image

On Firefox, it took ages, and eventually gave:

image

@reivilibre
Copy link
Contributor

Is this on test.voip.librepush.net (which is currently running with #18) or on a local copy?

This is probably the tester's fault, especially if Firefox gives it a clean bill of health. The inconsistency is an issue even if nothing else.
It did actually catch an issue with matrix.org some months ago but I seem to remember it was fixed and monitoring was added to make sure it didn't happen again :) — so yes, probably the tester's fault here.

@reivilibre
Copy link
Contributor

matrix.org works (and quickly) for me on Brave, which is the closest to Chrome that I had, but I downloaded a copy of ungoogled-chromium and it took ages (you really weren't kidding, although you said this about Firefox, which works fine for me).

At the end of it, it came up with this contradiction:
image
(The overall result probably shouldn't be 'Excellent' if the actual test runs fail even though a promising-looking candidate was found, but that's for another issue.)

I wonder why it's quite so inconsistent (for you, Firefox misbehaves; for me, it's Chromium).

The 'taking ages' part seems to be waiting for ICE to signal that it finished gathering candidates — even though all of them were available within the first second. This could be ameliorated by adding Trickle ICE support (or perhaps even just cutting ICE off, once a candidate that is interesting for our test is received, if this is allowed).

The failure seems to come from an error in the testing service itself, and it comes back seemingly instantly, but the logs don't immediately reveal anything.

@richvdh
Copy link
Member Author

richvdh commented Jan 20, 2021

Is this on test.voip.librepush.net (which is currently running with #18) or on a local copy?

yes, this was on test.voip.librepush.net.

Something I have noticed in the past is that Chrome gets upset by TURN servers that expose IPv6 addresses (as turn.matrix.org) does, though I now can't quite remember the details. So part of the difference may be about whether turn.matrix.org is reachable over IPv6 from where you are?

@reivilibre
Copy link
Contributor

Is this on test.voip.librepush.net (which is currently running with #18) or on a local copy?

yes, this was on test.voip.librepush.net.

Something I have noticed in the past is that Chrome gets upset by TURN servers that expose IPv6 addresses (as turn.matrix.org) does, though I now can't quite remember the details. So part of the difference may be about whether turn.matrix.org is reachable over IPv6 from where you are?

My ISP doesn't do IPv6 yet so you're probably right on the mark with that one

@richvdh
Copy link
Member Author

richvdh commented Jan 20, 2021

that might also be part of why chromium is slow for you, if the ipv6 bits are timing out?

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

2 participants