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

Can't login into my server from newly installed Element #8897

Closed
Manifoldme opened this issue Sep 5, 2024 · 4 comments
Closed

Can't login into my server from newly installed Element #8897

Manifoldme opened this issue Sep 5, 2024 · 4 comments
Labels
T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@Manifoldme
Copy link

Manifoldme commented Sep 5, 2024

Steps to reproduce

Issue: I enter my server address and the app returns ".well-known not available".
Element 1.6.18
Samsung S21 Ultra,
Android 14,
One UI 6.1,
Security Patch August.

I've been self-hosting Synapse for about six years without federation/delegation, so .well-known is not present in my installation.
First I had a problem with the microphone on 1.6.20, where after a screen went off, my microphone also went off.
So I tried Schieldi, but it never worked for me in the past and the notification issue is still there, so I installed the older version of Element from F-Droid 1.6.18, but suddenly
I experience the same problem I had with ElementX which works over proxy, and that's why I don't use it.
Update.
Synapse 1.114.0+Bookworm1
has integrated sliding sync, that's might be the culprit.

Outcome

What did you expect?

What happened instead?

.well-known not available

Your phone model

Samsung S21 Ultra

Operating system version

Android 14

Application version and app store

1.6.18

Homeserver

Synapse 1.114.0+Bookworm1

Will you send logs?

No

Are you willing to provide a PR?

Yes

@Manifoldme Manifoldme added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Sep 5, 2024
@Alex11381
Copy link

I have same problem. How you fix it?

@JitteryDoodle
Copy link

Can confirm that I'm also having this issue on versions 1.6.14-1.6.18 on GrapheneOS (Android 14, Build 2024090400).

Installing the older versions did not fix this issue.

However, this might be related to a change on the actual synapse client maybe? When I run curl to get the same file:

curl https://matrix.mydomain.xyz/.well-known/matrix/client
{"errcode":"M_NOT_FOUND","error":".well-known not available"}% 

So this file really doesn't seem to exist on my Synapse endpoint, which is probably the issue.

@JitteryDoodle
Copy link

Solved! I had to add the .well-known information to my reverse proxy.

Follow this guide and set up the files manually, then you can sign in via Element.

@Ninjustin649
Copy link

I also had this issue. I resolved it by setting "public_baseurl: https://matrix.domain.name/" in homeserver.yaml. After restarting the matrix synapse service it started hosting the .well-known file.

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