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

Unable to log in using element web or desktop #2127

Open
lgwapnitsky opened this issue Feb 6, 2025 · 3 comments
Open

Unable to log in using element web or desktop #2127

lgwapnitsky opened this issue Feb 6, 2025 · 3 comments
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@lgwapnitsky
Copy link

I'm receiving the following error when attempting to use app.element.io or the element desktop app on my linux install:

Can't connect to homeserver - please check your connectivity, ensure your [homeserver's SSL certificate](https://matrix.wapnitsky.com/) is trusted, and that a browser extension is not blocking requests.

I can successfully connect from the app on my phone with no issues, but I do need desktop access.

I've tried using the switch as recommended below with no luck:

As mentioned in matrix-org/synapse#5152 (comment), to connect with my .onion hs I need to run Element Desktop version 1.11.30 with --ignore-certificate-errors parameter. The same HS run with Element Web (on element.io) connects without sweat, although the browser (Chrome) turns the padlock icon red as "your connection to this site is not secure", which I accept as Tor provides another means for privacy.

Firstly, I would much more prefer a relevant option in config.json to either ignore certificate checks completely or create a whitelist of trusted hosts about which electron should not make fuss if a self-signed certificate is presented.

Eventually, I would also like self-signed certificates to simply be acknowledged and handled favorably. Please also note, that on Element Android, when a non-trusted certificate is presented by the server, the client simply asks the user whether it should be accepted. Seems only plausible to expect a similar user experience on both platforms.

Originally posted by @ghost in #798

@dosubot dosubot bot added O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect labels Feb 6, 2025
@t3chguy
Copy link
Member

t3chguy commented Feb 6, 2025

You'd need to look at the Electron console and provide the logs there, only that knows the underlying error as CORS hides the underlying error from javascript code.

@t3chguy t3chguy added the X-Needs-Info This issue is blocked awaiting information from the reporter label Feb 6, 2025
@lgwapnitsky
Copy link
Author

lgwapnitsky commented Feb 6, 2025 via email

@t3chguy
Copy link
Member

t3chguy commented Feb 6, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

No branches or pull requests

2 participants