Komga
A QuickBox Pro-backed Komga deployment for managing digital comics and manga.
Overview
Komga is a media server for your digital comics and manga. QuickBox Pro installs Komga per user, runs it as a systemd service, and exposes it through the QuickBox reverse proxy.
Key features
🧩 Per-user service
Runs as a user-scoped systemd unit (komga@username).
🗂️ User-scoped config + database
Stores configuration and data under /home/username/.config/Komga.
🌐 Reverse-proxy path
Default access path is /username/komga behind nginx.
🔒 SSL subdomain support
Optional Komga SSL setup via qb install lecert --komga builds a subdomain proxy.
When to use it
Use Komga when
- Host a dedicated media server for digital comics and manga.
- Run Komga per user with isolated configuration and data directories.
You want to
- Install Komga with
qb install komga -u username. - Access it through the QuickBox reverse proxy at
/username/komga.
Installation
Komga is installed per user:
qb install komga -u usernameIf you provide a domain, QuickBox will configure the Komga nginx reverse proxy during install:
qb install komga -u username -d 'komga.domain.com'Install options
-u, --usernameRequiredSet the username for Komga (required).
-d, --domainSet the domain for Komga (configures the nginx reverse proxy during install).
Access and authentication
Komga is served through the QuickBox nginx reverse proxy using the per-user path:
https://your-server/username/komgaThe reverse proxy points to the user’s Komga port (default is 8088).
SSL and subdomain setup
Dashboard SSL Control (Komga)
In the QuickBox dashboard, SSL Control includes a Komga row labeled “Stage SSL for Komga?” with a domain field and an optional username field. The tooltip explains that choosing Yes will configure the SSL certificate and establish the required nginx settings and links for secure access via your domain.
CLI SSL flow
You can also stage Komga SSL through the CLI:
qb install lecert --komga -d 'komga.domain.com' -u usernameWhen Komga SSL is staged, QuickBox copies the Komga subdomain nginx template, updates it with your domain and user port, sets the user-specific Komga URL override, and switches Komga’s servlet context path from /username/komga to / before restarting the service.
Configuration and files
Additional system locations used by QuickBox:
-
/opt/username/Komga/komga.jar /etc/nginx/software/username.komga.conf(path-based proxy)/etc/nginx/sites-enabled/username.komga.conf(subdomain proxy created by SSL staging)
Common tasks
# Start or restart Komga for a user
systemctl start komga@username
systemctl restart komga@username
# Stop Komga for a user
systemctl stop komga@usernameBest practices
Do
- Use
-dduring install when you want QuickBox to configure the Komga reverse proxy automatically. - Confirm your domain points to the server before staging SSL in the dashboard or with
qb install lecert --komga. - Provide the username when multiple users run Komga so the SSL setup targets the correct instance.
Don't
- Don’t stage Komga SSL without a domain; the
-dflag is required for certificate creation. - Don’t expect the Komga path to remain
/username/komgaafter SSL subdomain staging; the servlet context path is switched to/.
Troubleshooting
SSL staging changes the Komga path
When you stage Komga SSL, QuickBox updates Komga’s servlet context path to / and rebuilds the nginx subdomain config. Access Komga via the domain root (for example, https://komga.domain.com/ ), not the user path.
Username required for SSL subdomains
Komga SSL staging requires a username to resolve the correct user port. If multiple users run Komga, make sure to supply the username in SSL Control or via qb install lecert —komga.
Related Applications
Resources
QuickBox resources
Komga resources
Join the Community
Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.