Fixed Prosody port numbers (see #70)

jsxc · Sep 19, 2019 · 4e84b60 · 4e84b60
1 parent 953debc
commit 4e84b60
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -4,6 +4,15 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](http://keepachangelog.com/)
 and this project adheres to [Semantic Versioning](http://semver.org/).
 
+## 2.0.4+ - [Unreleased]
+### Added
+
+### Fixed
+- Port numbers in Prosody documentation
+
+### Changed
+
+
 ## 2.0.4 - 2019-09-19
 ### Added
 * `xcrefreshroster` to clear a faulty roster cache.

diff --git a/doc/Installation.md b/doc/Installation.md
@@ -273,8 +273,8 @@ Current workaround: Delete the account in Conversations and then add it again.
 
 If you see unreliable behavior with *Prosody*, you might want to try the experimental socket interface.
 When using the `mod_auth_external.lua` bundled here (together with `pseudolpty.lua`), you can use
-the `external_auth_command = "@localhost:23664";` option to talk over a socket to a process not spawned
-by *Prosody* on port 23664. [doc/Systemd.md](../doc/Systemd.md) explains how to automatically start
+the `external_auth_command = "@localhost:23663";` option to talk over a socket to a process not spawned
+by *Prosody* on port 23663. [doc/Systemd.md](../doc/Systemd.md) explains how to automatically start
 such a process using *systemd*.
 
 ### *ejabberd* shared roster support