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 we adverstise the proxy entry in our homeserver.yml instead of /.well-known/matrix/client #404

Closed
Domoel opened this issue Feb 24, 2024 · 5 comments

Comments

@Domoel
Copy link

Domoel commented Feb 24, 2024

Hi,

I am running my synapse installation in a docker environment and cannot access the "/.well-known/matrix/client" file to make the necessary adjustments to advertise the proxy entry. Instead I asked myself if we can bypass this by making some adjustments to the homeserver.yml.

Synapse does support for these kind of options with the following config command:

serve_server_wellknown: true
well_known_server_config:
server: "DOMAIN.ltd"
well_known_client_config:
client: "DOMAIN.ltd"

Is there something similiar for the following entry which usually must be put into the proxy config?

{
"org.matrix.msc3575.proxy": {
"url": "https://slidingsync.proxy.url.here"
}
}

And if not how can I get access to the "/.well-known/matrix/client"" config within a docker container (running on a Synology NAS with container manager)?

Thanks for helping me out. I'm really not an expert (learning by doing). So advise would be highly appreciated.

Best
Dom

@Slug-V
Copy link

Slug-V commented Feb 24, 2024

homeserver.yml has a preference extra_well_known_client_content:

extra_well_known_client_content:
  org.matrix.msc3575.proxy:
    url: "https://slidingsync.proxy.url.here"

My instance uses this.

@Domoel
Copy link
Author

Domoel commented Feb 25, 2024

Thank you! this was the solution I was looking for! Is this part of the official documentation? If so where to find it?

@Slug-V
Copy link

Slug-V commented Feb 25, 2024

You're welcome👍
I found this below.
https://element-hq.github.io/synapse/v1.99/usage/configuration/config_documentation.html#extra_well_known_client_content

The example doesn't have the 2-level setting, but it has no problem.
This will be documented for all Synapse users.

@kegsay kegsay closed this as completed Mar 5, 2024
@Richigeht
Copy link

You're welcome👍 I found this below. https://element-hq.github.io/synapse/v1.99/usage/configuration/config_documentation.html#extra_well_known_client_content

The example doesn't have the 2-level setting, but it has no problem. This will be documented for all Synapse users.

Where did the documentation go? I haven't seen it - only found this just now through digging (and trying to find out, why my slinding sync isnt working)

@Slug-V
Copy link

Slug-V commented May 27, 2024

@Richigeht I'm sorry, I chose wrong word😝

This will be documented

What I mean is "This SHOULD be documented (by someone)", and no one there.
So I created a PR.(edit: it was closed, #443 took over)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants