README.rst 38 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967
  1. .. contents::
  2. Introduction
  3. ============
  4. Matrix is an ambitious new ecosystem for open federated Instant Messaging and
  5. VoIP. The basics you need to know to get up and running are:
  6. - Everything in Matrix happens in a room. Rooms are distributed and do not
  7. exist on any single server. Rooms can be located using convenience aliases
  8. like ``#matrix:matrix.org`` or ``#test:localhost:8448``.
  9. - Matrix user IDs look like ``@matthew:matrix.org`` (although in the future
  10. you will normally refer to yourself and others using a third party identifier
  11. (3PID): email address, phone number, etc rather than manipulating Matrix user IDs)
  12. The overall architecture is::
  13. client <----> homeserver <=====================> homeserver <----> client
  14. https://somewhere.org/_matrix https://elsewhere.net/_matrix
  15. ``#matrix:matrix.org`` is the official support room for Matrix, and can be
  16. accessed by any client from https://matrix.org/docs/projects/try-matrix-now.html or
  17. via IRC bridge at irc://irc.freenode.net/matrix.
  18. Synapse is currently in rapid development, but as of version 0.5 we believe it
  19. is sufficiently stable to be run as an internet-facing service for real usage!
  20. About Matrix
  21. ============
  22. Matrix specifies a set of pragmatic RESTful HTTP JSON APIs as an open standard,
  23. which handle:
  24. - Creating and managing fully distributed chat rooms with no
  25. single points of control or failure
  26. - Eventually-consistent cryptographically secure synchronisation of room
  27. state across a global open network of federated servers and services
  28. - Sending and receiving extensible messages in a room with (optional)
  29. end-to-end encryption[1]
  30. - Inviting, joining, leaving, kicking, banning room members
  31. - Managing user accounts (registration, login, logout)
  32. - Using 3rd Party IDs (3PIDs) such as email addresses, phone numbers,
  33. Facebook accounts to authenticate, identify and discover users on Matrix.
  34. - Placing 1:1 VoIP and Video calls
  35. These APIs are intended to be implemented on a wide range of servers, services
  36. and clients, letting developers build messaging and VoIP functionality on top
  37. of the entirely open Matrix ecosystem rather than using closed or proprietary
  38. solutions. The hope is for Matrix to act as the building blocks for a new
  39. generation of fully open and interoperable messaging and VoIP apps for the
  40. internet.
  41. Synapse is a reference "homeserver" implementation of Matrix from the core
  42. development team at matrix.org, written in Python/Twisted. It is intended to
  43. showcase the concept of Matrix and let folks see the spec in the context of a
  44. codebase and let you run your own homeserver and generally help bootstrap the
  45. ecosystem.
  46. In Matrix, every user runs one or more Matrix clients, which connect through to
  47. a Matrix homeserver. The homeserver stores all their personal chat history and
  48. user account information - much as a mail client connects through to an
  49. IMAP/SMTP server. Just like email, you can either run your own Matrix
  50. homeserver and control and own your own communications and history or use one
  51. hosted by someone else (e.g. matrix.org) - there is no single point of control
  52. or mandatory service provider in Matrix, unlike WhatsApp, Facebook, Hangouts,
  53. etc.
  54. We'd like to invite you to join #matrix:matrix.org (via
  55. https://matrix.org/docs/projects/try-matrix-now.html), run a homeserver, take a look
  56. at the `Matrix spec <https://matrix.org/docs/spec>`_, and experiment with the
  57. `APIs <https://matrix.org/docs/api>`_ and `Client SDKs
  58. <https://matrix.org/docs/projects/try-matrix-now.html#client-sdks>`_.
  59. Thanks for using Matrix!
  60. [1] End-to-end encryption is currently in beta: `blog post <https://matrix.org/blog/2016/11/21/matrixs-olm-end-to-end-encryption-security-assessment-released-and-implemented-cross-platform-on-riot-at-last>`_.
  61. Synapse Installation
  62. ====================
  63. Synapse is the reference python/twisted Matrix homeserver implementation.
  64. System requirements:
  65. - POSIX-compliant system (tested on Linux & OS X)
  66. - Python 2.7
  67. - At least 1GB of free RAM if you want to join large public rooms like #matrix:matrix.org
  68. Installing from source
  69. ----------------------
  70. (Prebuilt packages are available for some platforms - see `Platform-Specific
  71. Instructions`_.)
  72. Synapse is written in python but some of the libraries it uses are written in
  73. C. So before we can install synapse itself we need a working C compiler and the
  74. header files for python C extensions.
  75. Installing prerequisites on Ubuntu or Debian::
  76. sudo apt-get install build-essential python2.7-dev libffi-dev \
  77. python-pip python-setuptools sqlite3 \
  78. libssl-dev python-virtualenv libjpeg-dev libxslt1-dev
  79. Installing prerequisites on ArchLinux::
  80. sudo pacman -S base-devel python2 python-pip \
  81. python-setuptools python-virtualenv sqlite3
  82. Installing prerequisites on CentOS 7 or Fedora 25::
  83. sudo yum install libtiff-devel libjpeg-devel libzip-devel freetype-devel \
  84. lcms2-devel libwebp-devel tcl-devel tk-devel redhat-rpm-config \
  85. python-virtualenv libffi-devel openssl-devel
  86. sudo yum groupinstall "Development Tools"
  87. Installing prerequisites on Mac OS X::
  88. xcode-select --install
  89. sudo easy_install pip
  90. sudo pip install virtualenv
  91. brew install pkg-config libffi
  92. Installing prerequisites on Raspbian::
  93. sudo apt-get install build-essential python2.7-dev libffi-dev \
  94. python-pip python-setuptools sqlite3 \
  95. libssl-dev python-virtualenv libjpeg-dev
  96. sudo pip install --upgrade pip
  97. sudo pip install --upgrade ndg-httpsclient
  98. sudo pip install --upgrade virtualenv
  99. Installing prerequisites on openSUSE::
  100. sudo zypper in -t pattern devel_basis
  101. sudo zypper in python-pip python-setuptools sqlite3 python-virtualenv \
  102. python-devel libffi-devel libopenssl-devel libjpeg62-devel
  103. Installing prerequisites on OpenBSD::
  104. doas pkg_add python libffi py-pip py-setuptools sqlite3 py-virtualenv \
  105. libxslt
  106. To install the synapse homeserver run::
  107. virtualenv -p python2.7 ~/.synapse
  108. source ~/.synapse/bin/activate
  109. pip install --upgrade pip
  110. pip install --upgrade setuptools
  111. pip install https://github.com/matrix-org/synapse/tarball/master
  112. This installs synapse, along with the libraries it uses, into a virtual
  113. environment under ``~/.synapse``. Feel free to pick a different directory
  114. if you prefer.
  115. In case of problems, please see the _`Troubleshooting` section below.
  116. There is an offical synapse image available at
  117. https://hub.docker.com/r/matrixdotorg/synapse/tags/ which can be used with
  118. the docker-compose file available at `contrib/docker <contrib/docker>`_. Further information on
  119. this including configuration options is available in the README on
  120. hub.docker.com.
  121. Alternatively, Andreas Peters (previously Silvio Fricke) has contributed a
  122. Dockerfile to automate a synapse server in a single Docker image, at
  123. https://hub.docker.com/r/avhost/docker-matrix/tags/
  124. Configuring synapse
  125. -------------------
  126. Before you can start Synapse, you will need to generate a configuration
  127. file. To do this, run (in your virtualenv, as before)::
  128. cd ~/.synapse
  129. python -m synapse.app.homeserver \
  130. --server-name my.domain.name \
  131. --config-path homeserver.yaml \
  132. --generate-config \
  133. --report-stats=[yes|no]
  134. ... substituting an appropriate value for ``--server-name``. The server name
  135. determines the "domain" part of user-ids for users on your server: these will
  136. all be of the format ``@user:my.domain.name``. It also determines how other
  137. matrix servers will reach yours for `Federation`_. For a test configuration,
  138. set this to the hostname of your server. For a more production-ready setup, you
  139. will probably want to specify your domain (``example.com``) rather than a
  140. matrix-specific hostname here (in the same way that your email address is
  141. probably ``user@example.com`` rather than ``user@email.example.com``) - but
  142. doing so may require more advanced setup - see `Setting up
  143. Federation`_. Beware that the server name cannot be changed later.
  144. This command will generate you a config file that you can then customise, but it will
  145. also generate a set of keys for you. These keys will allow your Home Server to
  146. identify itself to other Home Servers, so don't lose or delete them. It would be
  147. wise to back them up somewhere safe. (If, for whatever reason, you do need to
  148. change your Home Server's keys, you may find that other Home Servers have the
  149. old key cached. If you update the signing key, you should change the name of the
  150. key in the ``<server name>.signing.key`` file (the second word) to something
  151. different. See `the spec`__ for more information on key management.)
  152. .. __: `key_management`_
  153. The default configuration exposes two HTTP ports: 8008 and 8448. Port 8008 is
  154. configured without TLS; it should be behind a reverse proxy for TLS/SSL
  155. termination on port 443 which in turn should be used for clients. Port 8448
  156. is configured to use TLS with a self-signed certificate. If you would like
  157. to do initial test with a client without having to setup a reverse proxy,
  158. you can temporarly use another certificate. (Note that a self-signed
  159. certificate is fine for `Federation`_). You can do so by changing
  160. ``tls_certificate_path``, ``tls_private_key_path`` and ``tls_dh_params_path``
  161. in ``homeserver.yaml``; alternatively, you can use a reverse-proxy, but be sure
  162. to read `Using a reverse proxy with Synapse`_ when doing so.
  163. Apart from port 8448 using TLS, both ports are the same in the default
  164. configuration.
  165. Registering a user
  166. ------------------
  167. You will need at least one user on your server in order to use a Matrix
  168. client. Users can be registered either `via a Matrix client`__, or via a
  169. commandline script.
  170. .. __: `client-user-reg`_
  171. To get started, it is easiest to use the command line to register new users::
  172. $ source ~/.synapse/bin/activate
  173. $ synctl start # if not already running
  174. $ register_new_matrix_user -c homeserver.yaml https://localhost:8448
  175. New user localpart: erikj
  176. Password:
  177. Confirm password:
  178. Make admin [no]:
  179. Success!
  180. This process uses a setting ``registration_shared_secret`` in
  181. ``homeserver.yaml``, which is shared between Synapse itself and the
  182. ``register_new_matrix_user`` script. It doesn't matter what it is (a random
  183. value is generated by ``--generate-config``), but it should be kept secret, as
  184. anyone with knowledge of it can register users on your server even if
  185. ``enable_registration`` is ``false``.
  186. Setting up a TURN server
  187. ------------------------
  188. For reliable VoIP calls to be routed via this homeserver, you MUST configure
  189. a TURN server. See `<docs/turn-howto.rst>`_ for details.
  190. IPv6
  191. ----
  192. As of Synapse 0.19 we finally support IPv6, many thanks to @kyrias and @glyph
  193. for providing PR #1696.
  194. However, for federation to work on hosts with IPv6 DNS servers you **must**
  195. be running Twisted 17.1.0 or later - see https://github.com/matrix-org/synapse/issues/1002
  196. for details. We can't make Synapse depend on Twisted 17.1 by default
  197. yet as it will break most older distributions (see https://github.com/matrix-org/synapse/pull/1909)
  198. so if you are using operating system dependencies you'll have to install your
  199. own Twisted 17.1 package via pip or backports etc.
  200. If you're running in a virtualenv then pip should have installed the newest
  201. Twisted automatically, but if your virtualenv is old you will need to manually
  202. upgrade to a newer Twisted dependency via:
  203. pip install Twisted>=17.1.0
  204. Running Synapse
  205. ===============
  206. To actually run your new homeserver, pick a working directory for Synapse to
  207. run (e.g. ``~/.synapse``), and::
  208. cd ~/.synapse
  209. source ./bin/activate
  210. synctl start
  211. Connecting to Synapse from a client
  212. ===================================
  213. The easiest way to try out your new Synapse installation is by connecting to it
  214. from a web client. The easiest option is probably the one at
  215. https://riot.im/app. You will need to specify a "Custom server" when you log on
  216. or register: set this to ``https://domain.tld`` if you setup a reverse proxy
  217. following the recommended setup, or ``https://localhost:8448`` - remember to specify the
  218. port (``:8448``) if not ``:443`` unless you changed the configuration. (Leave the identity
  219. server as the default - see `Identity servers`_.)
  220. If using port 8448 you will run into errors until you accept the self-signed
  221. certificate. You can easily do this by going to ``https://localhost:8448``
  222. directly with your browser and accept the presented certificate. You can then
  223. go back in your web client and proceed further.
  224. If all goes well you should at least be able to log in, create a room, and
  225. start sending messages.
  226. (The homeserver runs a web client by default at https://localhost:8448/, though
  227. as of the time of writing it is somewhat outdated and not really recommended -
  228. https://github.com/matrix-org/synapse/issues/1527).
  229. .. _`client-user-reg`:
  230. Registering a new user from a client
  231. ------------------------------------
  232. By default, registration of new users via Matrix clients is disabled. To enable
  233. it, specify ``enable_registration: true`` in ``homeserver.yaml``. (It is then
  234. recommended to also set up CAPTCHA - see `<docs/CAPTCHA_SETUP.rst>`_.)
  235. Once ``enable_registration`` is set to ``true``, it is possible to register a
  236. user via `riot.im <https://riot.im/app/#/register>`_ or other Matrix clients.
  237. Your new user name will be formed partly from the ``server_name`` (see
  238. `Configuring synapse`_), and partly from a localpart you specify when you
  239. create the account. Your name will take the form of::
  240. @localpart:my.domain.name
  241. (pronounced "at localpart on my dot domain dot name").
  242. As when logging in, you will need to specify a "Custom server". Specify your
  243. desired ``localpart`` in the 'User name' box.
  244. Security Note
  245. =============
  246. Matrix serves raw user generated data in some APIs - specifically the `content
  247. repository endpoints <https://matrix.org/docs/spec/client_server/latest.html#get-matrix-media-r0-download-servername-mediaid>`_.
  248. Whilst we have tried to mitigate against possible XSS attacks (e.g.
  249. https://github.com/matrix-org/synapse/pull/1021) we recommend running
  250. matrix homeservers on a dedicated domain name, to limit any malicious user generated
  251. content served to web browsers a matrix API from being able to attack webapps hosted
  252. on the same domain. This is particularly true of sharing a matrix webclient and
  253. server on the same domain.
  254. See https://github.com/vector-im/vector-web/issues/1977 and
  255. https://developer.github.com/changes/2014-04-25-user-content-security for more details.
  256. Platform-Specific Instructions
  257. ==============================
  258. Debian
  259. ------
  260. Matrix provides official Debian packages via apt from https://matrix.org/packages/debian/.
  261. Note that these packages do not include a client - choose one from
  262. https://matrix.org/docs/projects/try-matrix-now.html (or build your own with one of our SDKs :)
  263. Fedora
  264. ------
  265. Synapse is in the Fedora repositories as ``matrix-synapse``::
  266. sudo dnf install matrix-synapse
  267. Oleg Girko provides Fedora RPMs at
  268. https://obs.infoserver.lv/project/monitor/matrix-synapse
  269. OpenSUSE
  270. --------
  271. Synapse is in the OpenSUSE repositories as ``matrix-synapse``::
  272. sudo zypper install matrix-synapse
  273. SUSE Linux Enterprise Server
  274. ----------------------------
  275. Unofficial package are built for SLES 15 in the openSUSE:Backports:SLE-15 repository at
  276. https://download.opensuse.org/repositories/openSUSE:/Backports:/SLE-15/standard/
  277. ArchLinux
  278. ---------
  279. The quickest way to get up and running with ArchLinux is probably with the community package
  280. https://www.archlinux.org/packages/community/any/matrix-synapse/, which should pull in most of
  281. the necessary dependencies. If the default web client is to be served (enabled by default in
  282. the generated config),
  283. https://www.archlinux.org/packages/community/any/python2-matrix-angular-sdk/ will also need to
  284. be installed.
  285. Alternatively, to install using pip a few changes may be needed as ArchLinux
  286. defaults to python 3, but synapse currently assumes python 2.7 by default:
  287. pip may be outdated (6.0.7-1 and needs to be upgraded to 6.0.8-1 )::
  288. sudo pip2.7 install --upgrade pip
  289. You also may need to explicitly specify python 2.7 again during the install
  290. request::
  291. pip2.7 install https://github.com/matrix-org/synapse/tarball/master
  292. If you encounter an error with lib bcrypt causing an Wrong ELF Class:
  293. ELFCLASS32 (x64 Systems), you may need to reinstall py-bcrypt to correctly
  294. compile it under the right architecture. (This should not be needed if
  295. installing under virtualenv)::
  296. sudo pip2.7 uninstall py-bcrypt
  297. sudo pip2.7 install py-bcrypt
  298. During setup of Synapse you need to call python2.7 directly again::
  299. cd ~/.synapse
  300. python2.7 -m synapse.app.homeserver \
  301. --server-name machine.my.domain.name \
  302. --config-path homeserver.yaml \
  303. --generate-config
  304. ...substituting your host and domain name as appropriate.
  305. FreeBSD
  306. -------
  307. Synapse can be installed via FreeBSD Ports or Packages contributed by Brendan Molloy from:
  308. - Ports: ``cd /usr/ports/net-im/py-matrix-synapse && make install clean``
  309. - Packages: ``pkg install py27-matrix-synapse``
  310. OpenBSD
  311. -------
  312. There is currently no port for OpenBSD. Additionally, OpenBSD's security
  313. settings require a slightly more difficult installation process.
  314. 1) Create a new directory in ``/usr/local`` called ``_synapse``. Also, create a
  315. new user called ``_synapse`` and set that directory as the new user's home.
  316. This is required because, by default, OpenBSD only allows binaries which need
  317. write and execute permissions on the same memory space to be run from
  318. ``/usr/local``.
  319. 2) ``su`` to the new ``_synapse`` user and change to their home directory.
  320. 3) Create a new virtualenv: ``virtualenv -p python2.7 ~/.synapse``
  321. 4) Source the virtualenv configuration located at
  322. ``/usr/local/_synapse/.synapse/bin/activate``. This is done in ``ksh`` by
  323. using the ``.`` command, rather than ``bash``'s ``source``.
  324. 5) Optionally, use ``pip`` to install ``lxml``, which Synapse needs to parse
  325. webpages for their titles.
  326. 6) Use ``pip`` to install this repository: ``pip install
  327. https://github.com/matrix-org/synapse/tarball/master``
  328. 7) Optionally, change ``_synapse``'s shell to ``/bin/false`` to reduce the
  329. chance of a compromised Synapse server being used to take over your box.
  330. After this, you may proceed with the rest of the install directions.
  331. NixOS
  332. -----
  333. Robin Lambertz has packaged Synapse for NixOS at:
  334. https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/misc/matrix-synapse.nix
  335. Windows Install
  336. ---------------
  337. Synapse can be installed on Cygwin. It requires the following Cygwin packages:
  338. - gcc
  339. - git
  340. - libffi-devel
  341. - openssl (and openssl-devel, python-openssl)
  342. - python
  343. - python-setuptools
  344. The content repository requires additional packages and will be unable to process
  345. uploads without them:
  346. - libjpeg8
  347. - libjpeg8-devel
  348. - zlib
  349. If you choose to install Synapse without these packages, you will need to reinstall
  350. ``pillow`` for changes to be applied, e.g. ``pip uninstall pillow`` ``pip install
  351. pillow --user``
  352. Troubleshooting:
  353. - You may need to upgrade ``setuptools`` to get this to work correctly:
  354. ``pip install setuptools --upgrade``.
  355. - You may encounter errors indicating that ``ffi.h`` is missing, even with
  356. ``libffi-devel`` installed. If you do, copy the ``.h`` files:
  357. ``cp /usr/lib/libffi-3.0.13/include/*.h /usr/include``
  358. - You may need to install libsodium from source in order to install PyNacl. If
  359. you do, you may need to create a symlink to ``libsodium.a`` so ``ld`` can find
  360. it: ``ln -s /usr/local/lib/libsodium.a /usr/lib/libsodium.a``
  361. Troubleshooting
  362. ===============
  363. Troubleshooting Installation
  364. ----------------------------
  365. Synapse requires pip 1.7 or later, so if your OS provides too old a version you
  366. may need to manually upgrade it::
  367. sudo pip install --upgrade pip
  368. Installing may fail with ``Could not find any downloads that satisfy the requirement pymacaroons-pynacl (from matrix-synapse==0.12.0)``.
  369. You can fix this by manually upgrading pip and virtualenv::
  370. sudo pip install --upgrade virtualenv
  371. You can next rerun ``virtualenv -p python2.7 synapse`` to update the virtual env.
  372. Installing may fail during installing virtualenv with ``InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.``
  373. You can fix this by manually installing ndg-httpsclient::
  374. pip install --upgrade ndg-httpsclient
  375. Installing may fail with ``mock requires setuptools>=17.1. Aborting installation``.
  376. You can fix this by upgrading setuptools::
  377. pip install --upgrade setuptools
  378. If pip crashes mid-installation for reason (e.g. lost terminal), pip may
  379. refuse to run until you remove the temporary installation directory it
  380. created. To reset the installation::
  381. rm -rf /tmp/pip_install_matrix
  382. pip seems to leak *lots* of memory during installation. For instance, a Linux
  383. host with 512MB of RAM may run out of memory whilst installing Twisted. If this
  384. happens, you will have to individually install the dependencies which are
  385. failing, e.g.::
  386. pip install twisted
  387. On OS X, if you encounter clang: error: unknown argument: '-mno-fused-madd' you
  388. will need to export CFLAGS=-Qunused-arguments.
  389. Troubleshooting Running
  390. -----------------------
  391. If synapse fails with ``missing "sodium.h"`` crypto errors, you may need
  392. to manually upgrade PyNaCL, as synapse uses NaCl (https://nacl.cr.yp.to/) for
  393. encryption and digital signatures.
  394. Unfortunately PyNACL currently has a few issues
  395. (https://github.com/pyca/pynacl/issues/53) and
  396. (https://github.com/pyca/pynacl/issues/79) that mean it may not install
  397. correctly, causing all tests to fail with errors about missing "sodium.h". To
  398. fix try re-installing from PyPI or directly from
  399. (https://github.com/pyca/pynacl)::
  400. # Install from PyPI
  401. pip install --user --upgrade --force pynacl
  402. # Install from github
  403. pip install --user https://github.com/pyca/pynacl/tarball/master
  404. Running out of File Handles
  405. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  406. If synapse runs out of filehandles, it typically fails badly - live-locking
  407. at 100% CPU, and/or failing to accept new TCP connections (blocking the
  408. connecting client). Matrix currently can legitimately use a lot of file handles,
  409. thanks to busy rooms like #matrix:matrix.org containing hundreds of participating
  410. servers. The first time a server talks in a room it will try to connect
  411. simultaneously to all participating servers, which could exhaust the available
  412. file descriptors between DNS queries & HTTPS sockets, especially if DNS is slow
  413. to respond. (We need to improve the routing algorithm used to be better than
  414. full mesh, but as of June 2017 this hasn't happened yet).
  415. If you hit this failure mode, we recommend increasing the maximum number of
  416. open file handles to be at least 4096 (assuming a default of 1024 or 256).
  417. This is typically done by editing ``/etc/security/limits.conf``
  418. Separately, Synapse may leak file handles if inbound HTTP requests get stuck
  419. during processing - e.g. blocked behind a lock or talking to a remote server etc.
  420. This is best diagnosed by matching up the 'Received request' and 'Processed request'
  421. log lines and looking for any 'Processed request' lines which take more than
  422. a few seconds to execute. Please let us know at #matrix-dev:matrix.org if
  423. you see this failure mode so we can help debug it, however.
  424. ArchLinux
  425. ~~~~~~~~~
  426. If running `$ synctl start` fails with 'returned non-zero exit status 1',
  427. you will need to explicitly call Python2.7 - either running as::
  428. python2.7 -m synapse.app.homeserver --daemonize -c homeserver.yaml
  429. ...or by editing synctl with the correct python executable.
  430. Upgrading an existing Synapse
  431. =============================
  432. The instructions for upgrading synapse are in `UPGRADE.rst`_.
  433. Please check these instructions as upgrading may require extra steps for some
  434. versions of synapse.
  435. .. _UPGRADE.rst: UPGRADE.rst
  436. .. _federation:
  437. Setting up Federation
  438. =====================
  439. Federation is the process by which users on different servers can participate
  440. in the same room. For this to work, those other servers must be able to contact
  441. yours to send messages.
  442. As explained in `Configuring synapse`_, the ``server_name`` in your
  443. ``homeserver.yaml`` file determines the way that other servers will reach
  444. yours. By default, they will treat it as a hostname and try to connect to
  445. port 8448. This is easy to set up and will work with the default configuration,
  446. provided you set the ``server_name`` to match your machine's public DNS
  447. hostname.
  448. For a more flexible configuration, you can set up a DNS SRV record. This allows
  449. you to run your server on a machine that might not have the same name as your
  450. domain name. For example, you might want to run your server at
  451. ``synapse.example.com``, but have your Matrix user-ids look like
  452. ``@user:example.com``. (A SRV record also allows you to change the port from
  453. the default 8448. However, if you are thinking of using a reverse-proxy on the
  454. federation port, which is not recommended, be sure to read
  455. `Reverse-proxying the federation port`_ first.)
  456. To use a SRV record, first create your SRV record and publish it in DNS. This
  457. should have the format ``_matrix._tcp.<yourdomain.com> <ttl> IN SRV 10 0 <port>
  458. <synapse.server.name>``. The DNS record should then look something like::
  459. $ dig -t srv _matrix._tcp.example.com
  460. _matrix._tcp.example.com. 3600 IN SRV 10 0 8448 synapse.example.com.
  461. Note that the server hostname cannot be an alias (CNAME record): it has to point
  462. directly to the server hosting the synapse instance.
  463. You can then configure your homeserver to use ``<yourdomain.com>`` as the domain in
  464. its user-ids, by setting ``server_name``::
  465. python -m synapse.app.homeserver \
  466. --server-name <yourdomain.com> \
  467. --config-path homeserver.yaml \
  468. --generate-config
  469. python -m synapse.app.homeserver --config-path homeserver.yaml
  470. If you've already generated the config file, you need to edit the ``server_name``
  471. in your ``homeserver.yaml`` file. If you've already started Synapse and a
  472. database has been created, you will have to recreate the database.
  473. If all goes well, you should be able to `connect to your server with a client`__,
  474. and then join a room via federation. (Try ``#matrix-dev:matrix.org`` as a first
  475. step. "Matrix HQ"'s sheer size and activity level tends to make even the
  476. largest boxes pause for thought.)
  477. .. __: `Connecting to Synapse from a client`_
  478. Troubleshooting
  479. ---------------
  480. You can use the federation tester to check if your homeserver is all set:
  481. ``https://matrix.org/federationtester/api/report?server_name=<your_server_name>``
  482. If any of the attributes under "checks" is false, federation won't work.
  483. The typical failure mode with federation is that when you try to join a room,
  484. it is rejected with "401: Unauthorized". Generally this means that other
  485. servers in the room couldn't access yours. (Joining a room over federation is a
  486. complicated dance which requires connections in both directions).
  487. So, things to check are:
  488. * If you are trying to use a reverse-proxy, read `Reverse-proxying the
  489. federation port`_.
  490. * If you are not using a SRV record, check that your ``server_name`` (the part
  491. of your user-id after the ``:``) matches your hostname, and that port 8448 on
  492. that hostname is reachable from outside your network.
  493. * If you *are* using a SRV record, check that it matches your ``server_name``
  494. (it should be ``_matrix._tcp.<server_name>``), and that the port and hostname
  495. it specifies are reachable from outside your network.
  496. Running a Demo Federation of Synapses
  497. -------------------------------------
  498. If you want to get up and running quickly with a trio of homeservers in a
  499. private federation, there is a script in the ``demo`` directory. This is mainly
  500. useful just for development purposes. See `<demo/README>`_.
  501. Using PostgreSQL
  502. ================
  503. As of Synapse 0.9, `PostgreSQL <https://www.postgresql.org>`_ is supported as an
  504. alternative to the `SQLite <https://sqlite.org/>`_ database that Synapse has
  505. traditionally used for convenience and simplicity.
  506. The advantages of Postgres include:
  507. * significant performance improvements due to the superior threading and
  508. caching model, smarter query optimiser
  509. * allowing the DB to be run on separate hardware
  510. * allowing basic active/backup high-availability with a "hot spare" synapse
  511. pointing at the same DB master, as well as enabling DB replication in
  512. synapse itself.
  513. For information on how to install and use PostgreSQL, please see
  514. `docs/postgres.rst <docs/postgres.rst>`_.
  515. .. _reverse-proxy:
  516. Using a reverse proxy with Synapse
  517. ==================================
  518. It is recommended to put a reverse proxy such as
  519. `nginx <https://nginx.org/en/docs/http/ngx_http_proxy_module.html>`_,
  520. `Apache <https://httpd.apache.org/docs/current/mod/mod_proxy_http.html>`_ or
  521. `HAProxy <https://www.haproxy.org/>`_ in front of Synapse. One advantage of
  522. doing so is that it means that you can expose the default https port (443) to
  523. Matrix clients without needing to run Synapse with root privileges.
  524. The most important thing to know here is that Matrix clients and other Matrix
  525. servers do not necessarily need to connect to your server via the same
  526. port. Indeed, clients will use port 443 by default, whereas servers default to
  527. port 8448. Where these are different, we refer to the 'client port' and the
  528. 'federation port'.
  529. The next most important thing to know is that using a reverse-proxy on the
  530. federation port has a number of pitfalls. It is possible, but be sure to read
  531. `Reverse-proxying the federation port`_.
  532. The recommended setup is therefore to configure your reverse-proxy on port 443
  533. to port 8008 of synapse for client connections, but to also directly expose port
  534. 8448 for server-server connections. All the Matrix endpoints begin ``/_matrix``,
  535. so an example nginx configuration might look like::
  536. server {
  537. listen 443 ssl;
  538. listen [::]:443 ssl;
  539. server_name matrix.example.com;
  540. location /_matrix {
  541. proxy_pass http://localhost:8008;
  542. proxy_set_header X-Forwarded-For $remote_addr;
  543. }
  544. }
  545. and an example apache configuration may look like::
  546. <VirtualHost *:443>
  547. SSLEngine on
  548. ServerName matrix.example.com;
  549. <Location /_matrix>
  550. ProxyPass http://127.0.0.1:8008/_matrix nocanon
  551. ProxyPassReverse http://127.0.0.1:8008/_matrix
  552. </Location>
  553. </VirtualHost>
  554. You will also want to set ``bind_addresses: ['127.0.0.1']`` and ``x_forwarded: true``
  555. for port 8008 in ``homeserver.yaml`` to ensure that client IP addresses are
  556. recorded correctly.
  557. Having done so, you can then use ``https://matrix.example.com`` (instead of
  558. ``https://matrix.example.com:8448``) as the "Custom server" when `Connecting to
  559. Synapse from a client`_.
  560. Reverse-proxying the federation port
  561. ------------------------------------
  562. There are two issues to consider before using a reverse-proxy on the federation
  563. port:
  564. * Due to the way SSL certificates are managed in the Matrix federation protocol
  565. (see `spec`__), Synapse needs to be configured with the path to the SSL
  566. certificate, *even if you do not terminate SSL at Synapse*.
  567. .. __: `key_management`_
  568. * Synapse does not currently support SNI on the federation protocol
  569. (`bug #1491 <https://github.com/matrix-org/synapse/issues/1491>`_), which
  570. means that using name-based virtual hosting is unreliable.
  571. Furthermore, a number of the normal reasons for using a reverse-proxy do not
  572. apply:
  573. * Other servers will connect on port 8448 by default, so there is no need to
  574. listen on port 443 (for federation, at least), which avoids the need for root
  575. privileges and virtual hosting.
  576. * A self-signed SSL certificate is fine for federation, so there is no need to
  577. automate renewals. (The certificate generated by ``--generate-config`` is
  578. valid for 10 years.)
  579. If you want to set up a reverse-proxy on the federation port despite these
  580. caveats, you will need to do the following:
  581. * In ``homeserver.yaml``, set ``tls_certificate_path`` to the path to the SSL
  582. certificate file used by your reverse-proxy, and set ``no_tls`` to ``True``.
  583. (``tls_private_key_path`` will be ignored if ``no_tls`` is ``True``.)
  584. * In your reverse-proxy configuration:
  585. * If there are other virtual hosts on the same port, make sure that the
  586. *default* one uses the certificate configured above.
  587. * Forward ``/_matrix`` to Synapse.
  588. * If your reverse-proxy is not listening on port 8448, publish a SRV record to
  589. tell other servers how to find you. See `Setting up Federation`_.
  590. When updating the SSL certificate, just update the file pointed to by
  591. ``tls_certificate_path``: there is no need to restart synapse. (You may like to
  592. use a symbolic link to help make this process atomic.)
  593. The most common mistake when setting up federation is not to tell Synapse about
  594. your SSL certificate. To check it, you can visit
  595. ``https://matrix.org/federationtester/api/report?server_name=<your_server_name>``.
  596. Unfortunately, there is no UI for this yet, but, you should see
  597. ``"MatchingTLSFingerprint": true``. If not, check that
  598. ``Certificates[0].SHA256Fingerprint`` (the fingerprint of the certificate
  599. presented by your reverse-proxy) matches ``Keys.tls_fingerprints[0].sha256``
  600. (the fingerprint of the certificate Synapse is using).
  601. Identity Servers
  602. ================
  603. Identity servers have the job of mapping email addresses and other 3rd Party
  604. IDs (3PIDs) to Matrix user IDs, as well as verifying the ownership of 3PIDs
  605. before creating that mapping.
  606. **They are not where accounts or credentials are stored - these live on home
  607. servers. Identity Servers are just for mapping 3rd party IDs to matrix IDs.**
  608. This process is very security-sensitive, as there is obvious risk of spam if it
  609. is too easy to sign up for Matrix accounts or harvest 3PID data. In the longer
  610. term, we hope to create a decentralised system to manage it (`matrix-doc #712
  611. <https://github.com/matrix-org/matrix-doc/issues/712>`_), but in the meantime,
  612. the role of managing trusted identity in the Matrix ecosystem is farmed out to
  613. a cluster of known trusted ecosystem partners, who run 'Matrix Identity
  614. Servers' such as `Sydent <https://github.com/matrix-org/sydent>`_, whose role
  615. is purely to authenticate and track 3PID logins and publish end-user public
  616. keys.
  617. You can host your own copy of Sydent, but this will prevent you reaching other
  618. users in the Matrix ecosystem via their email address, and prevent them finding
  619. you. We therefore recommend that you use one of the centralised identity servers
  620. at ``https://matrix.org`` or ``https://vector.im`` for now.
  621. To reiterate: the Identity server will only be used if you choose to associate
  622. an email address with your account, or send an invite to another user via their
  623. email address.
  624. URL Previews
  625. ============
  626. Synapse 0.15.0 introduces a new API for previewing URLs at
  627. ``/_matrix/media/r0/preview_url``. This is disabled by default. To turn it on
  628. you must enable the ``url_preview_enabled: True`` config parameter and
  629. explicitly specify the IP ranges that Synapse is not allowed to spider for
  630. previewing in the ``url_preview_ip_range_blacklist`` configuration parameter.
  631. This is critical from a security perspective to stop arbitrary Matrix users
  632. spidering 'internal' URLs on your network. At the very least we recommend that
  633. your loopback and RFC1918 IP addresses are blacklisted.
  634. This also requires the optional lxml and netaddr python dependencies to be
  635. installed. This in turn requires the libxml2 library to be available - on
  636. Debian/Ubuntu this means ``apt-get install libxml2-dev``, or equivalent for
  637. your OS.
  638. Password reset
  639. ==============
  640. If a user has registered an email address to their account using an identity
  641. server, they can request a password-reset token via clients such as Vector.
  642. A manual password reset can be done via direct database access as follows.
  643. First calculate the hash of the new password::
  644. $ source ~/.synapse/bin/activate
  645. $ ./scripts/hash_password
  646. Password:
  647. Confirm password:
  648. $2a$12$xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  649. Then update the `users` table in the database::
  650. UPDATE users SET password_hash='$2a$12$xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
  651. WHERE name='@test:test.com';
  652. Synapse Development
  653. ===================
  654. Before setting up a development environment for synapse, make sure you have the
  655. system dependencies (such as the python header files) installed - see
  656. `Installing from source`_.
  657. To check out a synapse for development, clone the git repo into a working
  658. directory of your choice::
  659. git clone https://github.com/matrix-org/synapse.git
  660. cd synapse
  661. Synapse has a number of external dependencies, that are easiest
  662. to install using pip and a virtualenv::
  663. virtualenv -p python2.7 env
  664. source env/bin/activate
  665. python synapse/python_dependencies.py | xargs pip install
  666. pip install lxml mock
  667. This will run a process of downloading and installing all the needed
  668. dependencies into a virtual env.
  669. Once this is done, you may wish to run Synapse's unit tests, to
  670. check that everything is installed as it should be::
  671. PYTHONPATH="." trial tests
  672. This should end with a 'PASSED' result::
  673. Ran 143 tests in 0.601s
  674. PASSED (successes=143)
  675. Running the Integration Tests
  676. =============================
  677. Synapse is accompanied by `SyTest <https://github.com/matrix-org/sytest>`_,
  678. a Matrix homeserver integration testing suite, which uses HTTP requests to
  679. access the API as a Matrix client would. It is able to run Synapse directly from
  680. the source tree, so installation of the server is not required.
  681. Testing with SyTest is recommended for verifying that changes related to the
  682. Client-Server API are functioning correctly. See the `installation instructions
  683. <https://github.com/matrix-org/sytest#installing>`_ for details.
  684. Building Internal API Documentation
  685. ===================================
  686. Before building internal API documentation install sphinx and
  687. sphinxcontrib-napoleon::
  688. pip install sphinx
  689. pip install sphinxcontrib-napoleon
  690. Building internal API documentation::
  691. python setup.py build_sphinx
  692. Help!! Synapse eats all my RAM!
  693. ===============================
  694. Synapse's architecture is quite RAM hungry currently - we deliberately
  695. cache a lot of recent room data and metadata in RAM in order to speed up
  696. common requests. We'll improve this in future, but for now the easiest
  697. way to either reduce the RAM usage (at the risk of slowing things down)
  698. is to set the almost-undocumented ``SYNAPSE_CACHE_FACTOR`` environment
  699. variable. The default is 0.5, which can be decreased to reduce RAM usage
  700. in memory constrained enviroments, or increased if performance starts to
  701. degrade.
  702. .. _`key_management`: https://matrix.org/docs/spec/server_server/unstable.html#retrieving-server-keys