Notes on how to troubleshoot Pleroma Installation

My social network: social.arinbasu.online

I have been hosting social.arinbasu.online for my personal social media site based on a fediverse app named Pleroma (link?). Pleroma is a fantastic fediverse app, and extremely lightweight with small footprint and it has tons of features. So, if you want to host one for yourself, this could be a perfect solution if you want. I also use the Soapbox Frontend as Soapbox is another fantastic skin that allows a lot of features including tags, replies, and microblogging.

While this is all fun, I also need to troubleshoot my Pleroma instance with Soapbox instance now and then. Basically, every 90 days make sure you at least log on to your instance via the command line and issue

sudo systemctl stop nginx
sudo systemctl certbot renew
sudo systemctl start nginx

This makes sure that nginx gets stopped and started on time and also, that the letsencrypt certificate is timely renewed. It’s ideal to use a systemd for this purpose but I find this somewhat easier to keep tab of what is happening on the server. The only thing to keep in mind is to set a date and do it.

The second part is updating the Pleroma instance. Here are the instructions from https://docs.soapbox.pub/backend/administration/updating/

sudo -Hu pleroma bash # this changes to pleroma user
cd /opt/pleroma #…