Poddery - Diaspora, Matrix and XMPP - Revision history

Pravs: Redirect XMPP to durare and clarify nginx configuration

2025-10-24T14:41:56Z

Redirect XMPP to durare and clarify nginx configuration

@@ Line 18: / Line 18: @@
 === Chat/XMPP ===
-* [https://prosody.im/ Prosody] is used as the XMPP server which is modern and lightweight.
+* This is moved to Durare.org server Virtual Host. See https://gitlab.com/piratemovin/diasp.in/-/wikis/XMPP-durare.org-setup
 === Chat/Matrix ===
@@ Line 35: / Line 33: @@
 == Backend Services ==
 === Web Server / Reverse Proxy ===
-* Nginx web server which also acts as front-end (reverse proxy) for Diaspora and Matrix.
+* Nginx web server which also acts as front-end (reverse proxy) for Diaspora and Matrix. By default all https requests to 443 are passed to diaspora. Requests starting with
 === Database ===
@@ Line 256: / Line 256: @@
 == Chat/XMPP ==
-* Steps for setting up Prosody is given at https://wiki.debian.org/Diaspora/XMPP
+* See https://gitlab.com/piratemovin/diasp.in/-/wikis/XMPP-durare.org-setup
 == TLS ==

Ravi: /* TLS */ Update certificate renewal steps

2025-10-11T19:06:02Z

TLS: Update certificate renewal steps

← Older revision		Revision as of 00:36, 12 October 2025
Line 328:		Line 328:
	''34 2 * * 1 /etc/init.d/prosody reload''		''34 2 * * 1 /etc/init.d/prosody reload''

	* Manually updating TLS certificate:		===SSL certificate renewal===
	~~letsencrypt certonly --webroot --agree-tos -w~~ /~~usr~~/~~share/diaspora~~/~~public -d poddery.com -d www.poddery.com -d test.poddery.com -d groups.poddery.com -~~d ~~fund.poddery.com -w~~ /~~usr~~/~~share/diaspora/public/save~~ -~~d save.poddery.com~~ -~~w /var/www/riot~~ -~~d chat~~.poddery.~~com~~		On the 12th of October 2025, all the certificates were removed and were recreated. [https://codema.in/d/XUfAOrPW/poddery-server-certificates-recreated This thread] documents all those steps.
	* To include an additional subdomain such as fund.~~poddery.com use with --expand parameter as shown below~~
	letsencrypt certonly --webroot --agree-tos --expand -w /usr/share/diaspora/public -d poddery.com -d www.poddery.com -d test.poddery.com -d groups.poddery.com -d fund.poddery.com -w /usr/share/diaspora/public/save/ -d save.poddery.com -w /var/www/riot/ -d chat.poddery.com		When renewing certificates on the poddery server, make sure to follow the following steps.

			# Stop nginx by running
			sudo systemctl stop nginx

			# Renew certificates for all the domains
			sudo certbot renew

			Follow the prompts by certbot to renew certificates for all the domains.

			# Start nginx after the renewal is successful
			sudo systemctl start nginx

	==Backup==		==Backup==

Ravi: Fix 1 spelling

2025-10-07T20:44:50Z

Fix 1 spelling

← Older revision		Revision as of 02:14, 8 October 2025
Line 1:		Line 1:
	We run decentralized and federated [https://diasporafoundation.org/ Diaspora] social ~~netowrk~~, [https://xmpp.org/ XMPP] and [https://matrix.org Matrix] instant messaging services at [https://poddery.com poddery.com]. Along with Diaspora, Poddery username and password can be used to access XMPP and Matrix services as well. [https://chat.poddery.com chat.poddery.com] provides Element client (accessed by a web browser), which can be used to connect to any Matrix server without installing the Element app.		We run decentralized and federated [https://diasporafoundation.org/ Diaspora] social network, [https://xmpp.org/ XMPP] and [https://matrix.org Matrix] instant messaging services at [https://poddery.com poddery.com]. Along with Diaspora, Poddery username and password can be used to access XMPP and Matrix services as well. [https://chat.poddery.com chat.poddery.com] provides Element client (accessed by a web browser), which can be used to connect to any Matrix server without installing the Element app.

	= Environment =		= Environment =

Ravi: Replace Riot with Element

2025-10-07T20:42:59Z

Replace Riot with Element

← Older revision		Revision as of 02:12, 8 October 2025
Line 1:		Line 1:
	We run decentralized and federated [https://diasporafoundation.org/ Diaspora] social netowrk, [https://xmpp.org/ XMPP] and [https://matrix.org Matrix] instant messaging services at [https://poddery.com poddery.com]. Along with Diaspora, Poddery username and password can be used to access XMPP and Matrix services as well. [https://chat.poddery.com chat.poddery.com] provides ~~Riot~~ client (accessed by a web browser), which can be used to connect to any Matrix server without installing ~~a Riot~~ app~~/client~~.		We run decentralized and federated [https://diasporafoundation.org/ Diaspora] social netowrk, [https://xmpp.org/ XMPP] and [https://matrix.org Matrix] instant messaging services at [https://poddery.com poddery.com]. Along with Diaspora, Poddery username and password can be used to access XMPP and Matrix services as well. [https://chat.poddery.com chat.poddery.com] provides Element client (accessed by a web browser), which can be used to connect to any Matrix server without installing the Element app.

	= Environment =		= Environment =

Ravi: /* Workers */ It was very hard to distinguish one service from the other in the previous list. So, I made a new line for each of the services.

2025-10-07T13:10:41Z

Workers: It was very hard to distinguish one service from the other in the previous list. So, I made a new line for each of the services.

← Older revision		Revision as of 18:40, 7 October 2025
Line 234:		Line 234:
	* These services must be enabled:		* These services must be enabled:

	matrix-synapse@synchrotron.service matrix-synapse@federation_reader.service matrix-synapse@event_creator.service matrix-synapse@federation_sender.service matrix-synapse@pusher.service matrix-synapse@user_dir.service matrix-synapse@media_repository.service matrix-synapse@frontend_proxy.service matrix-synapse@client_reader.service matrix-synapse@synchrotron_2.service		matrix-synapse@synchrotron.service
			matrix-synapse@federation_reader.service
			matrix-synapse@event_creator.service
			matrix-synapse@federation_sender.service
			matrix-synapse@pusher.service
			matrix-synapse@user_dir.service
			matrix-synapse@media_repository.service
			matrix-synapse@frontend_proxy.service
			matrix-synapse@client_reader.service
			matrix-synapse@synchrotron_2.service

	To load balance between the 2 synchrotrons, We are running [https://github.com/Sorunome/matrix-synchrotron-balancer matrix-synchrotron-balancer]. It has a systemd file at <code>/etc/systemd/system/matrix-synchrotron-balancer</code>. The files are in <code>/opt/matrix-synchrotron-balancer</code>		To load balance between the 2 synchrotrons, We are running [https://github.com/Sorunome/matrix-synchrotron-balancer matrix-synchrotron-balancer]. It has a systemd file at <code>/etc/systemd/system/matrix-synchrotron-balancer</code>. The files are in <code>/opt/matrix-synchrotron-balancer</code>

Ravi: /* Prosody */

2025-01-08T08:54:19Z

Prosody

← Older revision		Revision as of 14:24, 8 January 2025
Line 481:		Line 481:
	For taking the dump, the following was run from the backup-server		For taking the dump, the following was run from the backup-server
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	ssh user@poddery-server 'mysqldump -u prosody --password="$(cat <path/to/password-file>)" prosody \| gzip' > backups/prosody-backup~~-2024-10-27~~.sql.gz		ssh user@poddery-server 'mysqldump -u prosody --password="$(cat <path/to/password-file>)" prosody \| gzip' > backups/prosody-backup.sql.gz
	</syntaxhighlight>		</syntaxhighlight>

Ravi: /* Prosody */

2025-01-08T08:48:07Z

Prosody

@@ Line 479: / Line 479: @@
 * `/etc/prosody` for config files
-For taking the dump, the following was run from the backup-server<syntaxhighlight lang="bash">
+For taking the dump, the following was run from the backup-server
 ssh user@poddery-server 'mysqldump -u prosody --password="$(cat <path/to/password-file>)" prosody | gzip' > backups/prosody-backup-2024-10-27.sql.gz
 </syntaxhighlight>

Ravi: /* Backup steps on 7th Jan 2025 */

2025-01-08T08:41:26Z

Backup steps on 7th Jan 2025

← Older revision		Revision as of 14:11, 8 January 2025
Line 456:		Line 456:
	===Backup steps on 7th Jan 2025===		===Backup steps on 7th Jan 2025===
	====Matrix-synapse====		====Matrix-synapse====
	For synapse, the following files were backed up:		For synapse, the following files were backed up:
	~~- Dump of postgresql using `pg_dump`~~
	~~- `/etc/matrix-synapse`~~
	~~- `/var/lib/static/synapse/media`~~

	~~In order to access the poddery server from the backup server (with your public ssh keys added to both the servers in~~ `~/~~.ssh~~/~~authorized~~-~~keys~~`~~), run the following command in your local system:~~		* Dump of postgresql database using `pg_dump`
			* `/etc/matrix-synapse` - contains config files
			* `/var/lib/static/synapse/media` -- contains uploaded media files

	`eval "$(ssh-agent -s)"`		In order to access the poddery server from the backup server (with your public ssh keys added to both the servers in `~/.ssh/authorized-keys`), run the following command in your local system:<syntaxhighlight lang="bash">
			eval "$(ssh-agent -s)"
			</syntaxhighlight>followed by<syntaxhighlight>
			ssh user@server -o "ForwardAgent yes" -o "AddKeysToAgent yes"
			</syntaxhighlight>on the local system.

	~~followed by~~		The dump was taken using the command from the [https://element-hq.github.io/synapse/latest/usage/administration/backups.html#quick-and-easy-database-backup-and-restore official docs]:<syntaxhighlight>
			ssh user@poddery-server 'sudo -u postgres pg_dump -Fc --exclude-table-data e2e_one_time_keys_json synapse' > synapse-2025-01-07.dump
	~~`ssh user@server -o "ForwardAgent yes" -o "AddKeysToAgent yes"`~~		</syntaxhighlight>
	~~on the local system.~~

	The dump was taken using the command from the [https://element-hq.github.io/synapse/latest/usage/administration/backups.html#quick-and-easy-database-backup-and-restore official docs]:

	`ssh user@poddery-server 'sudo -u postgres pg_dump -Fc --exclude-table-data e2e_one_time_keys_json synapse' > ~~poddery-backups/matrix-synapse/~~synapse-2025-01-07.dump`

	====Prosody====		====Prosody====
	~~The~~ following were ~~backed up for prosody~~:		For backing up prosody, the following were copied:

	* Dump of the database using `mysqldump`		* Dump of the database using `mysqldump`

Ravi: /* Prosody */

2025-01-08T08:35:29Z

Prosody

← Older revision		Revision as of 14:05, 8 January 2025
Line 476:		Line 476:
	====Prosody====		====Prosody====
	The following were backed up for prosody:		The following were backed up for prosody:
	~~- Dump of the database using `mysqldump`~~
	~~- `/var/lib/prosody` for media files~~
	~~- `/etc/prosody` for config files~~

	For taking the dump, the following was run from the backup-server		* Dump of the database using `mysqldump`
	`ssh user@poddery-server 'mysqldump -u prosody --password="$(cat <path/to/password-file>)" prosody \| gzip' > backups/prosody-backup-2024-10-27.sql.gz`		* `/var/lib/prosody` for media files
			* `/etc/prosody` for config files

			For taking the dump, the following was run from the backup-server<syntaxhighlight lang="bash">
			ssh user@poddery-server 'mysqldump -u prosody --password="$(cat <path/to/password-file>)" prosody \| gzip' > backups/prosody-backup-2024-10-27.sql.gz
			</syntaxhighlight>

	= Troubleshooting =		= Troubleshooting =

Ravi: Add backup steps

2025-01-08T08:31:33Z

Add backup steps

← Older revision		Revision as of 14:01, 8 January 2025
Line 453:		Line 453:

	$ ps -ef \| grep receiver		$ ps -ef \| grep receiver

			===Backup steps on 7th Jan 2025===
			====Matrix-synapse====
			For synapse, the following files were backed up:
			- Dump of postgresql using `pg_dump`
			- `/etc/matrix-synapse`
			- `/var/lib/static/synapse/media`

			In order to access the poddery server from the backup server (with your public ssh keys added to both the servers in `~/.ssh/authorized-keys`), run the following command in your local system:

			`eval "$(ssh-agent -s)"`

			followed by

			`ssh user@server -o "ForwardAgent yes" -o "AddKeysToAgent yes"`
			on the local system.

			The dump was taken using the command from the [https://element-hq.github.io/synapse/latest/usage/administration/backups.html#quick-and-easy-database-backup-and-restore official docs]:

			`ssh user@poddery-server 'sudo -u postgres pg_dump -Fc --exclude-table-data e2e_one_time_keys_json synapse' > poddery-backups/matrix-synapse/synapse-2025-01-07.dump`

			====Prosody====
			The following were backed up for prosody:
			- Dump of the database using `mysqldump`
			- `/var/lib/prosody` for media files
			- `/etc/prosody` for config files

			For taking the dump, the following was run from the backup-server
			`ssh user@poddery-server 'mysqldump -u prosody --password="$(cat <path/to/password-file>)" prosody \| gzip' > backups/prosody-backup-2024-10-27.sql.gz`

	= Troubleshooting =		= Troubleshooting =