element-x-android icon indicating copy to clipboard operation
element-x-android copied to clipboard

"We couldn't reach this homeserver" with a valid homeserver URL (without sliding sync support)

Open Ezwen opened this issue 2 years ago • 1 comments

Steps to reproduce

  1. Where are you starting? What can you see?

I install the app for the first time, choose to use a custom homeserver, type in the URL (eg. https://domain.tld). Note that said homeserver does not support sliding sync.

  1. What do you click?

I click the search result available below the search bar (with domain.tld)

Outcome

What did you expect?

I expect the app to acknowledge that the provided URL is indeed a valid matrix homeserver, but that it unfortunately does not provide sliding sync and is thus not compatible.

What happened instead?

The app tells me "We couldn't reach this homeserver", which I find inconsistent this this homeserver does exist − even though it is not compatible.

Your phone model

Mi Mix 2

Operating system version

Android 13 / Lineage 20 (without GAPPS installed)

Application version and app store

0.1.2

Homeserver

Private, Synapse 1.90.0

Will you send logs?

No

Are you willing to provide a PR?

No

Ezwen avatar Aug 20 '23 16:08 Ezwen

Given sliding sync proxy is actually going away right now, this issue can probably be closed as WONTFIX?

spaetz avatar Oct 01 '24 12:10 spaetz

This still happens today for incompatible home servers. I get this error when trying to log in to mozilla.org with the current version of EXA. I used to get the doesn't support sliding sync error, but now it's this one. I think they're not using MAS yet so that's the issue, but it is still a confusing error.

Susurrus avatar Jan 11 '25 07:01 Susurrus

Why is this still an issue for mozilla.org even when they are hosted by element themself afaik?

bjorn3 avatar Jun 17 '25 15:06 bjorn3

This error must only happen to administrators who are testing their matrix backend setup before sharing it to their users. Normal users should not see it.

Any error message within a popup will always not be enough to debug the problem. If you see this message, tap seven times on the version number displayed on the first screen of the tap to display the bug report screen. From there, you will be able to extract the logs from the app to better target the issue.

For info, since this issue was created, ESS Community is now available to set up the whole backend stack in a few minutes. You can have a look at this talk made at Matrix Conference yesterday: Getting started with Element Server Suite Community .

manuroe avatar Oct 19 '25 12:10 manuroe