-
Notifications
You must be signed in to change notification settings - Fork 187
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
Remote media fetches fail from beeper.com since 1.110.0rc1 #17394
Comments
Potentially related: #17256 |
This looks like it is due to hitting this case ( In their config, To state the problem more clearly, any homeserver which has |
We have deployed an update to the Beeper homeserver which should make it send the |
hah, I came by to say it looks like Beeper deployed a fix because I'm struggling to test my changes locally 😅 |
#17439) Prior to this PR, remote downloads which did not provide a `content-length` were decremented from the remote download ratelimiter at the max allowable size, leading to excessive ratelimiting - see #17394. This PR adds a linearizer to limit concurrent remote downloads to 6 per IP address, and decrements remote downloads without a `content-length` from the ratelimiter *after* the download is complete and the response length is known. Also adds logic to ensure that responses with a known length respect the `max_download_size`.
Description
Images never load, and the logs are spammed with these 429 errors
Steps to reproduce
beeper.com
user to a user on a homeserver running Synapse 1.110.0rc1 or newerHomeserver
nerdhouse.io, beeper.com
Synapse Version
1.110.0
Installation Method
Docker (matrixdotorg/synapse)
Database
postgres 15
Workers
Multiple workers
Platform
Docker on Linux
Configuration
I also have the LDAP module configured
Relevant log output
Anything else that would be useful to know?
There are also occasionally also authentication errors from Beeper's media store in S3, although I'm not sure if they're related. Not posting those logs because they're full of what look like keys
The text was updated successfully, but these errors were encountered: