You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I still have the issue. The changes did not work. I asked in the synapse chat and they adviced me to search in the reverse proxies. I will keep this post up to date when I find new ideas to solve the issue.
The text was updated successfully, but these errors were encountered:
It should be noted that the Ruby SDK chooses not to try to intelligently handle any low-level communication issues, it will only handle expected application-level errors that can occur - things like the Matrix server responding with a 429 Too Many Requests.
If you're seeing errors with the socket not opening within the timeout, you can either expand said value
api.open_timeout=120
or use Ruby's exception handling to retry the action that failed.
If your bot is requesting a lot you will easily get into this error. It can be solved by increasing the rate limit:
https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users
Alternatively this is also possible via SQL:
matrix-org/synapse#6286 (comment)
EDIT 1
I still have the issue. The changes did not work. I asked in the synapse chat and they adviced me to search in the reverse proxies. I will keep this post up to date when I find new ideas to solve the issue.
The text was updated successfully, but these errors were encountered: