How to setup well known for matrix synapse

Arno · May 10, 2025, 6:20am

Here are a few examples :

github.com/spantaleev/matrix-docker-ansible-deploy

caddy2 and .well-known

opened 03:19PM - 23 May 21 UTC

suggestion docs

The instructions for "[configuring well known](https://github.com/spantaleev/mat…rix-docker-ansible-deploy/blob/master/docs/configuring-well-known.md#option-3-setting-up-reverse-proxying-of-the-well-known-files-from-the-base-domains-server-to-the-matrix-server)" are, like usual, concise. Possible too concise. At least for caddy2. A note might be added: > Beware that caddy's `redir` directive has very high priority. For example you may need to us a `route` directive to work around that.

github.com/caddyserver/caddy

Caddy hijacks requests to .well-known/acme-challenge

opened 03:49PM - 09 Aug 16 UTC

closed 04:15AM - 11 Aug 16 UTC

bobobo1618

feature

#### 1. What version of Caddy are you running (`caddy -version`)? Caddy 0.9.0 #…### 2. What are you trying to do? Create/verify Lets Encrypt certificates for non-HTTP services on a server that also happens to run Caddy. #### 3. What is your entire Caddyfile? ``` text http://*/.well-known { root /stuff/.well-known } https://domain { root /otherstuff } ``` #### 4. How did you run Caddy (give the full command and describe the execution environment)? `/usr/local/bin/caddy -log stdout -agree=true -conf=/etc/caddy/Caddyfile -root=/var/tmp -email=me@me.me` #### 5. What did you expect to see? ``` text certbot certonly --manual -d domain.com printf '%s' "challenge" > /stuff/.well-known/acme-challenge/challenge <cert is verified and added here> ``` #### 6. What did you see instead (give full error messages and/or log)? From `certbot`: ``` text Failed authorization procedure. domain.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://domain.com/.well-known/acme-challenge/challenge 2sU [123.456.789.10]: 500 ``` From caddy: ``` text http: proxy error: dial tcp [::1]:5033: getsockopt: connection refused ``` I see in the code that 5033 is the port used for a secondary verification server, so it looks like Caddy is hijacking all requests to that URI for its own purposes. #### 7. How can someone who is starting from scratch reproduce this behavior as minimally as possible? ``` cat > Caddyfile <<EOF http://*/.well-known { root /stuff/.well-known } https://domain { root /otherstuff } EOF caddy <new session here> certbot certonly --webroot -w /stuff -d domain.com ```

github.com/matrix-org/synapse

Make it possible to customize /.well-known/matrix/client response

opened 08:33AM - 10 Nov 20 UTC

closed 10:48AM - 16 Jun 22 UTC

henrikjohansson712

Z-Help-Wanted z-feature T-Enhancement P4

**Description:** The response from the well-known endpoint is currently limit…ed to the homeserver and identity server base urls. Chat clients like Element require that some settings are served through this endpoint, which is quite hard to do the way it's currently set up. Would it be possible to add a "well-known" section to homeserver.yaml where you can add custom values?

If you can help me that would me great!