Plausible Analytics is an open-source, self-hosted web analytics tool that focuses on simplicity and privacy. It measures your website’s traffic and visitor activity without using cookies or tracking personal data. It’s a good option for developers and businesses that need website analytics while keeping user data private.

In this article, you deploy Plausible Analytics on a Linux server using Docker and Docker Compose. The setup includes installing required packages, configuring the Plausible environment, and running the application in containers. You also configure Nginx as a reverse proxy, enable HTTPS with Let's Encrypt, and secure the installation for production use.

Prerequisites

Before you begin, ensure you:

• Have access to a Linux server (such as Ubuntu, Debian, or Fedora) as a non-root user with sudo privileges.
• Install Docker and Docker Compose.
• Configure a domain name, such as plausible.example.com, to point to your server's public IP address.

Configure Plausible Environment

Plausible uses environment variables to define the base URL, administrator account, and application settings. Follow the steps below to create the environment file and update the Docker Compose configuration.

1. Create a directory for Plausible.

   console Copy

   $ mkdir ~/plausible
   

   Explain Code

2. Navigate to the Plausible directory.

   console Copy

   $ cd ~/plausible
   

   Explain Code

3. Clone the Plausible Community Edition repository.

   console Copy

   $ git clone https://github.com/plausible/community-edition.git
   

   Explain Code

4. Navigate to the project directory.

   console Copy

   $ cd community-edition
   

   Explain Code

5. Generate a random secret key for Plausible.

   console Copy

   $ openssl rand -base64 64 | tr -d '\n'
   

   Explain Code

   Copy the generated value to use as the secret key in the environment file in the next step.

6. Create and open the environment configuration file.

   console Copy

   $ nano .env
   

   Explain Code

7. Add the following configuration to the file.

   ini Copy

   ADMIN_USER_EMAIL=admin@example.com
   ADMIN_USER_NAME=admin
   ADMIN_USER_PWD=ADMIN_PASSWORD
   BASE_URL=https://plausible.example.com
   SECRET_KEY_BASE=YOUR_SECRET_KEY_BASE
   
   DATABASE_URL=postgres://postgres:postgres@plausible_db:5432/plausible_db
   CLICKHOUSE_DATABASE_URL=http://plausible_events_db:8123/plausible_events_db
   

   Explain Code

   Replace:

   • admin@example.com with your email address.
   • ADMIN_PASSWORD with a strong password.
   • plausible.example.com with the domain name that points to your server.
   • YOUR_SECRET_KEY_BASE with the random key you generated in the previous step.

   Save the file and exit the editor.

8. Create a Docker Compose override file to expose the Plausible port.

   console Copy

   $ nano compose.override.yaml
   

   Explain Code

   Add the following configuration.

   yaml Copy

   services:
     plausible:
       ports:
         - 127.0.0.1:8000:8000
   

   Explain Code

   Save the file and exit the editor. Docker Compose automatically merges this file with compose.yml when starting the containers.

Deploy Plausible Analytics

With the environment configured, the next step is to bring Plausible Analytics online. This section uses Docker Compose to launch the application, database, and event processing services and ensures they are running properly before enabling HTTPS.

1. Start the Plausible containers in detached mode.

   console Copy

   $ docker compose up -d
   

   Explain Code

2. Verify that all containers are running.

   console Copy

   $ docker compose ps
   

   Explain Code
   Note

   For more information on managing a Docker Compose stack, see the How To Use Docker Compose article.

Set Up Nginx Reverse Proxy and HTTPS

To make Plausible accessible over the internet and secure all traffic with HTTPS, you need to place Nginx in front of the application as a reverse proxy. Nginx forwards incoming requests to Plausible’s internal service, while Certbot issues and manages TLS certificates from Let’s Encrypt.

Configure Nginx as a Reverse Proxy

1. Update the server’s package information index.

   console Copy

   $ sudo apt update
   

   Explain Code

2. Install the Nginx web server.

   console Copy

   $ sudo apt install nginx -y
   

   Explain Code

3. Create a new Nginx configuration file for Plausible.

   console Copy

   $ sudo nano /etc/nginx/sites-available/plausible.conf
   

   Explain Code

4. Add the following configuration.

   ini Copy

   server {
       listen       80;
       listen       [::]:80;
       server_name  plausible.example.com;
   
       access_log  /var/log/nginx/plausible.access.log;
       error_log   /var/log/nginx/plausible.error.log;
   
       location / {
         proxy_pass http://127.0.0.1:8000;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_http_version 1.1;
         proxy_set_header Upgrade $http_upgrade;
         proxy_set_header Connection "Upgrade";
     }
   }
   

   Explain Code

   Replace plausible.example.com with your domain.

   Save the file and exit the editor.

5. Enable the configuration.

   console Copy

   $ sudo ln -s /etc/nginx/sites-available/plausible.conf /etc/nginx/sites-enabled/
   

   Explain Code

6. Test the Nginx configuration.

   console Copy

   $ sudo nginx -t
   

   Explain Code

   You should see:

   nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
   nginx: configuration file /etc/nginx/nginx.conf test is successful

7. Reload Nginx to apply the changes.

   console Copy

   $ sudo systemctl reload nginx
   

   Explain Code

Install Certbot and Enable HTTPS

1. Install Certbot and the Nginx plugin.

   console Copy

   $ sudo apt install certbot python3-certbot-nginx -y
   

   Explain Code

2. Allow traffic through your firewall to port 80 and 443. Port 80 is required for the ACME SSL challenge (used by Let's Encrypt), and port 443 is required to access the Plausible dashboard securely.

   console Copy

   $ sudo ufw allow 80,443/tcp
   

   Explain Code

3. Request a TLS certificate and enable HTTPS with the command below. Replace plausible.example.com with your domain name, and admin@example.com with your email.

   console Copy

   $ sudo certbot --nginx -d plausible.example.com -m admin@example.com --agree-tos --no-eff-email
   

   Explain Code

   This command requests a Let’s Encrypt TLS certificate and automatically configures Nginx to use HTTPS for the specified domain.

Test and Access Plausible

In this section, you verify the deployment by creating an administrator account, adding a website, and confirming that analytics data is collected correctly.

1. Open your browser and navigate to the Plausible registration page by appending /register to your domain name.

   https://plausible.example.com/register

   Replace plausible.example.com with the domain name that points to your server.

2. On the Register page, enter your full name, email address, and password. Click Create my account to set up the initial administrator account.

3. Enter the domain you want to track, choose your reporting time zone, and click Install Plausible to continue.

   

4. On the next screen, Plausible provides a JavaScript tracking snippet. Install this script in the <head> section of your website. Refer to the Installation guide for more information. Then click Verify Script installation to confirm that Plausible detects the script.

5. Refresh the page or open your Plausible dashboard in a new browser tab after the first page view appears to confirm that the setup is complete.

   

6. After verification, the Plausible dashboard opens and lists your website with traffic stats.

   

Conclusion

You deployed Plausible Analytics on a Linux server and configured it to run securely in Docker containers. You installed all required packages, set up the Plausible environment, and enabled HTTPS using Nginx and Certbot. For more information, refer to the official Plausible Analytics documentation.