Open Half-Shot opened 1 year ago
The problem is due to the connections being closed without a response (the appservice closed the connection without responding to the HTTP request.)
@Half-Shot can we close this? I'm not sure it'll be easy to make it any clearer what's going on
I feel like "Connection was closed without a response" is a much clearer error than "Connection was closed cleanly".
I wouldn't usually be so bothered about it, but since the user action to take when their bridge fails to ping is "consult your homeserver logs", there needs to be some clarity about what's going wrong.
I concede though this is probably more of a Twisted issue than Synapse, so I can take this elsewhere.
Hmm, I guess that's fair. Though I think it'll be a bit of a PITA to try and rewrite these connection errors TBH.
Description
When the AS tried to access the ping endpoint, it instead gets a 502 response. The response logs are pretty unhelpful, as it doesn't explain what's actually failing.
Note: This service was working prior to an update to the bridge which caused it to start pinging the HS, so I'm fairly sure the connection to the AS should be fine.
Steps to reproduce
(I'm afraid I don't know the full steps to cause this, as I'm just reporting what I am seeing)
Homeserver
N/A
Synapse Version
1.85.1
Installation Method
Docker (matrixdotorg/synapse)
Database
PostgreSQL
Workers
Multiple workers
Platform
Kubernetes
Configuration
No response
Relevant log output
Anything else that would be useful to know?
No response