Skip to Content
ApplicationsMedia ManagementSickChill

Overview

SickChill is an automatic TV library manager. In QuickBox, SickChill is installed per user under /opt/username/SickChill, runs as the systemd unit sickchill@username, and stores its configuration in /home/username/.config/SickChill/config.ini.

Key features

The highlights below are drawn from QuickBox’s installer, service unit, and nginx proxy configuration.

Per-user install + service

QuickBox installs SickChill in /opt/username/SickChill and runs it as sickchill@username.

Proxied web route

The nginx proxy exposes SickChill at /username/sickchill and the API at /username/sickchill/api.

Basic auth for UI

The main UI route is protected with nginx basic auth; the API route disables basic auth.

Config in the user profile

QuickBox writes web_root, web_host, and web_port in /home/username/.config/SickChill/config.ini.

When to use it

Use SickChill when you want a TV-focused manager that QuickBox runs as a dedicated per-user service.

Good fit if

  • You want an automated TV library manager that watches for new episodes.
  • You prefer a per-user install with its own config directory under /home/username/.config/SickChill.

QuickBox approach

  • Install SickChill for the user and manage it as the sickchill@username systemd service.
  • Access it through the nginx proxy at /username/sickchill.

Installation

Install from the Dashboard

Open App Dashboard → Package Management (/dashboard?mode=packages), find SickChill in the catalog (browse Media Management or search), and click Install. The dashboard streams the install log live and SickChill appears in your Application Control panel when it finishes. Reinstall and Remove are in the same Package Management panel. To update, use the amber Update badge on the SickChill row in the App Dashboard.

What you see and can manage is gated by your account: admins manage any user’s apps; regular users manage their own. See App Management for the full flow.

Install from the CLI (automation)

The CLI runs the same install and is suited to automation and scripting:

bash
qb install sickchill -u username
qb reinstall sickchill -u username
qb update sickchill -u username
qb remove sickchill -u username

Full flag reference: CLI Reference.

Access and authentication

SickChill is proxied through nginx and protected by basic auth on the main UI route.

URL / route

The proxy route is /username/sickchill, and the API route is /username/sickchill/api.

Credentials / tokens

The UI route uses nginx basic auth with /etc/htpasswd.d/htpasswd.username. SickChill’s API key is stored in /home/username/.config/SickChill/config.ini and is surfaced in the QuickBox dashboard service controls.

Security notes

The /username/sickchill/api route explicitly disables nginx basic auth, so API access relies on the SickChill API key.

Ports and networking

QuickBox sets a base port and auto-generates an available port if auto-generation is enabled.

  • Base/default port: 8081.
  • Assigned port: QuickBox randomizes within a range around the base port and retries until a free port is found when auto-generation is enabled.
  • Where to confirm the live port: the QuickBox dashboard service control card lists the SickChill port field for the user.

Configuration and files

Key locations that QuickBox creates or manages for SickChill are listed below.

Path
Description
/
opt/
username/
SickChill/
Application files
lib/
python/
SickChill/
.venv/
Python virtual environment for SickChill
home/
username/
.config/
SickChill/
config.ini
web_root, web_host, web_port, API key
etc/
nginx/
software/
username.sickchill.conf
nginx proxy for /username/sickchill
systemd/
system/
sickchill@.service
Systemd unit for per-user SickChill
htpasswd.d/
htpasswd.username
Basic auth file for /username/sickchill

Common tasks

Use the dashboard service controls to manage SickChill for a user.

  • Start: Start action for SickChill in the service control widget.
  • Stop: Stop action for SickChill in the service control widget.
  • Refresh: Refresh action for SickChill in the service control widget.

Best practices

These practices align with the QuickBox installer and service layout for SickChill.

Do

  • Use the nginx route /username/sickchill instead of connecting directly to the loopback port.
  • Keep the SickChill config in /home/username/.config/SickChill/config.ini and let QuickBox manage permissions.

Don't

  • Do not remove /etc/systemd/system/sickchill@.service while SickChill is installed for any user.
  • Do not edit /etc/nginx/software/username.sickchill.conf without reloading nginx after changes.

Troubleshooting

If something does not work as expected, use the checks below before reinstalling.

Login prompt or 401 errors
Warning

The UI route /username/sickchill is protected by nginx basic auth. Verify the user entry in /etc/htpasswd.d/htpasswd.username and confirm nginx is proxying to the expected port.

API calls fail
Info

The API route /username/sickchill/api disables nginx basic auth. Confirm the API key in /home/username/.config/SickChill/config.ini and compare it with the key shown in the dashboard service controls.

Service will not start
Caution

The systemd unit runs SickChill from /opt/username/lib/python/SickChill/.venv/bin/SickChill and uses /home/username/.config/SickChill as its data directory. Ensure both paths exist for the user.

Resources

Use these references for upstream project details and release source.

SickChill project

SickChill on GitHub

Upstream project referenced by QuickBox releases

Join the Community

Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.

  • Dedicated Support
  • Feature Previews
  • Community Configs
  • Active Discussions
Join Discord Server
Last updated on
ReadarrSickGear