Public and private (web) services

There are a few services I provide to the public for anyone to use, and a few services I run for a limited group of users (mainly friends and family).

Most of the services are hosted in Germany, although some are (additionally) hosted in USA or Canada for redundancy. Maintenance is generally done via ansible. Where possible services are using both IPv6 and IPv4 IP addresses (some are IPv6 only).

Public services


A public teamspeak 3 server with plenty of space and bandwidth for voice chat.


In the past it was used for various groups and still boasts its original banner from -si.ka-
(waaaay back when we played the original counter strike, probably a good 10-15 years ago).


Maintenance is “when teamspeak updates are released” and outside of peak times. The standard downtime for users is 2-5 seconds. If a downtime longer than a minute is expected, I post it in the “Message of the day” of the server a week in advance.


Internal services


I usually have one or more game servers running depending on what is currently of interest. Currently I’m using an AMP setup to control and manage multiple game server instances.


Nothing too elaborate, just proxy servers located in Europe and North America with user authentication.


VPN servers located in Europe and North America for tasks that require more than just a proxy or to access networks that aren’t using public IPs.


Your usual mail server IMAP and Webmail. Supports email sub-addressing with “+” and “-” to help keep track of where an email was used.
Uses DKIM, SPF and DMARC as well as Spamassassin to keep Spam and misuse of the domains contained as well as possible. I write about the setup occasionally on the blog.
Support for server-side sieve filtering and two MX servers (Europe and North America) so nothing gets lost in case of an unplanned downtime.


This one is kinda in both categories, technically the wiki is publicly available, but large parts are walled off and only view able for logged in users.
I currently use confluence as the software for this wiki since it is used by people with various degrees of technical knowledge and it (currently) has very affordable licenses for small user bases.

Code repository

You can’t really maintain code without a version control tool. Subversion is still in use for most older stuff. Although I do have a gitlab in my test environment just waiting to see some action and eventually replace svn with git.

Monitoring and Logging

Graylog and Netdata are in place to monitor server and application metrics, as well as collect and visualize logs.