LibertaCasa/system
9
0
Fork 0
Code Issues 3 Pull Requests Projects Releases Wiki Activity

matrix nginx/config issue #7

New Issue
Closed
opened 2021-10-30 11:16:16 +02:00 by pratyush · 3 comments
pratyush commented 2021-10-30 11:16:16 +02:00
Owner
Copy Link
10:52 <~val> so in the Matrix protocol, when the user ID is @xxxx:liberta.casa, clients are supposed to query https://liberta.casa/.well-known/matrix/client first
10:52 <~val> if it returns 404, they assume liberta.casa itself is the homeserver, so they query https://liberta.casa/_matrix/client/r0/login
10:52 <~val> which is also 404 on your config
10:53 <~val> so clients have no way of knowing that your matrix server is actually at matrix.liberta.casa
10:53 <mogad0n> I see 
10:53 <~val> so you have two options:
10:53 <~val> 1. make the user ids @xxxx:matrix.liberta.casa
10:54 <~val> 2. copy https://matrix.liberta.casa/.well-known/matrix/client to https://liberta.casa/.well-known/matrix/client

discussion resulting from the diagnosis of the sasl auth timeout failure for the matrix2051 client.

``` 10:52 <~val> so in the Matrix protocol, when the user ID is @xxxx:liberta.casa, clients are supposed to query https://liberta.casa/.well-known/matrix/client first 10:52 <~val> if it returns 404, they assume liberta.casa itself is the homeserver, so they query https://liberta.casa/_matrix/client/r0/login 10:52 <~val> which is also 404 on your config 10:53 <~val> so clients have no way of knowing that your matrix server is actually at matrix.liberta.casa 10:53 <mogad0n> I see 10:53 <~val> so you have two options: 10:53 <~val> 1. make the user ids @xxxx:matrix.liberta.casa 10:54 <~val> 2. copy https://matrix.liberta.casa/.well-known/matrix/client to https://liberta.casa/.well-known/matrix/client ``` discussion resulting from the diagnosis of the sasl auth timeout failure for the matrix2051 client.
Georg commented 2021-10-30 19:34:58 +02:00
Owner
Copy Link

This needs to be in a Matrix repository.

There are SRV records on iberta.casa pointing to matrix.liberta.casa in addition to well-known files. I thought SRV records would be sufficient, but discovered:

Yet to discover:

  • Why is the well-known fallback not working?
This needs to be in a Matrix repository. There are SRV records on iberta.casa pointing to matrix.liberta.casa in addition to well-known files. I thought SRV records would be sufficient, but discovered: * They are not sufficient: https://github.com/matrix-org/matrix-federation-tester/issues/93#issuecomment-760940902. * They are not being served. Yet to discover: * Why is the well-known fallback not working?
Georg commented 2021-12-07 00:56:30 +01:00
Owner
Copy Link

Did this get resolved with the replacement of the certificate with one including the liberta.casa SAN? The federation tester shows green.

Did this get resolved with the replacement of the certificate with one including the liberta.casa SAN? The federation tester shows green.
pratyush commented 2022-06-21 18:07:52 +02:00
Author
Owner
Copy Link

Matrix is dead so im closing this issue

Matrix is dead so im closing this issue
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Priority: Critical
Priority: High
Priority: Low
Priority: Medium
Type: Sprinkle
Write yaml to salt
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: LibertaCasa/system#7
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?