Installation of Etherpad

Etherpad logo
Etherpad is a free system for collaborative editing of text documents well suited to both working in parallel and serially. It is provided courtesy of the Etherpad Foundation and the developers

Objective: Install a private instance of Etherpad.org secured with TLS encryption and configuring the system to have good level of controll over who gets to see and edit what i.e. to authenticate the users.

Instructions used:


Basic install

Install the dependencies

sudo apt-get install gzip git curl python libssl-dev pkg-config build-essential

You will also need to download and install a working node.js system. The installation manual does recommend against using the version that apt-get installs and go for the downloadable one.

The official Node.js installation guide gives the following instructions for a Debian8:

curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -

followed by

sudo apt-get install -y nodejs

Which worked just fine installing the nodejs from deb.nodesource.com

Next create the directory where you want Etherpad to reside and git clone into the source tree

git clone git://github.com/ether/etherpad-lite.git

and change directory to there and run

bin/run.sh

and

lynx http://127.0.0.1:9001

and you should see your Etherpad installation.

TLS encryption with LetEncrypt.org certificates

Let's Encrypt logo
Let’s Encrypt is a free certification authority kindly provided by Internet Security Research Group (ISRG)

Objectives to the accomplished

  1. First I will be getting and installing a new cert for use on pad.byjuho.fi which will host an Etherpad instance to fulfill my secure textual collaboration needs safely.
  2. Second I will be replacing the shortly expiring commercial certificate for *.consumium.org. So far I know that I can have the old cert still in place and insert the new certs under a subjectAltName. This way the free social media that I host can continue operating normally (hopefully) without any downtime.

How I did it

The definitive instructions from readthedocs.io I found only sometime after starting this were very helpful as they almost always are.

https://letsencrypt.org/getting-started/ recommends using

CertBot logo
CertBot is a free cert management solution provided by The Electronic Frontier Foundation (EFF)

CertBot from Electronic Frontier Foundation to automate the installation of LetsEncrypt certificates so I’m doing that.

CertBot takes as arguments your web server and operating system and provides instructions customized by those.

ByJuho.fi is being served by an Apache2.4 on a Debian8.5 so I chose those.

CertBot points to instructions for enabling backports on my system. Which I promptly followed successfully.

Then you naturally need to

sudo apt-get update

before the backports start to work.

After that

sudo apt-get install python-certbot-apache -t jessie-backport

Runs fine and installs a bunch of python candy

Next I ran

sudo certbot --apache

as instructed by CertBot interactive website. That complained that it did not find any ‘ServerName’s in the configuration files which is slightly strange. When answering ‘no’ to the “Do you want to proceed?” question it exited and hinted to specify domain name with the ‘–domains’ switch

sudo certbot --apache --domains byjuho.fi

A blue screen comes up that asks for the “emergency” email address. Put one that you will never lose like an https://iki.fi address which I’ve used for over 20 yrs now and which is valid for a lifetime.

Next the blue screen asks if you want to have all traffic redirected to TLS encrypted. I chose to allow normal http too.

Program exits and gives good advice to check the installed cert with the awesome free test tool by SSLLabs so I proceeded to do so. Certbot apparently knows its stuff since the site got an ‘A’ rating for the things SSL.

SSLTest rating A
Parasta A-ryhmää / TLS protection rated A by QUALLABS SSL LAB’s free awesome SSLTEST service

Automating renewal of certificates

LetsEncrypt.org certificates are valid only for 90 days. Probably due to meticulous planning and execution to maximize security so we want to automate the renewal.

Now CertBot site instructs to test automatic renewal arrangement by issuing command

sudo certbot renew --dry-run

and it reports that everything seems to be in order to automate the renewal so I proceeded to do so with

crontab -e

and inserted instructions to run on quiet the renewal script twice a day 12-hours apart. The command to be run is given as

certbot renew --quiet

But that will fail unless run with sudo because it cannot access certain files so you need to set the cronjob as superuser. Type

sudo su

give password and then run

crontab -e

(See here for practical examples of crontab entry syntax). Exit super user account with ctrl-d and you are done automating the renewal of the certs.

The encrypted URL now leads to the default Apache2 on Debian landing page “It works.. blahblahblah…” so I need to make a new VirtualHost directive for the encrypted site in /etc/apache2/sites-enabled/001-hosts which is where I keep the directives.

So I need to figure where the CertBot put the certificate and the key.

CertBot puts the very secret key and the very public certificate in

‘/etc/letsencrypt/live/domain.tld’ and the automagic from the blue screen creates a VirtualHost entry in ‘/etc/apache2/sites-enabled/000-default-le-ssl.conf’. After I made a normal VirtualHost entry in ‘/etc/apache2/sites-enabled/001-sites.conf’ and commented everything out in the 000-default-le-ssl.conf this blog is now available also in TLS protected https://ByJuho.fi.

Friendly folks at #freenode pointed out that

sudo apachectl -S

is very useful for locating problem points regarding conflicting VirtualHost directives

Next I am going to figure out if the commenting out stuff from 000-default-le-ssl.conf has any adverse effects. It seems the files with lower prefixed number takes precedence.


Next I try to replicate the necessary steps described in this blog post to actually enable https://pad.byjuho.fi

All that was needed to bring up the default Debian/Apache “it works page” over TLS encrypted https was one run of

sudo certbot --apache --domains pad.byjuho.fi

and fix the VirtualHost directive to your liking to actually serve your content.


Getting new certs with nginx.

There doesn’t seem to be quite the same level of automation with Nginx hosted sites than the Apache ones.

sudo certbot certonly --webroot -d d.consumium.org --webroot-path /var/www/diaspora

Is what I used to successfully get the new certificates in place.

Installation of GNU MediaGoblin on Debian GNU/Linux

Installing GNU MediaGoblin 0.9.0 with Py3 support and using Postgreql as RDBMS on GNU/Linux system

Installing GNU MediaGoblin (over and over again)

Here I document how to install the GNU MediaGobin 0.9.0, The Three Gobliners on Debian GNU/Linux.

Why over and over again?

Short answer: The installation instructions given are required to be read to be completely understood. So I’ll be installing again a third time.

  • GNU MediaGoblin 0.8.0 I accidentally set to use SQLite, instead of Postgresql the intended database backend. No migration script exists so reinstall was needed
  • GNU MediaGoblin 0.9.0 I managed to install the 0.9.0 using Py2 instead of Py3.
  • GNU MediaGoblin 0.9.0 with python3 version is what I am aiming at the third time around installing
    UPDATE: Seems installation of GNU MediaGoblin 0.9.0 with python3 support is currently impossible if the idea was to use flup and fcgi. Follow this ticket for updates on the situation.

Since the installation using python3 is impossible at the moment I have installed the py2 version instead at https://media.consumium.org. using py2, Nginx and fcgi for serving content.

Previously installed on the server are Nginx for webserver with TLS security enabled. Services already running on the server are https://hub.consumium.org (Hubzilla), https://d.consumium.org (diaspora), https://social.consumium.org (GNU social) and https://friendica.consumium.org so some of the dependencies are likely there.


I run into some problems which caused that the Postgresql cluster was not created and started. I got good help from StuckMojo @ #postgresql @ freenode irc.

I fixed the situation by running

  • ‘nano /etc/locale.gen’ and uncommented the Finnish and US English locales
  • ‘sudo locale-gen’ generated the locales according to /etc/locale.gen
  • ‘sudo pg_createcluster –locale=en_US.UTF-8 9.4 main’ creates the cluster and
  • ‘sudo pg_ctlcluster 9.4 main start’ starts the cluster
  • check its status with ‘sudo pg_lsclusters’

Now should be ready to create the database user and the database.