diff options
| author | Daniel Gultsch <daniel@gultsch.de> | 2021-03-15 09:51:00 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-03-15 09:51:00 +0300 |
| commit | d30a08266a441df07fa169097f47f854686c6407 (patch) | |
| tree | 1101c1db736110c2c4af977d867a2336d9f58375 | |
| parent | 859f3b2a1dd0cdd2e92b1ac0b84173035b001cd3 (diff) | |
Fix typo in readme
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -143,7 +143,7 @@ Note: This is kind of a weird quirk in OpenFire. Most other servers would just t Maybe you attempted to use the Jabber ID `test@b.tld` because `a.tld` doesn’t point to the correct host. In that case you might have to enable the extended connection settings in the expert settings of Conversations and set a host name. -### I get 'Stream opening error'. What does that mean? +#### I get 'Stream opening error'. What does that mean? In most cases this error is caused by ejabberd advertising support for TLSv1.3 but not properly supporting it. This can happen if the OpenSSL version on the server already supports TLSv1.3 but the fast\_tls wrapper library used by ejabberd not (properly) support it. Upgrading fast\_tls and ejabberd or - theoretically - downgrading OpenSSL should fix the issue. A work around is to explicitly disable TLSv1.3 support in the ejabberd configuration. More information can be found on [this issue on the ejabberd issue tracker](https://github.com/processone/ejabberd/issues/2614). |