diff options
| author | Erik Johnston <erik@matrix.org> | 2019-10-09 16:52:21 +0100 |
|---|---|---|
| committer | Erik Johnston <erik@matrix.org> | 2019-10-09 16:52:21 +0100 |
| commit | 5c1f886c75979b606c1e8bb45fcd8b7d26a71f39 (patch) | |
| tree | ee651459cda811d4ac5d11f1e2fc4d9c06df037a /README.rst | |
| parent | Update (diff) | |
| parent | Merge pull request #6185 from matrix-org/erikj/fix_censored_evnets (diff) | |
| download | synapse-5c1f886c75979b606c1e8bb45fcd8b7d26a71f39.tar.xz | |
Merge branch 'develop' of github.com:matrix-org/synapse into erikj/patch_inner
Diffstat (limited to 'README.rst')
| -rw-r--r-- | README.rst | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/README.rst b/README.rst index 2948fd0765..ae51d6ab39 100644 --- a/README.rst +++ b/README.rst @@ -381,3 +381,16 @@ indicate that your server is also issuing far more outgoing federation requests than can be accounted for by your users' activity, this is a likely cause. The misbehavior can be worked around by setting ``use_presence: false`` in the Synapse config file. + +People can't accept room invitations from me +-------------------------------------------- + +The typical failure mode here is that you send an invitation to someone +to join a room or direct chat, but when they go to accept it, they get an +error (typically along the lines of "Invalid signature"). They might see +something like the following in their logs:: + + 2019-09-11 19:32:04,271 - synapse.federation.transport.server - 288 - WARNING - GET-11752 - authenticate_request failed: 401: Invalid signature for server <server> with key ed25519:a_EqML: Unable to verify signature for <server> + +This is normally caused by a misconfiguration in your reverse-proxy. See +`<docs/reverse_proxy.rst>`_ and double-check that your settings are correct. |