Dendrite 0.13.0 onwards causes unrecognized request on server URL input on Element Android

matrix-org / dendrite

Dendrite is a second-generation Matrix homeserver written in Go!

https://matrix-org.github.io/dendrite/

Apache License 2.0

5.67k stars 664 forks source link

Dendrite 0.13.0 onwards causes unrecognized request on server URL input on Element Android #3186

Open Alexilator opened 1 year ago

Alexilator commented 1 year ago

Background information

Dendrite version or git SHA: 0.13.0+
SQLite3 or Postgres?: Postgres
Running in Docker?: yes
Client used (if applicable): Element Android App

Description

What is the problem: since Dendrite-monolith 0.13.0 a login with Element Android is not possible
Who is affected: as far as I can tell, everyone using dendrite 0.13.0 onwards and Element Android
How is this bug manifesting: "unrecognized request" message below the custom server URL input field.
When did this first appear: Dendrite-monolith 0.13.0

Steps to reproduce

install / upgrade to dendrite-monolith inside docker 0.13.0 or later
input matrix domain of dendrite-monolith in Element Android App
error "unrecognized request" will be shown below the input

There is nothing in the container logs regarding the client error.

S7evinK commented 1 year ago

Which version did you upgrade from?

Alexilator commented 1 year ago

Which version did you upgrade from?

I upgraded from 0.12.0 but was also able to reproduce with a clean 0.13.0 install.

atahanacar commented 11 months ago

I had the same issue. Properly setting up a .well-known/matrix/client fixed the issue.

mkroman commented 10 months ago

Same issue here. I can confirm that setting up a proper .well-known/matrix/client response solves the issue.

I had to deploy nginx with a static response just for this:

https://github.com/mkroman/k8s/blob/d857aee6c3d4a5d600b9f788a32e2ddc8ae3633d/kustomize/dendrite/base/configmap.nginx-config.yaml#L9-L31

It would be great if Dendrite could provide this endpoint just like it provides the .well-known/matrix/server endpoint.

According to the specs at https://spec.matrix.org/v1.3/client-server-api/#well-known-uri a 404 should immediately trigger a IGNORE and the client should revert to using default values, which in my case would be the base domain.. But for some reason, the android client doesn't do that.

QAQ5555 commented 8 months ago

same error Hope it can be resolved as soon as possible