AudioBookshelf on VPS: installation, configuration, and maintenance

AudioBookshelf on a VPS is the ideal solution for centralized storage and streaming of your audiobook, podcast, and comic book collection, providing full data control and accessibility from any device via a web interface or mobile apps.

In the era of digital media, audiobook libraries are becoming increasingly popular. But what if you want to have full control over your collection, not depend on third-party services, and access your files anytime, from any device? This is where AudioBookshelf comes in — a powerful, open-source, and self-hosted solution for managing audiobooks. Installing AudioBookshelf on a VPS (Virtual Private Server) gives you this freedom, combining the flexibility of cloud computing with the ease of use of specialized software. In this article, we will detail how to deploy AudioBookshelf on a server using Docker for maximum efficiency and ease of maintenance.

What is AudioBookshelf and why choose a VPS for hosting it?

AudioBookshelf is a modern open-source application designed specifically for managing and streaming audiobooks, podcasts, and even comic books. It provides a convenient web interface for organizing your library, supports numerous formats (MP3, M4A, M4B, FLAC, OPUS, OGG, AAC, and others), and also features for tracking listening progress, syncing between devices, and even a built-in player. For many users who value privacy and sovereignty over their data, AudioBookshelf self-hosted is the ideal choice.

Advantages of AudioBookshelf self-hosted

• Full data control: All your audiobooks are stored on your server, not on third-party cloud platforms.
• No subscriptions or ads: You only pay for the VPS, and the application itself is completely free.
• Customization: Ability to fine-tune settings, integrations, and appearance.
• Accessibility from anywhere: With proper configuration, you can access your library from any internet-connected device.
• Community and development: Active community of developers and users, constant updates and improvements.

Why is a VPS the optimal choice for AudioBookshelf?

While AudioBookshelf can be installed on a home server or Raspberry Pi, a VPS provides a number of significant advantages, especially for those seeking reliability, scalability, and professional infrastructure:

• Reliability and uptime: Hosting providers, such as Valebyte.com, guarantee a high level of server availability (uptime), which is critical for constant access to your media library.
• Stable bandwidth: VPS typically have high-speed internet connections, ensuring smooth streaming of audiobooks without delays, even for multiple users simultaneously.
• Dedicated resources: Unlike shared hosting, a VPS provides dedicated CPU, RAM, and disk space resources, eliminating the impact of "neighbors" on your AudioBookshelf's performance.
• Flexibility and scalability: You can easily increase or decrease VPS resources depending on your needs, whether it's collection growth or an increase in the number of users.
• Security: A VPS provides an isolated environment, which enhances security compared to a home server that may be vulnerable to attacks from the home network.
• Ease of management: Modern VPS providers offer convenient control panels, allowing easy server management, OS installation, and resource monitoring.

Choosing a VPS for AudioBookshelf is an investment in stability, performance, and your digital freedom. It allows you to create a personal, powerful, and always accessible media server without worrying about physical hardware and its maintenance. If you want to delve deeper into understanding the differences between various hosting types, we recommend checking out the article Containers vs. VMs vs. Bare-metal: The Hosting Landscape 2026.

AudioBookshelf System Requirements: Which VPS is suitable?

AudioBookshelf is relatively undemanding in terms of resources, especially if your library is not too large and the number of simultaneous users is limited. However, for comfortable operation and scalability, several factors should be considered.

Minimum Requirements for Getting Started

To run AudioBookshelf on a VPS in test mode or for a small personal library (up to 1000 audiobooks, 1-2 simultaneous users), the following minimum specifications will suffice:

• Operating System: Ubuntu 20.04+, Debian 11+, CentOS 7+, or any other Linux system with Docker support.
• Processor (CPU): 1 vCPU with a clock speed of 1.5-2.0 GHz or higher.
• Random Access Memory (RAM): 1 GB. This is sufficient for the Docker container itself and basic operations.
• Disk Space: 20-30 GB NVMe SSD. In addition to the OS and Docker, you'll need space for your audiobook collection. NVMe SSD significantly speeds up file access and application performance.
• Network Bandwidth: 100 Mbps.

On such configurations, AudioBookshelf will work, but with active use or adding a large number of media files, you may experience delays when scanning the library or with simultaneous access by multiple users.

Recommended Configurations for Real-World Workloads

For comfortable operation with a library of several thousand audiobooks, supporting 3-5 simultaneous users, and fast scanning of new files, it is recommended to choose a VPS with more powerful specifications. This will ensure smooth operation, responsive interface, and no buffering during streaming.

Recommended VPS configurations for AudioBookshelf:

Parameter	For a small library (1-2 users)	For a medium library (3-5 users)	For a large library (5+ users, many podcasts)
CPU	2 vCPU (2.5+ GHz)	2-4 vCPU (2.8+ GHz)	4+ vCPU (3.0+ GHz)
RAM	2 GB	4 GB	8+ GB
Disk (type)	50 GB NVMe SSD	100-200 GB NVMe SSD	200+ GB NVMe SSD (expandable)
Disk (volume)	Depends on collection	Depends on collection	Depends on collection
Network	1 Gbps	1 Gbps	1 Gbps
Approximate VPS price*	From $5-10/month	From $15-25/month	From $30-50+/month

*Prices are approximate and may vary depending on the provider and region. Valebyte.com offers various plans that meet these requirements.

Important note on disk space: The disk volume specified in the table includes the operating system and AudioBookshelf itself. The main space will be occupied by your audiobook collection. Keep in mind that 1 hour of audio typically takes 30 to 100 MB. Thus, a library of 1000 hours of audio can take 30 to 100 GB. Plan your disk volume with a margin, and consider using additional block storage if your collection will be very large.

To monitor your VPS resource usage and optimize AudioBookshelf performance, you can install tools such as Netdata on VPS. This will allow you to track CPU, RAM, disk, and network load in real-time.

Preparing Your VPS for AudioBookshelf Installation via Docker

For the simplest and most reliable AudioBookshelf installation, we will use Docker and Docker Compose. This will allow us to isolate the application from the rest of the system, simplify its updates, and manage dependencies.

System Update and Docker/Docker Compose Installation

Before installing anything, it's always recommended to update your operating system. Connect to your VPS via SSH:

ssh user@your_vps_ip

Then execute the commands to update packages:

sudo apt update
sudo apt upgrade -y

Now let's install Docker. These commands are suitable for most Debian/Ubuntu-like systems:

# Install necessary packages
sudo apt install ca-certificates curl gnupg lsb-release -y

# Add Docker's official GPG key
sudo mkdir -p /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg

# Add Docker repository
echo \
  "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \
  $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

# Update package index and install Docker Engine
sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin -y

Verify that Docker is installed and running:

sudo docker run hello-world

If you see the message "Hello from Docker!", the installation was successful. To avoid constantly using sudo with Docker commands, add your user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Exit your SSH session and reconnect for the changes to take effect. Now you will be able to execute Docker commands without sudo.

Creating a User and Configuring File Structure

For better security and organization, it is recommended to run AudioBookshelf as a separate user and store its data in a dedicated directory. This also simplifies the backup process.

Let's create a directory for AudioBookshelf and its data:

mkdir -p ~/audiobookshelf/config
mkdir -p ~/audiobookshelf/audiobooks

• ~/audiobookshelf/config: This is where AudioBookshelf's configuration files will be stored.
• ~/audiobookshelf/audiobooks: This is where you will store your audiobooks.

You can choose any other location, but make sure that the user under which you run the Docker container has read and write permissions to these directories. In our case, since we are using the current user, permissions will be inherited.

For best practice, especially if you have multiple services on one VPS, you can create a separate user for AudioBookshelf, but for most personal installations, this is not a strict requirement.

Step-by-Step AudioBookshelf Installation on VPS with Docker Compose

Now that Docker and the necessary directories are ready, we can proceed with deploying AudioBookshelf using Docker Compose. This will allow us to define all container parameters in a single file and manage it easily.

Creating the docker-compose.yml file

Navigate to the directory we created for AudioBookshelf and create the file docker-compose.yml:

cd ~/audiobookshelf
nano docker-compose.yml

Paste the following content into the file. Don't forget to change TZ to your timezone (e.g., Europe/Moscow) and PUID/PGID to your user and group IDs (usually 1000, but you can check with the id command).

version: "3.8"
services:
  audiobookshelf:
    image: ghcr.io/advplyr/audiobookshelf:latest
    container_name: audiobookshelf
    restart: unless-stopped
    environment:
      - PUID=1000 # Your user ID
      - PGID=1000 # Your group ID
      - TZ=Europe/Moscow # Your timezone
      - AUDIOBOOKSHELF_PORT=80 # Port on which AudioBookshelf will run inside the container
    volumes:
      - ./config:/config # Path to configuration files
      - ./audiobooks:/audiobooks # Path to your audiobook library
      # - ./podcasts:/podcasts # Uncomment if you want to store podcasts separately
      # - ./metadata:/metadata # Uncomment if you want to store metadata separately
    ports:
      - 1337:80 # Host port:container port. 1337 can be changed to any free port.
    networks:
      - abs_network

networks:
  abs_network:
    driver: bridge

Explanations for the docker-compose.yml file:

• image: ghcr.io/advplyr/audiobookshelf:latest: Specifies the use of the latest stable version of the AudioBookshelf image from GitHub Container Registry.
• container_name: audiobookshelf: Assigns an easily recognizable name to the container.
• restart: unless-stopped: Ensures that the container will automatically restart after failures or VPS reboots.
• environment:
  • PUID and PGID: Define the user and group IDs under which the AudioBookshelf process will run inside the container. This is important for correct access permissions to mounted volumes (your audiobook files). You can find your IDs by running the id command in the terminal.
  • TZ: Sets the timezone for correct time display.
  • AUDIOBOOKSHELF_PORT: The port on which AudioBookshelf listens inside the container. Default is 80.
• volumes: Defines which directories from the host system will be mounted inside the container.
  • ./config:/config: Mounts your local directory ~/audiobookshelf/config to /config inside the container. This is where AudioBookshelf's database, settings, and cache are stored.
  • ./audiobooks:/audiobooks: Mounts your local directory ~/audiobookshelf/audiobooks to /audiobooks inside the container. This is where you will upload your audiobooks.
• ports: - 1337:80: Forwards port 80 from the container to port 1337 of your VPS. This means you will access AudioBookshelf via port 1337 on your server (e.g., http://your_vps_ip:1337). You can change 1337 to any other free port.
• networks: Defines the internal Docker network for the container. This is useful if you plan to add other services (e.g., a reverse proxy) to the same network.

Save the file (Ctrl+O, Enter, Ctrl+X).

Starting AudioBookshelf

Now that the docker-compose.yml file is created, you can start AudioBookshelf with a single command:

docker compose up -d

• docker compose up: Starts all services defined in docker-compose.yml.
• -d: Runs containers in the background (detached mode).

Docker will download the image (if not available locally), create the container, and start AudioBookshelf. You can check the container status:

docker ps

You should see the audiobookshelf container with status Up.

Now you can access the AudioBookshelf web interface by opening http://your_vps_ip:1337 in your browser (replace your_vps_ip with your VPS's actual IP address and 1337 with the port you specified).

Initial Setup and Adding Your Media Library

Upon first accessing AudioBookshelf, you will be prompted to create an administrator account. Choose a strong username and password. After logging in, you will see an empty library.

To add your audiobooks:

1. Upload files to the VPS: Use SFTP (e.g., via FileZilla) or SCP to copy your audiobooks to the ~/audiobookshelf/audiobooks directory on your VPS. Ensure files have correct permissions (usually 644 for files and 755 for directories).
2. Add the library in AudioBookshelf:
   • In the AudioBookshelf web interface, go to Settings -> Libraries.
   • Click Add Library.
   • Select the library type (e.g., "Audiobooks").
   • In the "Library Path" field, enter /audiobooks (this is the path inside the Docker container where we mounted your local audiobook directory).
   • Configure other settings as desired (e.g., metadata language, folder scanning).
   • Click "Save". AudioBookshelf will start scanning the added directory and importing your audiobooks.

The scanning process may take some time depending on the size of your collection. Once scanning is complete, you will see your audiobooks in the main interface.

Setting Up a Reverse Proxy and HTTPS for AudioBookshelf

Accessing AudioBookshelf via an IP address and a non-standard port is not very convenient and, more importantly, insecure. For production use, it is highly recommended to set up a reverse proxy with HTTPS to access AudioBookshelf via a domain name (e.g., audio.yourdomain.com) with an encrypted connection.

We will cover two popular options: Nginx and Caddy.

Before you begin:

1. You must have a domain name (e.g., yourdomain.com).
2. Create a DNS A-record pointing to your VPS's IP address (e.g., audio.yourdomain.com -> your_vps_ip).
3. Ensure that ports 80 and 443 are open on your VPS (if you are using a firewall, e.g., UFW: sudo ufw allow 80/tcp, sudo ufw allow 443/tcp).

To configure the reverse proxy, we will modify the docker-compose.yml file for AudioBookshelf so that it does not forward the port directly to the host, but instead uses the internal Docker network. Open ~/audiobookshelf/docker-compose.yml and comment out or remove the line ports: - 1337:80:

version: "3.8"
services:
  audiobookshelf:
    image: ghcr.io/advplyr/audiobookshelf:latest
    container_name: audiobookshelf
    restart: unless-stopped
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Moscow
      - AUDIOBOOKSHELF_PORT=80
    volumes:
      - ./config:/config
      - ./audiobooks:/audiobooks
    # ports: # Comment out or remove this line
    #   - 1337:80 # And this line
    networks:
      - abs_network

networks:
  abs_network:
    driver: bridge

Update the AudioBookshelf container:

cd ~/audiobookshelf
docker compose down
docker compose up -d

Now AudioBookshelf is only accessible within the Docker network by its container name (audiobookshelf) on port 80.

Nginx as a Reverse Proxy

Nginx is a powerful and widely used web server and reverse proxy. If you already have Nginx installed, skip the first steps.

Nginx Installation:

sudo apt install nginx -y

Creating Nginx Configuration:

Create a new configuration file for your domain:

sudo nano /etc/nginx/sites-available/audiobookshelf.conf

Paste the following content, replacing audio.yourdomain.com with your domain:

server {
    listen 80;
    server_name audio.yourdomain.com;

    location / {
        proxy_pass http://localhost:1337; # Use the port on which AudioBookshelf is locally available
        # Or, if you commented out ports in docker-compose.yml and are using the internal Docker network:
        # proxy_pass http://audiobookshelf:80; # Container name and its internal port
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

        # WebSocket support for AudioBookshelf (important for real-time updates)
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

If you removed port forwarding from docker-compose.yml, then proxy_pass should point to the container name in the Docker network: http://audiobookshelf:80;. If you kept port forwarding to 1337, then use http://localhost:1337;.

Create a symbolic link to sites-enabled and test the configuration:

sudo ln -s /etc/nginx/sites-available/audiobookshelf.conf /etc/nginx/sites-enabled/
sudo nginx -t

If there are no errors, restart Nginx:

sudo systemctl restart nginx

Now you can access AudioBookshelf via http://audio.yourdomain.com. But we need HTTPS.

Installing Certbot for HTTPS (Let's Encrypt):

sudo snap install core
sudo snap refresh core
sudo snap install --classic certbot
sudo ln -s /snap/bin/certbot /usr/bin/certbot

Obtain an SSL certificate and configure Nginx automatically:

sudo certbot --nginx -d audio.yourdomain.com

Follow Certbot's instructions. It will automatically modify your Nginx configuration, add HTTPS, and set up HTTP to HTTPS redirection. After this, your AudioBookshelf will be accessible at https://audio.yourdomain.com.

Caddy as a Reverse Proxy (alternative)

Caddy is a modern web server that automatically manages Let's Encrypt SSL certificates, making its setup much simpler than Nginx.

Caddy Installation:

sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
sudo apt update
sudo apt install caddy -y

Creating Caddyfile Configuration:

Create the file Caddyfile:

sudo nano /etc/caddy/Caddyfile

Remove existing content and paste the following, replacing audio.yourdomain.com with your domain:

audio.yourdomain.com {
    reverse_proxy audiobookshelf:80 # Container name and its internal port
    # If you kept port forwarding to 1337:
    # reverse_proxy localhost:1337
}

Save the file.

Testing and Starting Caddy:

sudo caddy validate --config /etc/caddy/Caddyfile
sudo systemctl restart caddy

Caddy will automatically obtain an SSL certificate and configure HTTPS. Your AudioBookshelf will be accessible at https://audio.yourdomain.com.

The choice between Nginx and Caddy depends on your preferences and experience. Nginx is more flexible for complex configurations, while Caddy excels in the simplicity of HTTPS setup.

AudioBookshelf Maintenance: Backups and Updates

Regular maintenance, including backups and updates, is critically important for the reliable and secure operation of your AudioBookshelf on a VPS.

AudioBookshelf Data Backup Strategies

Losing your audiobook collection data or AudioBookshelf settings can be very frustrating. Regular backups will help avoid this problem. What needs to be backed up?

1. AudioBookshelf configuration files: The directory ~/audiobookshelf/config (or the path you specified in docker-compose.yml). This is where the database, user settings, metadata, and cache are stored.
2. The audiobooks themselves: The directory ~/audiobookshelf/audiobooks. This is the largest part.

Backup Recommendations:

• Frequency: Configuration files should be backed up daily or weekly, depending on how often you make changes or add new books. Audiobooks can be backed up less frequently if you rarely add to your collection.
• Storage Location: Never store backups on the same VPS as the primary data. Use remote storage:
  • Cloud services (S3-compatible storage, Google Drive, Dropbox).
  • Another VPS or dedicated server.
  • Local computer (for small collections).
• Automation: Use scripts and cron jobs to automate the process.

Example script for configuration backup (with cloud upload):

Create the file backup_audiobookshelf.sh:

#!/bin/bash

# Paths
CONFIG_DIR="/home/$USER/audiobookshelf/config"
BACKUP_DIR="/tmp/audiobookshelf_backup"
DATE=$(date +%Y%m%d%H%M%S)
BACKUP_FILE="$BACKUP_DIR/audiobookshelf_config_$DATE.tar.gz"

# Create temporary directory for backup
mkdir -p "$BACKUP_DIR"

echo "Stopping AudioBookshelf for a consistent backup..."
cd /home/$USER/audiobookshelf
docker compose stop audiobookshelf

echo "Creating configuration archive..."
tar -czf "$BACKUP_FILE" -C "$CONFIG_DIR" .

echo "Starting AudioBookshelf..."
docker compose start audiobookshelf

echo "Configuration backup created: $BACKUP_FILE"

# Example of sending to S3-compatible storage using rclone
# Make sure rclone is installed and configured: rclone config
# rclone copy "$BACKUP_FILE" "my_s3_remote:audiobookshelf-backups/"

# Deleting temporary files
rm "$BACKUP_FILE"
rmdir "$BACKUP_DIR"

echo "Backup completed."

Make the script executable: chmod +x backup_audiobookshelf.sh.

Add it to cron for daily execution (e.g., at 3 AM):

crontab -e

Add the line:

0 3 * * * /home/$USER/backup_audiobookshelf.sh >> /var/log/audiobookshelf_backup.log 2>&1

For backing up the audiobooks themselves, if their volume is large, it's better to use incremental backups with rsync or specialized tools for cloud storage. You might find the article What is a VPS in 2026: Buyer's Guide vs. Cloud and Dedicated useful for choosing suitable storage.

AudioBookshelf and Docker Container Update Process

Updating AudioBookshelf running in Docker is very simple. It is recommended to regularly update both AudioBookshelf itself and the base Docker images to receive new features, bug fixes, and security improvements.

Updating AudioBookshelf:

Navigate to the directory containing your docker-compose.yml:

cd ~/audiobookshelf

Execute the following commands:

docker compose pull audiobookshelf # Download the latest image version
docker compose up -d             # Recreate the container with the new image, preserving data

docker compose pull will download a new version of the image if available. docker compose up -d will stop the old container, remove it, and create a new one based on the fresh image, while all your data (which is in the mounted volumes) will remain untouched.

Updating Docker Engine and System:

Periodically, you should also update Docker itself and your VPS's operating system:

sudo apt update
sudo apt upgrade -y

After updating the kernel or important system components, a VPS reboot may be required: sudo reboot.

Important note: Before any major updates, always back up your AudioBookshelf configuration. Although Docker Compose is designed for safe updates, it's better to be safe than sorry.

Choosing the Optimal VPS for AudioBookshelf: Valebyte.com Recommendations

Choosing the right VPS for AudioBookshelf depends on the size of your collection, the number of users, and your performance expectations. Valebyte.com offers various plans that can meet any needs.

Factors Influencing VPS Choice

1. Library Size: The more audiobooks, the more disk space you will need. For very large collections, consider a VPS with expandable disk capacity or block storage.
2. Number of Concurrent Users: Each active user, especially during streaming, consumes CPU and RAM resources. For 5+ users, a more powerful processor and more RAM will be required.
3. Disk Type: NVMe SSD significantly outperforms regular SSDs and HDDs in read/write speeds, which is critical for fast library scanning and interface responsiveness. Valebyte.com offers VPS with NVMe SSD.
4. Network Bandwidth: Important for smooth streaming. 1 Gbps is the standard that provides excellent performance.
5. Server Location: Choose a data center that is closer to your primary users to minimize latency.
6. Budget: Determine how much you are willing to spend monthly. Valebyte.com offers competitive prices for high-performance VPS.

Recommended Valebyte.com Plans

Based on system requirements and selection factors, we recommend the following VPS configurations from Valebyte.com for AudioBookshelf:

Valebyte.com Plan	CPU	RAM	NVMe SSD	Network	Use Case for AudioBookshelf	Approx. Price/month
Valebyte Start	2 vCPU	2 GB	50 GB	1 Gbps	Personal library (up to 1000 books), 1-2 users, testing.	from $7
Valebyte Basic	4 vCPU	4 GB	100 GB	1 Gbps	Medium family library (up to 5000 books), 3-5 users, active use.	from $15
Valebyte Pro	6 vCPU	8 GB	200 GB	1 Gbps	Large library (10000+ books), 5+ active users, podcasts, comic books.	from $30
Valebyte Max	8+ vCPU	16+ GB	400+ GB	1 Gbps	Very large collections, high load, many simultaneous streams.	from $50

For very large collections that may exceed the capacity of the primary NVMe SSD, consider using additional block storage, which can be easily connected to your VPS. This will allow you to scale disk space independently of other resources.

If you are new to server management and want more information about VPS, check out our article What are Servers and Dedicated Servers: A Complete Guide for Beginners. Also, for those looking for a balance between control and simplicity, the article Self-managed vs. Managed VPS in 2026: What to Choose will be of interest.

Conclusion

AudioBookshelf on a VPS is a powerful and flexible solution for creating your own media library of audiobooks, podcasts, and comic books. Using Docker and Docker Compose significantly simplifies installation, configuration, and maintenance, and a reliable VPS from Valebyte.com ensures stable operation and high performance.

By choosing a suitable Valebyte.com plan and following our installation and maintenance recommendations, you will gain full control over your media file collection, accessible from any device at any time.