Reinstalling OpenSlides on a fresh VPS: our step-by-step setup


After the performance problems at our first event, we decided not to keep tinkering with the old installation. Instead, we rebuilt OpenSlides from scratch on a new VPS.

The goal was a reproducible setup without years of accumulated configuration, so we could restore it quickly before future meetings.

This is the actual process, including the details that caused trouble.

Version note: These commands document our setup at the time of writing in February 2026. OpenSlides installation files, service names and migration commands may change. Check the current official OpenSlides instructions before using them on a new server.


Starting point

Our new VPS had:

  • Ubuntu LTS
  • 4 vCPUs
  • 8 GB RAM
  • A public IPv4 address
  • An existing domain

We chose to run OpenSlides entirely in Docker and avoid manual changes inside the running containers.

Step 1: Prepare the system

First, update the server:

sudo apt update
sudo apt upgrade -y

Then install Docker and the Compose plugin, using the packages suitable for your Ubuntu version:

sudo apt install -y docker.io docker-compose-plugin
sudo systemctl enable --now docker

Step 2: Prepare OpenSlides

Create a working directory:

mkdir -p /home/oliver/openslides2
cd /home/oliver/openslides2

Our original notes used the project repository:

git clone https://github.com/OpenSlides/OpenSlides.git .

That is the source repository, however, and not necessarily a complete ready-to-run production deployment. Use the deployment method recommended for your OpenSlides release.

In our case we could also take over parts of the existing setup:

  • docker-compose.yml
  • compose.rendered.yml
  • The secrets directory

Don't lose the secrets. Containers may start without the right files but still be unable to communicate with each other. Securely back up the secrets alongside the data.

Step 3: Start the containers

Once the correct Compose configuration is in place:

docker compose up -d
docker compose ps

The services should start and reach a healthy state.

In our environment the important components included:

  • postgres
  • redis
  • datastoreReader
  • datastoreWriter
  • backendManage
  • proxy

If one of them restarts repeatedly, check logs, permissions and configuration before assuming it's a networking issue.

Step 4: Handle database migrations

After moving data or changing versions, database migrations can still be pending.

A message we saw was:

Missing migrations to apply

For the version we were running, the migration command was:

./openslides migrations finalize -a manage:9008 --no-ssl

Then we checked:

./openslides check-server

These are version-specific commands. Don't run a migration against important production data without a backup and checking the current release notes.

Step 5: Test access

Our OpenSlides proxy was listening on port 8000.

From the server we tested:

curl -Ik https://127.0.0.1:8000/

Using plain HTTP against an HTTPS listener can give confusing errors. Match the protocol to the configured listener.

Step 6: Add the domain and reverse proxy

I didn't want to expose the OpenSlides service directly to the internet. We used Caddy as a reverse proxy because it manages TLS certificates automatically.

Our example Caddyfile looked like this:

openslide.street-bbq.de {
  reverse_proxy https://127.0.0.1:8000 {
    transport http {
      tls_insecure_skip_verify
    }
  }
}

Security caveat: The tls_insecure_skip_verify setting disables verification of the upstream certificate. This was a practical shortcut for our local upstream, not something to copy casually when the backend runs on another machine or across an untrusted network. Prefer a properly trusted upstream certificate where possible.

With DNS and connectivity in place, Caddy can obtain a public certificate.

Common first-start problems

These took most of our time:

  • Secrets inaccessible to containers
  • Pending database migrations
  • HTTP used where HTTPS was expected
  • Reverse proxy talking the wrong protocol
  • Accessing the service by IP when it expected the domain

A lot of these symptoms look like network failures. In reality they're usually configuration mistakes.

The result

After rebuilding, OpenSlides ran without the login failures or delays we'd seen before. Voting results appeared promptly and participants could work simultaneously without the system noticeably slowing down.

The biggest improvement wasn't a clever tweak. It was giving the setup enough resources and starting from a configuration we actually understood.

Previous Next