Troubleshooting

Full Docker Cleanup

If you encounter issues with Docker containers, images, or volumes and need to start fresh, you can perform a complete Docker cleanup. This will remove all containers, images, volumes, and custom networks.

Warning: This will remove ALL Docker containers, images, and volumes on your system, not just Rybbit-related ones. Make sure you don't have other important Docker containers running.

Steps for Complete Docker Cleanup

Remove your environment file

rm .env

Stop all running containers:

docker stop $(docker ps -q)

Remove all containers (both running and stopped):

docker rm -f $(docker ps -aq)

Remove all images:

docker rmi -f $(docker images -q)

Remove all volumes:

docker volume rm -f $(docker volume ls -q)

Remove all custom networks (preserves default networks):

docker network rm $(docker network ls | grep -v "bridge\|host\|none" | awk '{print $1}')

Alternative: Rybbit-Specific Cleanup

If you only want to clean up Rybbit-related Docker resources without affecting other containers, use these commands instead:

# Stop and remove Rybbit containers
docker-compose down

# Remove Rybbit images
docker-compose down --rmi all

# Remove Rybbit volumes (this will delete your data!)
docker-compose down --volumes

# Complete Rybbit cleanup
docker-compose down --rmi all --volumes --remove-orphans

After Cleanup

Once you've completed the cleanup, you can restart Rybbit by following the setup instructions:

# Copy environment file
cp .env.example .env

# Edit .env with your configuration
# Then start the services
docker-compose up -d

ClickHouse keeps crashing on a Proxmox VM

ClickHouse requires the SSE 4.2 instruction set. Proxmox VMs default to a generic CPU type (like kvm64 or x86-64-v2-AES) that doesn't expose all of the host CPU's instruction sets to the VM, which causes ClickHouse to fail with Illegal instruction errors or get stuck in a restart loop.

To fix this, set the VM's CPU type to host so it passes through the physical CPU directly:

Open the VM's hardware settings

In the Proxmox web UI, select your VM, then go to Hardware → Processors → Edit.

Set the CPU type to `host`

Change the Type dropdown to host and click OK.

Fully stop and start the VM

A reboot from inside the guest is not enough — do a full Stop and then Start from Proxmox for the CPU change to take effect.

The host CPU type can prevent live migration between Proxmox nodes with different CPU models. If you need migration, any CPU type that includes SSE 4.2 (e.g. x86-64-v2-AES on a host that supports it, or newer) may also work — but host is the most reliable option.

I ran out of disk space

Regular web analytics events take up almost no space in Clickhouse, so it is very unlikely that you ran out of disk space from from this. There are two main reasons why you might have run out of disk space:

1. You are using session replay

On self-hosted instances where we don't have access to S3 compatible object storage, session replays are stored in Clickhouse. Each session replay is at least 1000x the data footprint of the web analytics events. So it's very easy to run out of disk space.

We have a 30 day retention policy for session replays events, so if you turn off session replay, your disk space will slowly come back. If you need to immediately free up space, you can truncate the session replays table:

docker exec -it clickhouse clickhouse-client --database analytics

TRUNCATE TABLE session_replay_events;
TRUNCATE TABLE session_replay_metadata;

2. You didn't mount the Clickhouse log suppression configs

In our docker-compose.yml, we have a config for Clickhouse that suppresses logs. Clickhouse stores a ton of logs in the log tables by default. This will quickly fill up your disk space if left unchecked.

If you follow the standard installation process, the configs are already mounted for you. If you rolled your own Docker setup, you need to mount the configs manually.

Troubleshooting

On this page