Skip to content

Element can't access other servers but matrix.org #8950

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

Closed
Error504TimeOut opened this issue Nov 23, 2024 · 7 comments
Closed

Element can't access other servers but matrix.org #8950

Error504TimeOut opened this issue Nov 23, 2024 · 7 comments
Labels
T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@Error504TimeOut
Copy link

Steps to reproduce

  1. Sign out
  2. Open the sign in page
  3. Try to change the homeserver from matrix.org to something else

Outcome

What did you expect?

Selecting the homeserver as usual and being able to log in

What happened instead?

When trying to click next after typing in the homesever URL, it fails with " .well-known not available". I have tried to select another Homeserver on two different devices with three different servers and two different Synapse Versions and several Element Versions from F-Droid. No combination worked. Trying to log into a custom homeserver on: the web, the flatpak version and on an iPad all worked so seemingly this seems to be an issue with the Android version.

Your phone model

Pixel C, Redmi Note 10S

Operating system version

Android 8.1, Android 13 respectivly

Application version and app store

Element Version 1.6.20 F-Droid, Element Version 1.6.22 Play Store

Homeserver

Synapse 1.119.0/1.116.0, Synapse 1.119.0, Synapse 1.119.0

Will you send logs?

Yes

Are you willing to provide a PR?

No

@Error504TimeOut Error504TimeOut added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Nov 23, 2024
@Error504TimeOut
Copy link
Author

Also, while forks of Element like SchildiChat also did not work, independent projects like FluffyChat have been able to successfully log in

@Error504TimeOut
Copy link
Author

I tried to downgrade to 1.110.0 which is just an arbitrary value I picked. Running this version, I could log in and upgrade the server back afterwards.

@slagiewka
Copy link

Same issue here. I have cleared out the storage, trying to see if clean state will fix the abysmal performance of the app.
Little did I know that I would end up being locked out.

.well-known not available which is obviously not true. The well-known is under domain/.well-known/matrix/server which is exposed by Synapse.

Federation tester works:

DNS results

server name/.well-known result contains explicit port number: no SRV lookup done

I just installed FluffyChat and it's insanely fast. But most importantly, it... works.

@Error504TimeOut
Copy link
Author

This is another thing I noticed, only Element based Apps like Schildi (and Element ofc) seem to have this issue

@SebjuFrab
Copy link

Same issue here.

@mrSaT13
Copy link

mrSaT13 commented Apr 4, 2025

will there be a solution to this problem?
I would like to use your app. without setting up anything else,
Element X has no such problems....
can you do the same ?

@Error504TimeOut
Copy link
Author

I seemed to have missed something. To fix this, provide a client.json under .well-known/matrix/client.json after this schema

{
  "m.homeserver": {
    "base_url": "https://<fill accordingly>"
  }

If you have your matrix server running under a sub-domain, make sure to enter it in the JSON, but not in the App.
That at least fixed it for me.

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 and other reported problems
Projects
None yet
Development

No branches or pull requests

4 participants