Matthias/conduit

Fork 0

Sliding sync not working with Element Web #400

New issue

Open

opened 2023-11-05 18:18:15 +00:00 by lnicola · 10 comments

lnicola commented

2023-11-05 18:18:15 +00:00

(Migrated from gitlab.com)

Description

Try to enable sliding sync in Element Web (X works fine). I think I ran into two issues:

https://gitlab.com/famedly/conduit/-/blob/next/src/api/client_server/sync.rs#L1679 waits for 30 seconds, but Element times out after 5 seconds thinking the server doesn't have sliding sync support
~~if it didn't time out in the previous step, Element still seems to try to validate the proxy address by requesting /client/server.json, which Conduit doesn't know about~~

System Configuration

Element version: 1.11.47

Olm version: 3.2.14

Conduit Version: 0.7.0-alpha

Database backend: RocksDB

### Description Try to enable sliding sync in Element Web (X works fine). I think I ran into two issues: - https://gitlab.com/famedly/conduit/-/blob/next/src/api/client_server/sync.rs#L1679 waits for 30 seconds, but Element times out after 5 seconds thinking the server doesn't have sliding sync support - ~~if it didn't time out in the previous step, Element still seems to try to validate the proxy address by requesting `/client/server.json`, which Conduit doesn't know about~~ ### System Configuration Element version: 1.11.47 Olm version: 3.2.14 Conduit Version: 0.7.0-alpha Database backend: RocksDB

lnicola commented

2023-11-05 18:20:38 +00:00

(Migrated from gitlab.com)

changed the description

lnicola commented

2023-11-05 18:20:48 +00:00

(Migrated from gitlab.com)

changed the description

lnicola commented

2023-11-05 18:20:52 +00:00

(Migrated from gitlab.com)

changed the description

Thatoo commented

2023-11-15 11:02:17 +00:00

(Migrated from gitlab.com)

I understood that only Element X are sliding sync compatible for now. Element Web don't have this ability yet. So it's not a conduit issue.
If I'm right, this issue can be closed.

I understood that only Element X are sliding sync compatible for now. Element Web don't have this ability yet. So it's not a conduit issue. If I'm right, this issue can be closed.

lnicola commented

2023-11-15 11:07:30 +00:00

(Migrated from gitlab.com)

I couldn't say. Fixing these two issues might make it work without too much of an effort. It's worth trying.

I'll look into it when I have a bit of time.

I couldn't say. Fixing these two issues might make it work without too much of an effort. It's worth trying. I'll look into it when I have a bit of time.

lnicola commented

2023-11-21 13:49:30 +00:00

(Migrated from gitlab.com)

changed the description

lnicola commented

2023-11-21 13:51:03 +00:00

(Migrated from gitlab.com)

Update: there's no need to respond to /client/server.json. That request actually goes to the Element Web root, so it's enough to drop a file in there (not sure about desktop).

So after patching the wait, I was able to enable sliding sync in Element Web. I'm not sure yet whether it works.

UPDATE: I don't think it works.

Update: there's no need to respond to `/client/server.json`. That request actually goes to the Element Web root, so it's enough to drop a file in there (not sure about desktop). So after patching the wait, I was able to enable sliding sync in Element Web. I'm not sure yet whether it works. UPDATE: I don't think it works.

solarkraft commented

2023-11-23 21:13:22 +00:00

(Migrated from gitlab.com)

mentioned in issue #403

girlbossceo commented

2023-11-26 07:19:57 +00:00

(Migrated from gitlab.com)

Conduit could probably serve this but it would need to figure out its own homeserver URL, not the server name.

In this case my example for Caddy would be:

        header /client/server.json Content-Type application/json
        respond /client/server.json `{"server":"https://matrix.puppygock.gay","version":"cowonduit 4.2.0-6.9"}`

https://matrix.puppygock.gay/client/server.json

The version should be arbitrary, I can't think of any valid reason why it wouldn't be. If it isn't just take matrix.org's version

Conduit still needs to resolve https://gitlab.com/famedly/conduit/-/issues/404 in addition to the other issue you mentioned for Element Web syncv3 to hopefully work properly.

I think a workaround for the missing file is to just send a response on the reverse proxy side with the necessary JSON. As mentioned here https://github.com/vector-im/element-web/issues/26504#issuecomment-1820931405 it is supposed to be sent by the proxy so it definitely would not be looking at Element Web's location, but it's just a JSON file with the URL of the sliding sync proxy (in this case, your Conduit homeserver URL) and an arbitrary version of the proxy (can just put `Conduit 0.7.0-alpha`). Similar to what you would do for the client well-known `/.well-known/matrix/client` Conduit could _probably_ serve this but it would need to figure out its own homeserver URL, not the server name. In this case my example for Caddy would be: ``` header /client/server.json Content-Type application/json respond /client/server.json `{"server":"https://matrix.puppygock.gay","version":"cowonduit 4.2.0-6.9"}` ``` https://matrix.puppygock.gay/client/server.json The version *should* be arbitrary, I can't think of any valid reason why it wouldn't be. If it isn't just take [matrix.org](https://slidingsync.lab.matrix.org/client/server.json)'s version Conduit still needs to resolve https://gitlab.com/famedly/conduit/-/issues/404 in addition to the other issue you mentioned for Element Web syncv3 to hopefully work properly.

lnicola commented

2023-11-26 12:35:11 +00:00

(Migrated from gitlab.com)

It's not that big of a deal. I use different domains for Element Web and the HS, and Element looks for that file under the former. I just plopped the JSON in there.

it is supposed to be sent by the proxy so it definitely would not be looking at Element Web's location

That's where it looks in my case.

It's not that big of a deal. I use different domains for Element Web and the HS, and Element looks for that file under the former. I just plopped the JSON in there. > it is supposed to be sent by the proxy so it definitely would not be looking at Element Web's location That's where it looks in my case.