Generate Initial Synapse Config And Signing Key Failed Matrix-synapse

Posted on by admin

Unknown service 'matrix-synapse' + sudo yunohost service remove matrix-synapse W: GPG error: http: // httpredir.debian.org jessie Release: The following signatures couldn 't be verified because the public key is not available: NOPUBKEY 8B48AD NOPUBKEY 7638D0442B90D010 NOPUBKEY CBF8D6FD518E17E1. Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. Mar 05, 2018  @Half-Shot This is all my file homeserver.yaml: # vim:ft=yaml # PEM encoded X509 certificate for TLS. # You can replace the self-signed certificate that synapse # autogenerates on launch with your own SSL certificate + key pair # if you like.

  1. synapse wurde nicht ordnungsgemäß entfernt
  2. + sudo yunohost service remove matrix-synapse
  3. W: GPG error: http://httpredir.debian.org jessie-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010
  4. + DEBIAN_FRONTEND=noninteractive
  5. + ynh_package_update
  6. + sudo rm -rf /etc/apt/sources.list.d/matrix.list
  7. Close port 5349
  8. + grep -q '- 5349$'
  9. + closeport
  10. + sudo yunohost firewall disallow TCP 8448
  11. + echo 'Close port 8448'
  12. + sudo yunohost firewall list
  13. + port=8448
  14. + REMOVE_LOGROTATE_CONF
  15. + sudo rm /etc/nginx/conf.d/MY.DOMAIN.XXX.COM.d/synapse.conf
  16. + echo 'Delete nginx config'
  17. + '[' -e /etc/nginx/conf.d/MY.DOMAIN.XXX.COM.d/synapse.conf ']'
  18. + true
  19. E: Unable to locate package python-matrix-synapse-ldap3
  20. + sudo apt-get -y -qq autoremove matrix-synapse python-matrix-synapse-ldap3 coturn
  21. + ynh_apt autoremove matrix-synapse python-matrix-synapse-ldap3 coturn
  22. + ynh_package_autoremove matrix-synapse python-matrix-synapse-ldap3 coturn
  23. Failed to stop coturn.service: Unit coturn.service not loaded.
  24. + true
  25. Failed to stop matrix-synapse.service: Unit matrix-synapse.service not loaded.
  26. + turnserver_tls_port=5349
  27. ++ sudo yunohost app setting synapse turnserver_tls_port --output-as plain --quiet
  28. ++ ynh_app_setting_get synapse turnserver_tls_port
  29. ++ sudo yunohost app setting synapse synapse_tls_port --output-as plain --quiet
  30. + domain=MY.DOMAIN.XXX.COM
  31. ++ sudo yunohost app setting synapse domain --output-as plain --quiet
  32. + ARCHITECTURE=arm
  33. ++ grep arm
  34. + '[' -n '' ']'
  35. ++ uname -m
  36. ++ uname -m
  37. + test jessie jessie
  38. + debian_version=jessie
  39. + GET_DEBIAN_VERSION
  40. + CHECK_VAR synapse 'app name not set'
  41. ++ . /usr/share/yunohost/helpers.d/utils
  42. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  43. ++ '[' -r /usr/share/yunohost/helpers.d/user ']'
  44. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  45. ++ '[' -r /usr/share/yunohost/helpers.d/string ']'
  46. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  47. ++ '[' -r /usr/share/yunohost/helpers.d/setting ']'
  48. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  49. ++ '[' -r /usr/share/yunohost/helpers.d/print ']'
  50. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  51. ++ '[' -r /usr/share/yunohost/helpers.d/package ']'
  52. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  53. ++ . /usr/share/yunohost/helpers.d/mysql
  54. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  55. ++ '[' -r /usr/share/yunohost/helpers.d/ip ']'
  56. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  57. ++ . /usr/share/yunohost/helpers.d/filesystem
  58. ++ '[' -r /usr/share/yunohost/helpers.d/filesystem ']'
  59. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  60. +++ run-parts --list /usr/share/yunohost/helpers.d
  61. + set -eu
  62. ++ python_ujson_version=1.35-1
  63. ++ md5sum_python_ujson=5b65f8cb6bedef7971fdc557e09effbe
  64. ++ md5sum_python_nacl=34c44f8f5100170bae3b4329ffb43087
  65. ++ debian_repos=http://httpredir.debian.org/debian/
  66. Skript '/var/cache/yunohost/from_file/synapse_ynh-master/scripts/remove' wird ausgeührt..
  67. + sudo apt-get -y -qq -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold install coturn
  68. + ynh_apt -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold install coturn
  69. + sudo debconf-set-selections
  70. + echo 'matrix-synapse matrix-synapse/report-stats selectfalse'
  71. + echo 'matrix-synapse matrix-synapse/server-name select MY.DOMAIN.XXX.COM'
  72. + sudo apt-key add /tmp/matrix-repo-key.asc
  73. + wget -q -O /tmp/matrix-repo-key.asc https://matrix.org/packages/debian/repo-key.asc
  74. + sudo sed -i s@__PORT__@8008@g /etc/nginx/conf.d/MY.DOMAIN.XXX.COM.d/synapse.conf
  75. + sudo sed -i s@__PATH__@/_matrix@g /etc/nginx/conf.d/MY.DOMAIN.XXX.COM.d/synapse.conf
  76. + sudo cp ./conf/nginx.conf /etc/nginx/conf.d/MY.DOMAIN.XXX.COM.d/synapse.conf
  77. + sudo yunohost app setting synapse turnserver_pwd -v 1EZeOrvefWLEMotFLEOVpdmcVUvmIa --quiet
  78. + ynh_app_setting_set synapse turnserver_pwd 1EZeOrvefWLEMotFLEOVpdmcVUvmIa
  79. + sudo yunohost app setting synapse turnserver_tls_port -v 5349 --quiet
  80. + ynh_app_setting_set synapse turnserver_tls_port 5349
  81. + sudo yunohost app setting synapse synapse_tls_port -v 8448 --quiet
  82. + ynh_app_setting_set synapse synapse_tls_port 8448
  83. + sudo yunohost app setting synapse synapse_port -v 8008 --quiet
  84. + sudo yunohost app setting synapse is_public -v 1 --quiet
  85. + sudo yunohost app setting synapse path -v /_matrix --quiet
  86. + sudo yunohost app setting synapse domain -v MY.DOMAIN.XXX.COM --quiet
  87. + ynh_app_setting_set synapse domain MY.DOMAIN.XXX.COM
  88. ++ sed -n 's/(.{30}).*/1/p'
  89. ++ dd if=/dev/urandom bs=1 count=200
  90. .......................+........+................+............................++*++*
  91. Generating DH parameters, 2048 bit long safe prime, generator 2
  92. + sudo openssl dhparam -out /etc/yunohost/certs/MY.DOMAIN.XXX.COM/dh.pem 2048
  93. + test '!' -e /etc/yunohost/certs/MY.DOMAIN.XXX.COM/dh.pem
  94. + sudo yunohost firewall allow --no-upnp Both 5349
  95. + turnserver_tls_port=5349
  96. ++ netcat -z 127.0.0.1 5349
  97. ++ port=5349
  98. + synapse_port=8008
  99. ++ netcat -z 127.0.0.1 8008
  100. ++ port=8008
  101. + synapse_tls_port=8448
  102. ++ netcat -z 127.0.0.1 8448
  103. ++ port=8448
  104. + '[' -e /var/www/synapse ']'
  105. + CHECK_FINALPATH
  106. + sudo yunohost app checkurl MY.DOMAIN.XXX.COM/_matrix -a synapse
  107. + '[' x / ']'
  108. + CHECK_PATH
  109. + path=/_matrix
  110. + ARCHITECTURE=arm
  111. ++ grep arm
  112. + '[' -n '' ']'
  113. ++ uname -m
  114. ++ grep 64
  115. + test jessie jessie
  116. + debian_version=jessie
  117. + GET_DEBIAN_VERSION
  118. + CHECK_VAR synapse 'app name not set'
  119. ++ . /usr/share/yunohost/helpers.d/utils
  120. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  121. ++ '[' -r /usr/share/yunohost/helpers.d/user ']'
  122. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  123. ++ '[' -r /usr/share/yunohost/helpers.d/string ']'
  124. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  125. ++ '[' -r /usr/share/yunohost/helpers.d/setting ']'
  126. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  127. ++ '[' -r /usr/share/yunohost/helpers.d/print ']'
  128. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  129. ++ '[' -r /usr/share/yunohost/helpers.d/package ']'
  130. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  131. ++ . /usr/share/yunohost/helpers.d/mysql
  132. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  133. ++ '[' -r /usr/share/yunohost/helpers.d/ip ']'
  134. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  135. ++ . /usr/share/yunohost/helpers.d/filesystem
  136. ++ '[' -r /usr/share/yunohost/helpers.d/filesystem ']'
  137. ++ for helper in '$(run-parts--list/usr/share/yunohost/helpers.d 2>/dev/null)'
  138. +++ run-parts --list /usr/share/yunohost/helpers.d
  139. + set -eu
  140. ++ python_ujson_version=1.35-1
  141. ++ md5sum_python_ujson=5b65f8cb6bedef7971fdc557e09effbe
  142. ++ md5sum_python_nacl=34c44f8f5100170bae3b4329ffb43087
  143. ++ debian_repos=http://httpredir.debian.org/debian/
  144. Skript '/var/cache/yunohost/from_file/synapse_ynh-master/scripts/install' wird ausgeührt..
  145. Erledigt.
  146. Wird heruntergeladen..

Related

How to Install and Secure the Mosquitto MQTT Messaging Broker on Ubuntu 16.04 Tutorial
How to Install and Configure Ansible on Ubuntu 18.04 [Quickstart] Tutorial

Introduction

Matrix is an open standard for decentralized communication. It’s a collection of servers and services used for online messaging which speak a standardized API that synchronizes in real time.

Matrix uses homeservers to store your account information and chat history. They work in a similar way to how an email client connects to email servers through IMAP/SMTP. Like email, you can either use a Matrix homeserver hosted by somebody else or host your own and be in control of your own information and communications.

By following this guide you will install Synapse, the reference homeserver implementation of Matrix. When you’re finished, you will be able to connect to your homeserver via any Matrix client and communicate with others users across other Matrix federated homeservers.

Prerequisites

Before you begin this guide you’ll need the following:

  • One Ubuntu 16.04 server set up by following this initial server setup guide, including a sudo non-root user and a firewall.

  • Nginx installed on your server (allowing for HTTPS traffic); you can do this by following this Nginx on Ubuntu 16.04 tutorial.

  • A registered domain name set up with the appropriate DNS records by following this hostname tutorial. Which DNS records you need depend on how you’re using your domain.

    • If you’re using your domain exclusively for Synapse, or if you will be using the same server to host your website and Synapse, you only need an A record with the hostname @.
    • If you will be installing Synapse on a separate server, you will need an A record with the hostname set to the subdomain you want to use, like matrix.example.com, and a SRV record with the hostname _matrix._tcp pointing to the same subdomain on port 8448, with the default priority and weights of 10 and 100 respectively. This will tell Matrix clients and homeservers where to find your Synapse installation.

Generate Initial Synapse Config And Signing Key Failed Matrix-synapse Version

Step 1 — Installing Matrix Synapse

Log in to your server as your non-root user to begin.

Before you start installing anything, make sure your local package index is up to date.

Next, add the official Matrix repository to APT.

To make sure your server remains secure, you should add the repository key. This will check to make sure any installations and updates have been signed by the developers and stop any unauthorized packages from being installed on your server.

You’ll see the following output:

After adding the repository, update the local package index so it will include the new repository.

Generate initial synapse config and signing key failed matrix-synapse error

With the repository added, installing Synapse is as simple as running a single APT command.

During the installation, you will be prompted to enter a server name, which should be your domain name. You will also be asked to choose whether or not you wish to send anonymized statistics about your homeserver back to Matrix. Then, Synapse will install.

Once complete, use systemctl to automatically start Synapse whenever your server starts up.

That command only starts Synapse when the whole server starts. Your server is already running, so use systemctl manually to start Synapse now.

Synapse is now installed and running on your server, but you’ll need to create a user before you can start using it.

Step 2 — Creating a User for Synapse

Before you can start using Synapse, you will need to add a user account. Before you can add a new user, you need to set up a shared secret. A shared secret is a string that can be used by anybody who knows it to register, even if registration is disabled.

Use the following command to generate a 32-character string.

Copy the string you create, then open the Synapse configuration file with nano or your favorite text editor.

In the registration section, look for the registration_shared_secret key. Update its value to the random string you copied, inserting it between quotation marks (' '). Remember to activate the key by uncommenting the line (i.e. deleting the # at the beginning of the line).

If you want to enable public registration as well, you can update the value of enable_registration to True here.

Save and close the file.

After modifying the configuration, you need to restart Synapse so the changes can take effect.

Once restarted, use the command line to create a new user. The -c flag specifies the configuration file, and uses the local Synapse instance which is listening on port 8448.

You will be prompted to choose a username and a password. You’ll also be asked if you want to make the user an administrator or not; it’s up to you, but an administrator isn’t necessary for this tutorial.

Once your user is created, let’s make sure the webserver is able to serve Synapse requests.

Generate Initial Synapse Config And Signing Key Failed Matrix-synapse Download

Step 3 — Configuring Nginx and SSL

Matrix clients make requests to https://example.com/_matrix/ to connect to Synapse. You’ll need to configure Nginx to listen for these requests and pass them on to Synapse, which is listening locally on port 8008. You’ll also secure your setup by using SSL backed by Let’s Encrypt.

Generate Initial Synapse Config And Signing Key Failed Matrix-synapse Password

To do this, you’ll create a custom Nginx configuration file for your website. Create this new configuration file.

The location /_matrix block below specifies how Nginx should handle requests from Matrix clients. In addition to the request handling, the /.well-known block makes the directory of the same name available to Let’s Encrypt.

Copy and paste the following into the file.

/etc/nginx/sites-available/example.com

This Nginx server blocks tutorial has more information about how files like these work. When you have configured the server, you can save and close the file.

To enable this configuration, create a symlink for this file in the /etc/nginx/sites-enabled directory.

Test your configuration file for syntax errors by running the command.

Correct the syntax based on the error output, if any. When no errors are reported, use systemctl reload Nginx so the changes take effect.

To finish securing Nginx with a Let’s Encrypt certificate, follow this Let’s Encrypt for Nginx on Ubuntu 16.04 tutorial. Remember to use /etc/nginx/sites-available/example.com instead of the default configuration file. You’ve already added the ~/.well-known block mentioned in Step 2 of that tutorial.

Once Let’s Encrypt is set up, you can move on to configuring the firewall to allow the necessary traffic for Synapse to communicate with other homeservers.

Step 4 — Allowing Synapse through the Firewall

Client traffic connects to Synapse via the HTTPS port 443, (which is already open in your firewall from the Nginx guide). However, traffic from other servers connects directly to Synapse on port 8448 without going through the Nginx proxy, so you need to allow this traffic through the firewall as well.

Check the status of UFW.

It should look like this:

This means that all the necessary traffic is allowed through your firewall. The last step you should take is improving Synapse’s security by updating its SSL certificates.

Step 5 — Securing Federation with SSL (Recommended)

Generate Initial Synapse Config And Signing Key Failed Matrix-synapse Update

Now that Synapse is configured and can communicate with other homeservers, you can increase its security by using the same SSL certificates you requested from Let’s Encrypt at the end of Step 3. By default Synapse uses self signed certificates which do the job, but seeing as you already requested the Let’s Encrypt certificates it’s simple to use those and improve security.

Windows 8.1 enterprise activation key generator. Copy the certificates to your Synapse directory:

In order for these certificates to be updated when they are renewed you need to add these commands to your cron tab. Open it for editing.

Generate Initial Synapse Config And Signing Key Failed Matrix-synapse Error

And add the following lines:

Then save and close the file. Next, open your Synapse configuration file with nano or your favorite text editor.

Using the same certificate you requested from Lets Encrypt in Step 3, replace the paths in the configuration file.

Generate Initial Synapse Config And Signing Key Failed Matrix-synapse Windows 10

Restart Synapse so the configuration changes take effect.

/adobe-premiere-pro-cc-2018-key-generator.html. Everything’s set up, so now you can connect to your homeserver with any Matrix client and start communicating with others. For example, you can use the client on Matrix’s website.

Enter the following for the appropriate fields:

  • Your Matrix ID is in the format @user:server_name (e.g. @sammy:example.com). Other federated servers use this to find where your homeserver is hosted.
  • Your Password is the secure password you set when creating this user.
  • Your Home Server is the server name you chose in Step 1.

Generate Initial Synapse Config And Signing Key Failed Matrix-synapse Windows 7

If you enabled public registration in Step 2, you can also click the Create account link to create a new account or allow others to create a new account on your homeserver.

From there, you can log into rooms and start chatting. The official support room for Matrix is #matrix:matrix.org.

Conclusion

Generate Initial Synapse Config And Signing Key Failed Matrix-synapse Server

In this guide, you securely installed Matrix Synapse with Nginx, backed by SSL certificates from Let’s Encrypt. There are many Matrix clients you can use to connect to your homeserver, and you can even write your own Matrix client or get involved with the project in other ways.