Closed AlexanderBabel closed 1 month ago
The issue is that client
and federation
are not listed in resources, but I'm not sure if requiring them for the new endpoints is intentional or not. If it's intentional, it should probably be highlighted in release notes. If not, then it's a bug.
Agreed. Either we should:
client
and federation
resources during worker configuration
...ormedia
resource also start the relevant client/federation servlets for the new endpointsI think the preferred approach going forward should be to ensure that when specifying the media
resource, all appropriate handlers are started in that situation.
It might be nice to add a link to this to the upgrade notes as well. As of right now, this is really confusing because it still does not work, even after modify the reverse proxy config as instructed, if you are deploying with a seperate media worker. (https://element-hq.github.io/synapse/latest/upgrade)
I don't think there's any point in adding upgrade notes for a bug that was already fixed and released 🤔
@devonh the issue can probably be closed now?
Ah, then I seem to have overlooked it in the release notes.
Just to clarify, in case someone else is confused with this: As of 1.114, this fix is included. 1.113 does not have it yet.
Description
I use a workers configuration for my synapse with a media worker. I already updated my ingress to forward the new authenticated endpoints to the media worker instance. But all of them are returned with 404.
It looks like that the new endpoints are not registered on startup on the media server
Steps to reproduce
Homeserver
babel1.eu
Synapse Version
v1.111.0
Installation Method
Docker (matrixdotorg/synapse)
Database
postgres
Workers
Multiple workers
Platform
Ubuntu 22.04, Kubernetes
Configuration
Relevant log output
Anything else that would be useful to know?
No response