-
Notifications
You must be signed in to change notification settings - Fork 223
I can't login to any homeserver at all: "We couldn't reach this homeserver" #3447
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
Comments
You have an invalid global HTTP proxy set on your phone according to those logs. Try disabling it |
Umm? What proxy? I was connected to mobile data, no proxy is set up in Mobile APN settings. Now I'm connected to Wi-Fi. No proxy is set up in Wi-Fi network's settings. No VPNs are enabled. I also had AdAway installed, I disabled it, it didn't help, still getting same error. No issues with any other app, including Element (not x) |
Specifically I'm talking about the
|
Oh, is it issue with my android settings or with element x app? |
Probably your OS settings |
How do I disable that proxy?
|
Here's a discussion where several other users have had this issue beforehand https://matrix.to/#/!aCvOWKNDeXXpPgquKq:matrix.org/$omg7ZqwN8XJYoBjjUDGVtE0WMVTjij4gRn_ajJElwwE?via=nerdhouse.io&via=matrix.org&via=envs.net |
can confirm this issues with SAMSUNG SM-N910T on Android 14 |
open termux, enter "su" and execute commands:
|
no root on that phone |
that phone succesfully downloads well-known from my homeserver |
not fixed, please reopen |
@532910, can you try to do the same thing via adb shell from pc? |
it was done from pc |
@532910, maybe factory reset?... |
no way |
@532910, well ok i will reopen |
|
@532910 @ImMALWARE The reason that Element X Android can download the well known is that it uses the Retrofit library to download this well known, and here's the interesting thing: That import java.net.ProxySelector
import java.net.URI
ProxySelector.getDefault().select(URI("http://example.com"))
# Returns a single entry [Proxy.NO_PROXY] Retrofit uses OkHttp and by default inherits this system behaviour. Rust isn't like that and will validate this proxy string, thus errored out. I guess this should also applies to classic Element and other apps. |
same problem, the home server works on other devices like linux and browser, and all other apps on the phone work fine, just the element x login doesn't work, neither in mobile internet, nor in wifi. pls consider fixing as the old app is not available anymore via google play. |
my fix was to install the old app via f-droid. |
mmh, some VPN or other firewall app was setting Android's HTTP proxy settings to ":0" which rust apparently considers an invalid proxy. So from the app's point of view nothing to be fixed, as it is debatable whether ":0" is a valid HTTP proxy entry (aka don't use any) or an invalid one (preventing connections). The proper fix is to remove the HTTP value which could also cause problems for other applications besides EXA |
No I don't think that this value would trip most other apps, as this
I have written technical details in #3447 (comment) but to reiterate: The |
Steps to reproduce
Outcome
What did you expect?
Login and password prompt
What happened instead?
We couldn't reach this homeserver. Please check that you have entered the homeserver USL correctly. If the URL is correct, contact your homeserver administrator for further help.
No matter what homeserver I try to login, it always gives this error
Your phone model
POCO X5 Pro 5G
Operating system version
Android 14
Application version and app store
Element X 0.5.3
Homeserver
I tried a lot of homeserver, none worked, even matrix.org
Will you send logs?
Yes
Are you willing to provide a PR?
No
The text was updated successfully, but these errors were encountered: