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

call.element.dev connection issues #2269

Open
eukara opened this issue Mar 15, 2024 · 2 comments
Open

call.element.dev connection issues #2269

eukara opened this issue Mar 15, 2024 · 2 comments
Labels
T-Defect Something isn't working: bugs, crashes, hangs, vulnerabilities, or other reported problems

Comments

@eukara
Copy link

eukara commented Mar 15, 2024

Steps to reproduce

Try accessing call.element.dev via a VPN, or change the local time I suppose.

image

Outcome

What did you expect?

The user to be able to join the Element Call video room.

What happened instead?

The connection timed out due to handshake errors.
Most likely because the web server at call.element.dev reports the wrong time?

Operating system

Browser

Browser information

Chrome 122.0.6261.70

URL for webapp

call.element.dev

Will you send logs?

No

@eukara eukara added the T-Defect Something isn't working: bugs, crashes, hangs, vulnerabilities, or other reported problems label Mar 15, 2024
@toger5
Copy link
Contributor

toger5 commented Mar 15, 2024

This is in embedded mode right?
It seems like you are using the newest element web dev branch (that is expecting the widget to sent a content loaded event)
But the widget is not sending one. Which version (git commit) are u using for element call?

When accessing call.element.dev via a browser you should not get any widget related errors however...
Can you describe more in detail what exactly your setup is?

@eukara
Copy link
Author

eukara commented Mar 15, 2024

The main problem is not being able to open call.element.dev, this is using the latest version of Chrome:
image

Meanwhile, call.element.io works:
image

The user changed their timezone to not be automatic, they live in the East Coast of the United States, but have their timezone set to the West Coast as their business is there.
That's what's probably causing a handshake error, is what we're guessing.

Something is probably wrong with the configuration of the call.element.dev server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Defect Something isn't working: bugs, crashes, hangs, vulnerabilities, or other reported problems
Projects
None yet
Development

No branches or pull requests

2 participants