spantaleev
commented
1 month ago For matrix-media-repo, we're exposing the new "authenticated media" APIs on Traefik's internal entrypoint, so that they're reachable at http://matrix-traefik:8008/_matrix/client/v1/...
That said, this does not seem to be related to the new "authenticated media" APIs, but to the old ones judging by your logs containing references to /_matrix/media/ (as opposed to /_matrix/client/..).
These old media routes have been handled like this (being captured at the internal Traefik entrypoint and being forwarded to matrix-media-repo) for a long time, so this is not something new.
I suppose the problem may be that matrix-media-repo insists on being called with the correct Host header (your homeserver name), not with matrix-traefik. As it says here:
Configuring MMR to use the correct server name can be challenging. MMR requires that it be approached with a Host header matching the name used in user IDs. This same server name must also be the name used in the config for the homeserver.
Note that the server name is before delegation. You may need to override the Host header at the reverse proxy before forwarding the request to MMR.
As a solution, I wonder if we could use Traefik's Headers middleware (and its customRequestHeaders option) for matrix-media-repo's internal Traefik entrypoint routers (in the labels file) to force-set the Host header correctly before the request is forwarded to matrix-media-repo.
You can try defining a new middleware and applying it to these routers. Example:
+# Perhaps matrix.3ddruckbremen.de should be used here, but you may also try 3ddruckbremen.de
+traefik.http.middlewares.matrix-media-repo-set-host-header.headers.customrequestheaders.Host=matrix.3ddruckbremen.de
-{% if middlewares | length > 0 %}
-traefik.http.routers.matrix-media-repo-internal-media.middlewares={{ middlewares | join(',') }}
-{% endif %}
+traefik.http.routers.matrix-media-repo-internal-media.middlewares=matrix-media-repo-set-host-headerIf this helps, the labels.j2 template can be reworked to do things correctly.
I do not use matrix-media-repo myself, so I cannot test these changes.
wuast94
gnouts
Describe the bug When trying to send an image to a brdiged room i get
⚠ Your message may not have been bridged: failed to download media: failed to GET /_matrix/client/v1/media/download/[3ddruckbremen.de/c829d204cef7946e48bf2bb2fe7f427516d60e7b1817181090125709312](http://3ddruckbremen.de/c829d204cef7946e48bf2bb2fe7f427516d60e7b1817181090125709312): M_UNRECOGNIZED (HTTP 404): Unrecognized requesthere are the logs of media repo:
what wonders me in the error line is
Error downloading content: Get \"http://3ddruckbremen.de/000d55052f2b43c52b3cfc83e81d17e18c6c6f4e1817179450475806720\": host not allowed"i mean the url seems to be an internal one but the path is just a random string?
this happens on all bridges, telegram isnt even throughin an error. tried whatsapp telegram discord and instagram. sending in normal matrix rooms seems to work
To Reproduce matrix_mautrix_whatsapp_enabled: true matrix_media_repo_enabled: true
Expected behavior A clear and concise description of what you expected to happen.
Matrix Server: