Skip to Content
Sonarr

Sonarr

Smart PVR for automated TV series management and quality upgrades

Sonarr is a PVR (Personal Video Recorder) for Usenet and BitTorrent users. It monitors multiple RSS feeds for new episodes of your favorite shows and automatically grabs, sorts, and renames them. Sonarr can also be configured to automatically upgrade the quality of files already downloaded when a better quality format becomes available.

Automatic Series Monitoring

Track your favorite TV shows and automatically download new episodes as they become available

Quality Management

Define preferred quality profiles and automatically upgrade existing episodes to better quality versions

Calendar Integration

Visual calendar showing upcoming and aired episodes with at-a-glance schedule overview

TheTVDB Integration

Search and add new series from TheTVDB with comprehensive metadata and episode information

Automatic Organization

Rename and organize files with customizable naming patterns for consistent library structure

Download Client Support

Works with qBittorrent, Deluge, SABnzbd, NZBGet, rTorrent, and Transmission

Notification System

Get notified when episodes are grabbed, downloaded, or upgraded via Discord, Slack, Email, and more

Custom Scripts

Run custom scripts on grab, download, rename, or import events for advanced automation


Installation

Install from the Dashboard

Open App Dashboard → Package Management (/dashboard?mode=packages), find Sonarr in the catalog (browse Media Management or search), and click Install. The dashboard streams the install log live and Sonarr 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 Sonarr row in the App Dashboard.

In the install dialog you can pick the release channel — Stable (default) or Nightly. Stable follows Sonarr’s main branch, which carries Sonarr 4. Nightly follows the develop branch, which carries Sonarr 5. Switching the channel later and updating moves Sonarr to that channel’s latest build; the steps are in Move to Sonarr 5. See Channels & Versions for how channels work.

For a dedicated 4K library, install Sonarr4K — a separate instance with its own port, configuration directory (~/.config/Sonarr4K), and quality profiles, so your standard and 4K libraries never conflict. It appears as its own catalog entry in Package Management; on the CLI it is the --4k flag on qb install sonarr (see below).

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

Install and manage from the CLI

The CLI runs the same scripts as the Dashboard and is the full power-user/automation surface. Install Sonarr on the stable channel for a specific user:

bash
qb install sonarr -u username

The complete command set:

CommandDescription
qb install sonarr -u username
Install Sonarr on the stable channel (main branch, Sonarr 4) with automatic configuration
qb install sonarr -u username --nightly
Install on the nightly channel (develop branch), which carries Sonarr 5
qb install sonarr -u username --4k
Install a separate 4K instance (Sonarr4K) for high-resolution content
qb install sonarr -u username --nightly --4k
Install the 4K instance on the nightly branch
qb reinstall sonarr -u username
Remove and install Sonarr fresh (deletes its config folder and backups, so take a Full Backup first)
qb update sonarr -u username
Update on the channel Sonarr is set to (read from config.xml); never installs a lower major than the one you run
qb update sonarr -u username --nightly
Switch to the nightly channel and update: a Sonarr 4 install moves to Sonarr 5 (see Move to Sonarr 5)
qb remove sonarr -u username
Remove the standard installation
qb remove sonarr -u username --4k
Remove the 4K instance
qb help sonarr
Display comprehensive help information
OptionDescriptionExample
-u, --usernameRequired

Specify the user for installation

-u john
-u john
--nightly

Use the develop branch (nightly channel, Sonarr 5). On install it installs from develop. On update it switches the install to develop, so a Sonarr 4 install moves to Sonarr 5

--4k

Install a dedicated 4K instance (Sonarr4K) with its own config and port

--v4

Retired v3 to v4 flag. Do not use it: it is ignored, or the update stops with the error and changes nothing

How the 4K instance works
Note

--4k is a flag on the base Sonarr package — it installs a dedicated Sonarr4K instance with its own port, install directory (/opt/username/Sonarr4K), configuration (~/.config/Sonarr4K), and quality profiles, so your standard and 4K libraries never conflict. There is no separate sonarr4k install command — you pass --4k to qb install sonarr. In the Dashboard, Sonarr4K appears as its own catalog entry you can install the same way.

Update branch handling
Tip

When you run qb update sonarr -u username, QuickBox reads your current branch (main or develop) from config.xml and updates on it. You don’t need --nightly unless you want to switch to the nightly channel, and there is no CLI flag that switches back to stable: use the dashboard channel control, covered in Move to Sonarr 5.

Full flag reference: CLI Reference.


Directory Structure

Path
Description
/home/username
.config/
Sonarr/
Sonarr configuration directory
sonarr.db
Main database, saved by Full Backup
config.xml
Core configuration (ports, URL base, branch)
logs/
Application logs
Sonarr4K/
4K instance configuration (if --4k flag used)
sonarr.db
4K instance database
config.xml
4K instance configuration
.QuickBox/
software/
sonarr/
Backups folder (sonarr4k for the 4K instance); deleted by remove and reinstall
backup/
Config Only, Full Backup and Nginx files
Media/
Recommended media storage location
TV/
TV shows root folder
TV-4K/
4K TV shows (if using --4k)

Configuration Details

Standard instance:

  • Install location: /opt/username/Sonarr/
  • Config directory: ~/.config/Sonarr/
  • Database: ~/.config/Sonarr/sonarr.db
  • Service: sonarr@username.service
  • Default port: 8989 (auto-generated if in use)
  • SSL port: 9898 (auto-generated if in use)

4K instance (—4k flag):

  • Install location: /opt/username/Sonarr4K/
  • Config directory: ~/.config/Sonarr4K/
  • Database: ~/.config/Sonarr4K/sonarr.db
  • Service: sonarr4k@username.service
  • Ports: Auto-generated (typically 8990+)

Move to Sonarr 5

Sonarr 5 is published on Sonarr’s develop branch, which QuickBox calls the Nightly channel. The stable channel (main) stays on Sonarr 4. To move a Sonarr 4 install to Sonarr 5, switch it to Nightly and update once.

Take a Full Backup first
Warning

Sonarr 5 is a new major version, and an update will not move an install back to Sonarr 4 afterwards (see Going back to stable). A Full Backup saves the install tree and a consistent copy of sonarr.db, and a Rollback puts both back. See Back up and restore.

From the dashboard

The channel control is available to admins.

  1. Open the App Dashboard and stay on Application Control.
  2. On the Sonarr row, find the version number. Click the small branch icon beside it (its tooltip reads Change release channel).
  3. In the Sonarr — Channel Settings dialog, choose Nightly.
  4. Click Save Channel. Saving writes the channel into Sonarr’s config.xml.
  5. Run the update: click the amber Update badge when it appears on the Sonarr row (that dialog also has a channel picker and a Switch & Update Now button), or run the CLI command below.

The same control moves Sonarr4K: use the Sonarr4K row.

From the CLI

bash
qb update sonarr -u username --nightly

This switches the install to the develop branch and updates it in one step, so a Sonarr 4 install lands on Sonarr 5. For Sonarr4K add --4k. After the switch, a plain qb update sonarr -u username keeps updating on develop.

What QuickBox does after the move

  • QuickBox follows the major you run. An install on Sonarr 5 is checked for and updated with Sonarr 5 releases. An install on Sonarr 4 stays on 4 until you choose Nightly.
  • Sonarr can update itself. If you update from inside Sonarr, QuickBox keeps following the version you are on and never offers an older one.
  • A new install on Nightly gets Sonarr 5 directly. qb install sonarr -u username --nightly installs from develop.

Going back to stable

An update never installs a lower major than the one you run. If you set the channel back to Stable (on Nightly, click the amber channel badge in the Version column instead of the branch icon) and update a Sonarr 5 install, the update stops, changes nothing and reports that the newest release on the main branch is older than the version you run. Sonarr keeps running on Sonarr 5. To stay on Sonarr 5, set the channel back to Nightly. A reinstall without --nightly starts fresh on Stable (Sonarr 4) and deletes the config folder, so add --nightly to reinstall on Nightly. To get back to Sonarr 4, roll back to a Full Backup taken before the move (it holds the install tree and the config folder, see Back up and restore). If the Version column still shows Nightly after the rollback, set the channel back to Stable with Save Channel.

Sign in after the move

Sonarr 5 makes its own login
Warning

A QuickBox update never sets or changes an app login. When Sonarr 5 starts without a login user, it creates one itself: the user sonarr with a random password that it writes only to its log. Look for the line containing created 'sonarr' with the password in /home/username/.config/Sonarr/logs/sonarr.txt (Sonarr4K: the logs folder under /home/username/.config/Sonarr4K/).

Sign in with that user and password, then choose your own. Run qb user apppasswd -s sonarr -u username -o set to set a password: it replaces the generated sonarr login with your QuickBox username. You can also change it inside Sonarr under Settings → General → Security. We recommend keeping Sonarr’s own login on, with Authentication Method set to Forms and Authentication Required set to Enabled. An install that already had its own login keeps it through the update.


Legacy: Sonarr v3 to v4 (archived)


Accessing Sonarr

After installation, Sonarr is accessible through QuickBox’s nginx reverse proxy with SSL:

Instance TypeAccess URL
Standardhttps://your-server-ip/username/sonarr
4K Instancehttps://your-server-ip/username/sonarr4k
QuickBox Dashboard Integration
Tip

Sonarr is automatically integrated into your QuickBox dashboard. Find it on the App Dashboard (the default control view), stay on Application Control and expand its row for port and status. The API & Secrets section shows the Sonarr API key masked, with buttons to reveal it and copy it. Click Open to launch the web interface.

To install, reinstall, and remove applications, use the Package Management tab instead.

Network Configuration

QuickBox automatically configures:

  • URL Base: /username/sonarr (or /username/sonarr4k)
  • Bind Address: 127.0.0.1 (local only - proxied through nginx)
  • Port: Auto-assigned (typically 8989 for standard, 8990+ for 4K)
  • SSL: Handled by nginx reverse proxy (port 443)
  • Authentication: Forms login with your QuickBox username and password, set by install and reinstall

Initial Configuration

1. Check the Sonarr login

An install or reinstall turns Sonarr’s own login on for you: Forms authentication with Authentication Required enabled, using your QuickBox username and password (or the password you set with qb user apppasswd -s sonarr -u username -o set). An update never changes it. If Sonarr is accessible from the internet, keep that login on.

To change it, go to Settings → General → Security inside Sonarr. Keep Authentication Method on Forms and Authentication Required on Enabled, and use a strong password. After a move to Sonarr 5, see Sign in after the move.

2. Configure Download Client

Sonarr needs a download client to grab releases. QuickBox configures clients with SSL through nginx.

Steps:

  1. Go to Settings → Download Clients
  2. Click Add (+) button
  3. Select your client (qBittorrent, Deluge, rTorrent, etc.)
  4. Enable Show Advanced to access URL Base field
  5. Enter connection details from the table below

Download Client Configuration

QuickBox-specific connection details for common download clients

All configurations use SSL (port 443) through nginx reverse proxy

Deluge

HTTPS
Hostlocalhost or server IP
Port443
URL Base/username/deluge
AuthPassword (from Deluge connection manager)

Flood

HTTPS
Hostlocalhost or server IP
Port443
URL Base/username/flood
AuthUsername & Password (Flood credentials)

NZBGet

HTTPS
Hostlocalhost or server IP
Port443
URL Base/username/nzbget
AuthUsername & Password (NZBGet credentials)

qBittorrent

HTTPS
Hostlocalhost or server IP
Port443
URL Base/qbittorrent
AuthUsername & Password (qBittorrent credentials)

rTorrent

HTTPS
Hostlocalhost or server IP
Port443
URL Path/username (SCGI routed by QuickBox)
AuthUsername & Password (ruTorrent credentials)

SABnzbd

HTTPS
Hostlocalhost or server IP
Port443
URL Base/username/sabnzbd
AuthAPI Key (from SABnzbd settings) and Username & Password (SABnzbd credentials)

Transmission

HTTPS
Hostlocalhost or server IP
Port443
URL Base/username/transmission
AuthUsername & Password (Transmission credentials)
  1. Click Test to verify connection
  2. Click Save if test succeeds
Download Client Categories
Tip

Configure categories in your download client (e.g., tv-sonarr) to isolate Sonarr downloads and set specific paths automatically.

Prowlarr provides centralized indexer management across all *arr applications:

  1. Install Prowlarr: qb install prowlarr -u username
  2. In Prowlarr, navigate to Settings → Apps
  3. Click Add (+) and select Sonarr
  4. Enter:
    • Sonarr URL: http://localhost:8989/username/sonarr
    • API Key: Copy it from Sonarr’s row on the App Dashboard (API & Secrets section), or find it in Sonarr → Settings → General → Security
  5. Click Test then Save
  6. Add indexers in Prowlarr—they automatically sync to Sonarr
Why Prowlarr over Jackett?
Tip

Prowlarr is the modern successor to Jackett. When you add or remove indexers in Prowlarr, they automatically sync to Sonarr, Radarr, Lidarr, and other *arr apps. This centralized management saves time and ensures consistency.

Alternative: Manual indexers

  • Go to Settings → Indexers → Add (+)
  • Add trackers/usenet indexers individually

4. Set Root Folder

Define where Sonarr should store TV shows:

  1. Navigate to Settings → Media Management
  2. Click Root Folders
  3. Click Add Root Folder
  4. Enter path (e.g., /home/username/Media/TV)
  5. Click OK

Recommended structure:

  • Standard instance: /home/username/Media/TV
  • 4K instance: /home/username/Media/TV-4K

5. Quality Profiles & Upgrades

Configure quality preferences and automatic upgrades:

  1. Navigate to Settings → Profiles
  2. Edit existing profile or create new one
  3. Configure:
    • Upgrade Until: Maximum quality (e.g., Bluray-1080p)
    • Upgrades Allowed: ✓ Enabled
    • Cutoff: When to stop upgrading
  4. Click Save

Example workflow:

  • Episode airs → Download HDTV 720p
  • Web release available → Upgrade to WEBDL 1080p
  • Blu-ray released → Upgrade to Bluray 1080p (cutoff reached, stop upgrading)
Smart Upgrading Strategy
Tip

Set upgrade cutoffs to prevent endless upgrading. For example, setting cutoff to Bluray-1080p prevents automatic upgrades to massive 4K remuxes unless you specifically want them. This saves bandwidth and storage space.


File Naming Configuration

Recommended settings for consistent library organization:

Navigate to Settings → Media Management → File Management:

SettingRecommended Configuration
Rename Episodes✓ Enabled - Ensures consistent naming across your library
Replace Illegal Characters✓ Enabled - Removes filesystem-incompatible characters
Standard Episode Format{Series Title} - S{season:00}E{episode:00} - {Episode Title} {Quality Full}
Daily Episode Format{Series Title} - {Air-Date} - {Episode Title} {Quality Full}
Anime Episode Format{Series Title} - S{season:00}E{episode:00} - {absolute:000} - {Episode Title} {Quality Full}
Series Folder Format{Series Title} ({Series Year})

Example output:

  • Standard: The Office - S02E05 - Halloween WEBDL-1080p.mkv
  • Daily: The Daily Show - 2024-12-24 - Holiday Special HDTV-720p.mkv
  • Anime: Attack on Titan - S01E13 - 013 - Primal Desire Bluray-1080p.mkv

Adding TV Series

  1. Click Series in the main navigation
  2. Click Add New button
  3. Search for your show by name
  4. Select the series from search results
  5. Configure options:
    • Root Folder: Where to save the show
    • Quality Profile: Desired quality settings
    • Monitor: Which episodes to track (see below)
    • Series Type: Standard, Daily, or Anime
  6. Click Add Series

Monitoring Options

Monitoring OptionBehavior
All EpisodesMonitor and download all episodes (past and future) - ideal for completing a full series
Future EpisodesOnly monitor new episodes from now on - perfect for ongoing shows you're caught up on
Missing EpisodesDownload missing episodes from existing seasons - useful for filling gaps
Existing EpisodesDon't search for old episodes - monitors only what you already have
First SeasonOnly monitor season 1 - great for testing new shows
Latest SeasonOnly monitor the most recent season - conserve bandwidth on long-running shows
Smart Monitoring
Tip

Use Future Episodes for ongoing shows you’re already caught up on to avoid re-downloading existing episodes. For new shows or filling gaps, use Missing Episodes or All Episodes.


Service Management

Sonarr runs as a systemd service for reliability and automatic startup.

Service Commands

CommandDescription
systemctl status sonarr@usernameCheck service status and health
systemctl restart sonarr@usernameRestart the service
systemctl stop sonarr@usernameStop the service
systemctl start sonarr@usernameStart the service
journalctl -u sonarr@username -fView live logs (follow mode)
journalctl -u sonarr@username --since todayView logs from today

4K instance commands:

Replace sonarr with sonarr4k in all commands above:

bash
systemctl status sonarr4k@username
systemctl restart sonarr4k@username
journalctl -u sonarr4k@username -f
Auto-Start on Boot
Info

QuickBox automatically enables Sonarr to start on boot. You don’t need to run systemctl enable manually unless you’ve previously disabled it.


Back up and restore

QuickBox backs Sonarr up for you from the dashboard or the CLI, and the app keeps running while it does. Every backup is saved to /home/username/.QuickBox/software/sonarr/backup/, named with the version and the date. For the 4K instance, replace sonarr with sonarr4k and Sonarr with Sonarr4K in the paths and commands below.

BackupWhat it saves
Config Onlyconfig.xml, the small configuration file. Your library, series and history are in the database, so use Full Backup for them
Full BackupTwo archives: sonarr-<version>-config_<date>.tar.gz holds your config folder /home/username/.config/Sonarr/ (the sonarr.db database, taken as a consistent copy, plus config.xml), and sonarr-<version>-application_<date>.tar.gz holds the install tree /opt/username/Sonarr/. The logs, MediaCover (poster cache), Backups and UpdateLogs folders are left out
NginxSonarr’s nginx config, username.sonarr.conf

From the dashboard: open the App Dashboard, stay on Application Control, expand the Sonarr row and open Operations. Backup offers Full backup, Config Only and Nginx Only, and Restore lists every saved backup; for a full backup its button reads Rollback and puts back both the install tree and the config archive. Restore appears only when your account is allowed to restore backups. You can also open Content → Asset Management Center (AMC in the sidebar), choose the Application Backups tab, expand the Sonarr row and click Back up now; that row lists every saved file with download and delete buttons. See App Management → Application Backups for who can see the tab.

From the CLI:

bash
# Config Only: config.xml
qb manage software -o backup -u username -s sonarr
 
# Full Backup: config folder with the database, plus the install tree
qb manage software -o backup -o app -u username -s sonarr
 
# Roll back to a Full Backup: pick the version from a menu, then confirm
qb manage software -o rollback -o app -u username -s sonarr

Every option is described in the qb manage reference.

A rollback stops Sonarr, clears the stale -wal, -shm and -journal files beside each restored database, puts the archives back, and starts Sonarr again. If Sonarr was running before the rollback, it also waits for Sonarr to answer on its port, and if it does not come back the command reports an error instead of finishing quietly.

Remove and reinstall delete your backups
Caution

qb remove sonarr and qb reinstall sonarr both delete /home/username/.config/Sonarr/ (the database and settings) and the backup folder /home/username/.QuickBox/software/sonarr/ with every backup in it, and clear the rollback list. Before either one, download the Full Backup from the Application Backups tab, or copy the folder somewhere QuickBox does not manage:

bash
cp -a /home/username/.QuickBox/software/sonarr/backup /home/username/sonarr-backup-saved

Restore your library after a reinstall

Because the rollback list is cleared, a Full Backup you saved before a reinstall cannot be rolled back from the dashboard afterwards. Put back the database only and keep the new config.xml, which matches the nginx config QuickBox just wrote. First stop Sonarr from its row in the App Dashboard with the Stop Sonarr button. Then run the file commands as your own account, and start Sonarr again with the Start Sonarr button. An admin with shell access can stop and start it with sudo systemctl stop sonarr@username and sudo systemctl start sonarr@username instead.

bash
rm -f /home/username/.config/Sonarr/sonarr.db-wal /home/username/.config/Sonarr/sonarr.db-shm
tar -xzf /home/username/sonarr-backup-saved/sonarr-<version>-config_<date>.tar.gz -C /home/username/.config/Sonarr ./sonarr.db

Removing the two -wal/-shm files first stops the new install’s journal from being applied to the restored database.


Troubleshooting

Sonarr Won’t Start

Check These First

  • Check service logs: journalctl -u sonarr@username -f
  • Verify port availability: grep -E '<Port>' ~/.config/Sonarr/config.xml
  • Check for database corruption
  • Ensure config directory permissions are correct

Solutions

  • Restart the service: systemctl restart sonarr@username
  • Fix permissions: qb fix permissions -u username
  • Roll back to your last Full Backup if the database is corrupted (Back up and restore)
  • Check for conflicting port usage with other services

View detailed logs:

bash
journalctl -u sonarr@username --since "10 minutes ago" --no-pager

Downloads Not Appearing

Common Issues

  • No releases found in manual search
  • Episodes not automatically downloading
  • Download client connection errors (qBittorrent, Deluge, etc.)
  • Series shows as monitored but nothing happens

How to Fix

  • Verify indexers: Settings → Indexers → Test or check Prowlarr
  • Test download client: Settings → Download Clients → Test
  • Ensure series/episodes are monitored (blue icons on series page)
  • Try manual search: Click episode → Manual Search icon
  • Check quality profile cutoffs haven't been reached

Permission Issues

If Sonarr can’t access files or directories:

bash
# Fix all user permissions
qb fix permissions -u username
 
# Restart Sonarr
systemctl restart sonarr@username
 
# Verify ownership
ls -la ~/.config/Sonarr/
Common Permission Problems
Tip

Permission issues often occur after manually moving files or changing directory ownership. The qb fix permissions command resets ownership recursively for all user directories.

Database Corruption

Symptoms

  • Sonarr won't start with database errors in logs
  • Series or episodes disappearing randomly
  • Settings not saving properly
  • Constant crashes or unexpected behavior

Recovery Steps

  • Roll back to your last Full Backup: App Dashboard, expand the Sonarr row, Operations, Restore, then Rollback (or the CLI command in Back up and restore)
  • No Full Backup yet? Restore Sonarr's own backup from System, Backup inside Sonarr (the zips in ~/.config/Sonarr/Backups)
  • Last resort: stop the service with systemctl stop sonarr@username, copy the damaged sonarr.db somewhere safe, delete it and reconfigure from scratch
  • Do not reinstall to repair the database: qb reinstall sonarr deletes the config folder, database included

Check database integrity (stop the service first with systemctl stop sonarr@username):

bash
sqlite3 ~/.config/Sonarr/sonarr.db "PRAGMA integrity_check;"

Indexer Rate Limiting

If you’re getting rate limit errors from indexers:

  1. Reduce RSS sync interval: Settings → Indexers → Options → RSS Sync Interval (increase to 30-60 minutes)
  2. Use Prowlarr for centralized rate limit management
  3. Remove duplicate or redundant indexers
  4. Consider premium/VIP indexer accounts for higher limits

Best Practices

Do

  • Use Prowlarr for centralized indexer management across all *arr apps
  • Set reasonable quality profiles—avoid unnecessary 4K downloads if you don't need them
  • Monitor only shows you actually want to prevent excessive bandwidth usage
  • Configure proper file naming (Settings → Media Management) for consistent library organization
  • Take a Full Backup before every update, upgrade or reinstall, and download a copy from the Application Backups tab in the Asset Management Center (Back up and restore)
  • Use download client categories (e.g., tv-sonarr) to separate Sonarr downloads
  • Set upgrade cutoffs (e.g., Bluray-1080p) to prevent endless quality chasing
  • Enable notifications (Discord, Telegram, etc.) to track downloads and failed grabs
  • Use separate 4K instance (--4k flag) for 4K content management

Don't

  • Don't monitor every episode of every show—be selective to save bandwidth and storage
  • Don't set upgrade cutoff too high (4K remuxes are 50-100GB+ and may not be necessary)
  • Don't use too many indexers—causes rate limits and excessive API hits
  • Don't download to system drive—use dedicated media storage (/home/username/Media/TV)
  • Don't ignore failed download warnings—investigate and resolve issues promptly
  • Don't mix standard and 4K content in same instance—use separate 4K instance
  • Don't disable authentication if Sonarr is accessible from the internet
  • Don't skip Full Backups, because corruption can happen and a reinstall or remove deletes the database and the backup folder with it
  • Don't use Jackett if Prowlarr is available—Prowlarr is the modern replacement

Sonarr integrates seamlessly with the QuickBox ecosystem:


Additional Resources


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