From diaspora* project wiki
Revision as of 12:23, 25 April 2016 by Zauberstuhl (talk | contribs) (Created page with "{{Work_in_progress}} This wiki-page is about setting up the chat application on your Diaspora installation. = Installation/Update = If you're running the development versio...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
»» Work in progress
This article is a work in progress, it may contain incomplete or inaccurate information. There may be additional information on the talk page.

This wiki-page is about setting up the chat application on your Diaspora installation.


If you're running the development version of Diaspora and want to try out this feature, all you have to do is a regular update.


You'll find all required configuration parameters in diaspora.yml.example. If you'd like to activate the chat feature you have to copy paste the chat section from diaspora.yml.example to your actual diaspora.yml configuration file and activate the chat globally:

    enabled: true

If you have already a working XMPP server and need only the front-end:

    enabled: true
      enabled: false

It is also possible to configure the port and address of the BOSH service. You'll also find the required parameters in diaspora.yml.example with a small description.

Firewall Ports

If your server is behind a firewall or in a virtual environment without direct internet access (e.g. kvm/qemu). You have to open a few ports on your router (redirect ports in kvm):

  • port 5269 if you want that your xmpp server can communicate with other xmpp server (this is necessary if you want to communicate with other users on different pods)
  • port 5222 if you want that your user can login with different clients (e.g. #Pidgin)

UFW - Uncomplicated Firewall

(Will be shipped in the newer Ubuntu versions.)

sudo ufw allow 5269/tcp
sudo ufw allow 5222/tcp


FirewallD is used by RedHat/CentOS/Fedora based distributions. Open up the required ports permanently and add them to the public zone.

firewall-cmd --add-port=5222 --zone=public --permanent
firewall-cmd --add-port=5269 --zone=public --permanent


Check the OpenWRT documentation here..


Enable IP forwarding on your router:

echo "1" > /proc/sys/net/ipv4/ip_forward


sysctl net.ipv4.ip_forward=1

Redirect all traffic on the specified ports to

iptables -t nat -A PREROUTING -p tcp --dport 5269 -j DNAT --to-destination
iptables -t nat -A PREROUTING -p tcp --dport 5222 -j DNAT --to-destination
iptables -t nat -A POSTROUTING -j MASQUERADE


Edit your configuration file:

virsh -c qemu:/system edit <DOMAIN>

And add at the end before the ending-tag </domain>

  <qemu:arg value='-redir'/>
  <qemu:arg value='tcp:5269::5269'/>
  <qemu:arg value='-redir'/>
  <qemu:arg value='tcp:5222::5222'/>

Finally reboot:

virsh -c qemu:/system reboot <DOMAIN>


»» Important
For encrypted communication we need a certificate and the related key.

Put your files in the certificate-folder, you can configure the path in diaspora.yml under the chat section.

The default path is /path_to_diaspora_installation/config/certs/.
Also the domain name should be included in the file name e.g.:


Run it

If you are finished configuring the chat server you can start Diaspora as normal:


Log into Diaspora and you should see the web client in the right corner. You can also log into it with your favorite desktop client like Pidgin.

For that use your Diaspora ID and your Diaspora password.


JSXC is hidden, even after activating it


Go to your http://about:config and check whether you set




Reverse it and JSXC should be displayed, again!

I have no contacts in my roster

Please consider that you have to add chat privilege to your aspects!

You can toggle that privilege for every existing aspect:

Or you can do that while creating a new aspect:

(original post

Browser blocks mixed-content

You enabled the chat feature but haven't configured BOSH! That
could lead to mixed-content problems with the http clients. Please
think about editing your proxy configuration as described in:


The internal xmpp server does not support https and
even if we implement it, we would ran into certificate issues.
The problem with mixed-content is described here:

The easiest way of avoiding certificate and mixed-content issues is to use a proxy (see apache and nginx section below)!

If you finished configuring your proxy settings you also have to adjust diaspora.yml!
For my examples below, it would look like this:

        proxy: true
        bind: '/http-bind'


RewriteEngine On
RewriteCond %{REQUEST_URI} ^/http-bind
RewriteRule ^/(http\-bind.*)$ balancer://chat%{REQUEST_URI} [P,QSA,L]
RewriteRule ^/(.*)$ balancer://diaspora%{REQUEST_URI} [P,QSA,L]
<Proxy balancer://diaspora>
<Proxy balancer://chat>


upstream chat_cluster {
  server localhost:5280;

location /http-bind {
  proxy_set_header X-Real-IP $remote_addr;
  proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  proxy_set_header Host $http_host;
  proxy_set_header X-Forwarded-Proto https;

  proxy_redirect off;
  proxy_connect_timeout 5;
  proxy_buffering       off;

  proxy_read_timeout    70;
  keepalive_timeout     70;
  send_timeout          70;

  client_max_body_size 4M;
  client_body_buffer_size 128K;
  proxy_pass http://chat_cluster;


On default Vines will log to log/prosody.log and has a log level of info set. Un-comment in your diapsora.yml error: 'log/prosody.err to set the log level to debug-mode. The debug level logs all XML sent and received by the server.

        info: 'log/prosody.log'
        error: 'log/prosody.err'
        debug: false