Youtarr Troubleshooting Guide

May 15, 2026 · View on GitHub

Login Issues

Cannot Find the Setup Token

Problem: First-time setup wizard asks for a token and you don't know where to find it.

See Authentication - Cannot Find the Setup Token for the full list of solutions.

Forgotten Admin Password {#reset-admin-password}

Problem: Cannot log in because you've forgotten the admin password.

Solution:

Method 1: Using Environment Variables (Recommended)

  1. Stop Youtarr:

    ./stop.sh

  2. Edit your .env file and set new credentials:

    AUTH_PRESET_USERNAME=admin
AUTH_PRESET_PASSWORD=your-new-password

  3. Start Youtarr:

    ./start.sh

  4. Log in with the new credentials. Once logged in, you can remove these variables from .env if desired (credentials will persist in config/config.json)

Method 2: Reset via config.json (Requires localhost access)

  1. Stop Youtarr:

    ./stop.sh

  2. Edit ./config/config.json and delete both the username and passwordHash lines

  3. Start Youtarr:

    ./start.sh

  4. Open Youtarr in any browser. You will be prompted to create a new admin account using the one-time setup token from docker logs youtarr or config/setup-token.

Session Expired

Problem: Getting "Invalid or expired token" errors.

Solution:

  • You will be automatically redirected to the login page
  • Simply log back in with your credentials
  • Sessions expire after 7 days
  • If issues persist, clear browser cache/cookies

Plex API Key Issues

Problem: Cannot connect to Plex server or refresh library.

Solution:

  1. Get a new API key automatically:

    • Go to Configuration page
    • Click "Get Key" button next to Plex API Key field
    • Log in with your Plex account (must have admin access to your server)
    • Save configuration

  2. Get API key manually:

  3. If you have an invalid/old key:

    • Stop Youtarr: ./stop.sh
    • Edit config/config.json and clear the key: "plexApiKey": ""
    • Restart: ./start.sh
    • Get a new key using method 1 or 2 above

Discord Notifications Not Sending

Problem: You never receive Discord alerts after downloads.

Solution:

  1. Open Configuration → Optional: Notifications and confirm Enable Notifications is on.
  2. Verify the Discord webhook URL is correct and saved; click "Send Test Notification" to confirm delivery.
  3. Notifications only send when at least one new video downloads successfully—skipped runs will not trigger an alert.
  4. Check the server logs (docker compose logs -f) for Failed to send notification errors that may indicate network or webhook permission issues.

Test Notification Fails

Problem: "Send Test Notification" shows an error.

Solution:

  1. Ensure the webhook URL is saved and not blank or whitespace.
  2. Confirm the webhook belongs to Discord (URL should start with https://discord.com/api/webhooks/).
  3. Make sure the Discord channel still exists and the webhook has permission to post.
  4. Retry after checking network/firewall rules that may block outbound HTTPS requests.

Automatic Video Removal Issues

Dry Run Preview Fails or Shows "Storage status unavailable"

Problem: Previewing automatic removal returns an error, or the space-based strategy is disabled.

Solution:

  • Confirm the storage indicator at the top of the Configuration page is visible and shows valid values. Space-based removal requires the server to resolve the download directory path and gather disk usage via df.
  • Ensure the DATA_PATH (or selected YouTube directory) exists within the container/host and is mounted with read access to filesystem metadata.
  • If you're running on network storage or uncommon mounts, try remounting with df support or rely on age-based cleanup instead.
  • Retry the preview after saving the configuration again. The preview endpoint requires a valid auth token; log back in if necessary.

Nightly Cleanup Didn't Delete Anything

Problem: Automatic cleanup runs at 2:00 AM but no videos are removed.

Solution:

  • Verify Automatic Video Removal is enabled and at least one threshold (age or free space) is configured on the Configuration page.
  • Run the dry-run preview to see how many videos currently match the thresholds and adjust values if needed (for example, lower the free-space threshold or reduce the age requirement).
  • Check server logs around 2:00 AM for messages prefixed with [CRON] or [Auto-Removal] to confirm the job is executing (docker compose logs -f youtarr).
  • If errors appear in the logs (e.g., permission issues deleting files), resolve those first—the cron job will skip files it cannot delete.

Library / File Issues

Videos Show as "Missing" After I Moved or Renamed Files

Problem: After moving downloaded files to a new location, renaming a folder, or restoring from backup, videos display with a cloud-off icon as if they were deleted.

Solution: Open Settings -> Maintenance and click Rescan files on disk. Youtarr walks the downloads folder, matches files by the [<youtube-id>] segment in each filename, and updates the stored paths and "missing" flags. The same scan also runs daily on a schedule and at server startup.

The rescan recognizes .mp4, .webm, .mkv, .m4v, .avi, and .mp3. Files that no longer have the [<youtube-id>] segment in their name (for example, if you renamed Channel - Video [abc123XYZ01].mp4 to My Movie.mp4) cannot be matched and will continue to show as missing.

I Converted Videos to a Different Format and Youtarr Lost Them

Problem: You used ffmpeg or another tool to convert downloaded .mp4 videos to .mkv (or another container), and Youtarr now lists those videos as missing.

Solution: Run Settings -> Maintenance -> Rescan files on disk. As long as the converted file kept the original [<youtube-id>] segment in its filename and uses one of the supported extensions (.mp4, .webm, .mkv, .m4v, .avi, .mp3), Youtarr will detect the new file, update the stored path, and clear the "missing" flag. See Rescan Files on Disk for full details on supported formats and limitations.

Docker Issues

"Empty section between colons" Error

Problem: Getting error invalid spec: :/usr/src/app/data: empty section between colons when trying to start with Docker Compose.

Cause: You ran docker compose up directly instead of using ./start.sh without creating and configuring your .env file. The docker-compose.yml file requires the YOUTUBE_OUTPUT_DIR environment variable to be set, which ./start.sh reads from your config.json.

Solution:

  1. Use the start script instead of running docker-compose commands directly:
./start.sh

The start script:

  • Reads your configured YouTube output directory from config/config.json
  • Exports it as YOUTUBE_OUTPUT_DIR environment variable
  • Then runs docker-compose with the correct configuration
  1. Using docker-compose commands:
  • Ensure that you have created your .env file from the provided .env.example and configured your YOUTUBE_OUTPUT_DIR before attempting to run docker compose up -d

Docker Desktop Mount Path Error (Windows)

Problem: Error message: Error response from daemon: error while creating mount source path '/run/desktop/mnt/host/...': mkdir /run/desktop/mnt/host/...: file exists

This is a known Docker Desktop issue on Windows where mount points become corrupted.

Solutions (try in order):

  1. Restart Docker Desktop:

    ./stop.sh

    Quit Docker Desktop from system tray, restart it, then:

    ./start.sh

  2. Reset WSL2 mounts:

    • Open PowerShell as Administrator
    • Run: wsl --shutdown
    • Restart Docker Desktop
    • Run ./start.sh

  3. Full system restart:

    • If Docker Desktop hangs, restart your entire machine
    • This clears all stale mount points

Prevention:

  • Always use ./stop.sh before shutting down Docker Desktop
  • Disable Windows Fast Startup (Control Panel → Power Options)
  • Let Docker Desktop fully start before running ./start.sh

Container Won't Start

Problem: Containers fail to start or immediately exit.

Solution:

  1. Check logs:

    docker compose logs -f

  2. Ensure the web port isn't in use:

    netstat -an | grep 3087

Database Issues

Table Corruption After Simultaneous Database and Youtarr Update

Problem: After updating both your external MariaDB/MySQL and Youtarr at the same time, logs show errors like:

SequelizeDatabaseError: Table 'youtarr.Jobs' doesn't exist in engine

(errno 1932), and/or tables appear empty despite having data before the update.

Cause: When MariaDB upgrades to a new version, it performs internal data file upgrades on startup. If a Youtarr migration runs before that process completes, the combination of a database engine upgrade and an ALTER TABLE happening back-to-back can corrupt tables or cause data loss. This is a MariaDB/InnoDB limitation that affects any application running migrations during a database version change.

Solution: Restart Youtarr. In most cases the table corruption is transient and the health check will recover automatically on restart. The error in the logs may look severe, but the database typically self-heals once MariaDB finishes its internal upgrade. Job/download history may be lost, but channels, videos, and settings are unaffected.

Prevention: Never update your database server and Youtarr at the same time. Update MariaDB first, confirm it is fully running (check its logs for "ready for connections"), then update Youtarr. See the External Database Guide for details.

UTF-8 Character Errors

Problem: Errors like Incorrect string value: '\\xF0\\x9F\\xA7\\xA1' when channel names or video titles contain emojis.

By default Youtarr creates the database and tables as utf8mb4, so this shouldn't happen unless you are using an external DB. If so, see External Database Guide for how to create your DB with the correct character set.

How to ensure that your DB is using the correct character set:

  1. Check your database character set by connecting to the DB and then running:
    -- Database Character Set
    SELECT 'DATABASE' as Object_Type, 'youtarr' as Name, DEFAULT_CHARACTER_SET_NAME as   Charset, DEFAULT_COLLATION_NAME as Collation
    FROM information_schema.SCHEMATA
    WHERE SCHEMA_NAME = 'youtarr';

    -- Table Character Sets (excluding Sequelize metadata)
    SELECT 'TABLE' as Object_Type, TABLE_NAME as Name,
    IFNULL(CCSA.CHARACTER_SET_NAME, '') as Charset,
    TABLE_COLLATION as Collation
    FROM information_schema.tables t
    LEFT JOIN information_schema.COLLATION_CHARACTER_SET_APPLICABILITY CCSA
    ON t.TABLE_COLLATION = CCSA.COLLATION_NAME
    WHERE TABLE_SCHEMA = 'youtarr'
    AND TABLE_TYPE = 'BASE TABLE'
    AND TABLE_NAME != 'SequelizeMeta'
    ORDER BY TABLE_NAME;

It doesn't matter if the SequelizeMeta table is not utf8mb4

Solution Either:

  1. Recreate your DB with the correct character set (THIS WILL CAUSE LOSS OF ALL DB DATA) or
  2. Backup your DB and then alter your existing DB to the correct character set using:
  ALTER DATABASE youtarr CHARACTER SET = utf8mb4 COLLATE = utf8mb4_unicode_ci;

Database Connection Failed

Problem: Cannot connect to database errors.

Solution:

  1. Ensure the database container is running (the commands below only applies if using the bundled DB):

    docker ps | grep youtarr-db

  2. Check database logs:

    docker logs youtarr-db

  3. Verify database credentials in environment

Access Denied for Custom Database User

Problem: After changing DB_USER and DB_PASSWORD in your .env file to use a non-root user, you see access denied errors in the logs:

youtarr-db  | 2025-11-22  6:28:19 8 [Warning] Access denied for user '<DB_USER>'@'172.25.0.3' (using password: YES)

Cause: When using the bundled MariaDB container, you changed DB_USER and DB_PASSWORD in .env but forgot to uncomment the corresponding MYSQL_USER and MYSQL_PASSWORD environment variables in docker-compose.yml. MariaDB needs these variables to create the custom user during initialization.

Solution:

  1. Stop Youtarr: ./stop.sh or docker compose down

  2. Edit docker-compose.yml and uncomment the MYSQL_USER and MYSQL_PASSWORD lines under the youtarr-db service:

    environment:
  MYSQL_ROOT_PASSWORD: ${DB_ROOT_PASSWORD}
  MYSQL_DATABASE: ${DB_NAME}
  MYSQL_USER: ${DB_USER}        # Uncomment this line
  MYSQL_PASSWORD: ${DB_PASSWORD}  # Uncomment this line

  3. If the database has already been initialized with incorrect credentials, remove the database directory:

    WARNING: This will completely remove your DB data!

    rm -rf ./database
# Or if using a named volume:
docker volume rm youtarr-db-data

  4. Start Youtarr again: ./start.sh or docker compose up -d

Note: This only applies when using the bundled MariaDB container. External database setups don't need the MYSQL_USER/MYSQL_PASSWORD variables.

MariaDB init: Operation CREATE USER failed for 'root'@'%'

Problem: Fresh installs that only use .env + docker-compose.yml fail during the MariaDB bootstrap with:

ERROR 1396 (HY000) at line 21: Operation CREATE USER failed for 'root'@'%'

Cause: The compose file was configured to set MYSQL_USER=root. MariaDB already creates the root accounts internally, so trying to create it again aborts initialization and leaves the builtin tables in a crashed state.

Solution:

  1. Leave the MYSQL_USER / MYSQL_PASSWORD lines commented out in docker-compose.yml when DB_USER=root (the default). Only uncomment them if you explicitly set a non-root DB_USER / DB_PASSWORD in .env.
  2. Remove the broken datadir (rm -rf ./database or docker volume rm youtarr-db-data, depending on which storage you use).
  3. Run docker compose up -d again. MariaDB will initialize cleanly.

Duplicate Column Errors After Upgrade

Problem: MariaDB logs Duplicate column name 'duration' (or similar) when the stack starts. The API returns Database error: Duplicate column name ....

Cause: The SequelizeMeta table was lost or corrupted, so Sequelize re-ran migrations on top of a populated schema. Every migration now checks for existing tables/columns/indexes before mutating anything, so simply restarting the containers lets the stack skip duplicate work automatically in most cases. NOTE: This should not happen anymore, migrations have been updated to be idempotent.

Solution:

  1. Restart the stack (docker compose up -d). If the schema had already been migrated, the rerun will now skip those operations.
  2. If the error persists, check docker compose logs youtarr to see which migration is still failing.
  3. Manually reconcile the schema for that migration:
    • Connect to MariaDB: docker compose exec youtarr-db mysql -u root -p youtarr
    • Drop the duplicate column or table mentioned in the error (for example ALTER TABLE Videos DROP COLUMN media_type;), or restore a known-good backup.
    • Exit MySQL and restart the stack.
  4. Once the stack is back online, verify the latest schema under Configuration → System → Database Health.

Tip: run with a named volume (see Docker Desktop/ARM/Synology sections) so filesystem corruption is less likely to recur.

Docker Desktop / ARM: Incorrect information in file errors

Problem: MariaDB logs errors like:

ERROR 1033 (HY000): Incorrect information in file: './youtarr/videos.frm'

or:

errno 1932 - Table 'youtarr.videos' doesn't exist in engine

This can happen when MariaDB data lives on the bind-mounted host directory (./database:/var/lib/mysql) and Docker proxies that directory through a virtualized filesystem, most often Docker Desktop on Windows/macOS, ARM hosts, or some NAS setups. During DDL operations such as CREATE TABLE or ALTER TABLE, InnoDB can end up out of sync with MariaDB's table metadata. Native Linux Docker hosts are usually unaffected.

Existing install with data to preserve

Use the migration helper. It dumps the bind-mounted DB, preserves ./database/ as a timestamped backup directory, pins the named-volume override in .env, and imports the dump into a fresh named-volume MariaDB:

./scripts/migrate-to-named-volume.sh

See Database Management for the full migration and revert details.

Fresh install with no data to preserve

Start with the named-volume override:

docker compose -f docker-compose.yml -f docker-compose.arm.yml up -d

Or add this to .env before plain docker compose up -d:

COMPOSE_PATH_SEPARATOR=:
COMPOSE_FILE=docker-compose.yml:docker-compose.arm.yml

Alternatives:

  • Point Youtarr at an external MariaDB/MySQL instance via ./start-with-external-db.sh.
  • Run the stack on Linux/WSL, which uses a native filesystem for bind mounts.

Download Issues

Videos Not Downloading

Problem: Channels are added but videos aren't downloading.

Checklist:

  1. Check the download directory is correctly configured
  2. Verify the directory is accessible by Docker
  3. Check logs for yt-dlp errors: 
    docker compose logs -f youtarr | grep yt-dlp
  4. Ensure the cron schedule is configured (default: every 6 hours)
  5. Manually trigger a download from the Channels page

yt-dlp Errors

Problem: yt-dlp fails to download videos.

Solution #1:

Youtarr's Docker image includes yt-dlp which auto-updates on every release, update to the latest version if behind:

  • Via docker compose: 
    docker compose down
docker compose pull
docker compose up -d
  • Using helper scripts: 
    ./stop.sh
./start.sh --pull-latest

Solution #2:

YouTube is blocking your downloads.

  1. Try enabling and uploading cookies in Configuration -> Cookie Configuration
  2. If only some videos are failing, try increasing the "Sleep Between Requests" value in Configuration -> Advanced Settings
  3. Try using a proxy, or switching to a VPN

NOTE: In some cases YouTube may temporarily blacklist your IP address if too many requests were happening from your IP. You may just need to wait in order to download again. You can manually test downloading a video from YouTube to rule out Youtarr-specific issues by downloading yt-dlp and attempting to manually download a single video.

Slow Channel Operations with Proxy

Adding or Refreshing Channels Takes ~15 Seconds

Problem: Adding a new channel or refreshing channel metadata takes around 15 seconds longer than expected.

Cause: Youtarr first attempts direct HTTP requests for thumbnails and RSS feeds. When you're using a SOCKS5 or HTTP proxy, these direct requests cannot reach YouTube and must wait for a 15-second timeout before falling back to yt-dlp, which correctly uses your configured proxy.

Solution: This is expected behavior and no action is needed. The operations will complete successfully after the brief timeout. If operations are taking significantly longer than 15-20 seconds, verify your proxy is correctly configured in Configuration > Advanced Settings.

Plex Integration Issues

Videos Not Showing in Plex

Problem: Downloaded videos don't appear in Plex library.

Checklist:

  1. Verify Plex library is set to "Other Videos" type
  2. Ensure Plex agent is "Personal Media"
  3. Check Plex has access to the download directory
  4. Manually scan the library in Plex
  5. Verify Plex server IP and port are correct
    • Docker Desktop (Windows/macOS): host.docker.internal
    • Docker on macOS without Docker Desktop (e.g., Colima): host LAN IP (e.g., 192.168.x.x) or host.lima.internal
    • Docker on Linux or running inside WSL2 without Docker Desktop: host LAN IP (e.g., 192.168.x.x)
    • Ensure the Plex Port matches your Plex configuration (default 32400).

Cannot Connect to Plex

Problem: Youtarr cannot communicate with Plex server.

Solution:

  1. Verify the Plex IP and port settings:
  • Docker Desktop (Windows/macOS): use host.docker.internal
  • Docker on macOS without Docker Desktop (e.g., Colima): use the host LAN IP (e.g., 192.168.x.x) or host.lima.internal
  • Docker on Linux or running inside WSL2 without Docker Desktop: use the host LAN IP (e.g., 192.168.x.x)
  • Update the Plex Port field if Plex listens on a non-default port (default 32400).
  1. Ensure Plex is running on the same machine
  2. Check firewall isn't blocking local connections
  3. Verify Plex is accessible at the configured IP and port

Channel Import Issues

Cookies Upload Fails or Returns No Channels

Problem: Uploading a cookies file returns an error, or YouTube reports no subscriptions for the account.

Common causes and solutions:

  1. Expired or invalid cookies: Cookies from YouTube sessions expire. If you see "cookies appear to be expired or invalid," sign into YouTube in your browser, re-export your cookies using a browser extension (e.g., "Get cookies.txt LOCALLY"), and upload the fresh file.

  2. Wrong file format: The cookies file must be in Netscape cookies.txt format (the first line starts with # Netscape HTTP Cookie File). If you copied cookies from browser dev tools or exported in a different format, the upload will be rejected. Use a browser extension that exports in the Netscape format.

  3. Not logged into the right YouTube account: If the upload succeeds but returns zero channels, the cookies may belong to an account with no subscriptions. Make sure you are signed into the correct YouTube account before exporting cookies.

  4. Bot detection / verification challenge: YouTube sometimes flags automated access and shows a CAPTCHA or verification prompt. If you see "YouTube is asking for verification," open YouTube in your browser using the same account, complete any security challenges, then re-export your cookies and try again.

CSV Upload Errors

Problem: Uploading a CSV file returns "Missing header" or another parsing error.

Common causes and solutions:

  1. Wrong file: The import expects the subscriptions.csv file from Google Takeout, which has exactly three columns: Channel Id, Channel Url, Channel Title. If you uploaded a different CSV (e.g., a watch history or playlist export), select the correct file from your Takeout archive under YouTube and YouTube Music/subscriptions/subscriptions.csv.

  2. File too large: CSV uploads are limited to 5 MB. A typical Takeout subscriptions file is well under this limit. If your file exceeds it, verify you selected the right file; the subscriptions CSV should not be that large.

  3. Encoding issues: The parser expects UTF-8 encoding and handles a UTF-8 BOM if present. If your CSV was re-saved in a different encoding (e.g., UTF-16 or Latin-1), re-export from Google Takeout or re-save as UTF-8 in a text editor before uploading.

  4. No valid channels found: If the file parses but contains no rows with valid YouTube channel IDs (IDs starting with "UC"), the CSV may have been modified or corrupted. Download a fresh copy from Google Takeout.

Individual Channels Fail During Import

Problem: Some channels show errors during import while others succeed.

Per-channel failures are normal and do not stop the overall import. The import processes each channel independently and records individual results. Common reasons a single channel may fail:

  1. Bot detection / rate limiting: YouTube may throttle or block requests when many channels are resolved in sequence. Failed channels are marked with their error, and you can retry them later by running another import.

  2. Private or terminated channels: Channels that have been made private, deleted, or terminated by YouTube will fail with a lookup error. These cannot be imported.

  3. Network timeouts: Transient network issues can cause individual channel lookups to fail. Check the per-channel status on the import progress page; channels that failed due to temporary errors can be retried in a subsequent import.

Import Appears Stuck

Problem: The import has been running for a long time with no visible progress.

Large imports take time because each channel requires a yt-dlp lookup to resolve metadata (name, thumbnail, video feed URL). An import of several hundred channels can take 10-30 minutes depending on network speed and YouTube's response times.

What to check:

  1. Open the import progress page to see per-channel status. If channels are still being processed, the import is working normally.
  2. Check the container logs for errors: docker compose logs -f youtarr
  3. If the import is truly unresponsive (no channels have progressed for several minutes), you can cancel it from the progress page and start a new one.

"Too Many Requests" Error

Problem: The cookies upload endpoint returns a 429 "Too many requests" error.

The cookies preview endpoint is rate-limited to 3 requests per minute because each request runs a yt-dlp process against YouTube. Wait at least one minute before retrying. If you need to test multiple cookies files, space your uploads about 20-30 seconds apart.

Performance Issues

High Memory/CPU Usage

Problem: Youtarr consuming excessive resources.

Solution:

  1. Check for stuck download jobs (these can be cleared by restarting Youtarr)
  2. Restart containers: 
    ./stop.sh
./start.sh
  3. Check disk space - low space can cause performance issues

Network Access Issues

Cannot Access from Other Devices

Problem: Can't access Youtarr from other computers on the network.

Solution:

  1. Configure firewall to allow port 3087
  2. Use server's actual IP address, not localhost
  3. Check Windows Defender Firewall settings
  4. Verify router settings if accessing from different subnet

Metadata Issues

Metadata Not Showing in Media Server

Problem: Videos play but metadata (title, description, etc.) isn't displaying in your media server.

Plex

Solution:

  • Ensure "Local Media Assets" is enabled in your library agent settings
  • Place Local Media Assets at the top of the agent priority list
  • Check container logs for "Successfully added additional metadata to video file"
  • Try "Refresh Metadata" on the library or individual items
  • Verify the library type is "Other Videos" with "Personal Media" agent

Kodi/Jellyfin/Emby

Solution:

  • Verify .nfo files exist alongside video files (same name, different extension)
  • Ensure library is configured as "Movies" or "Mixed" type
  • Enable "Nfo" metadata reader in library settings
  • Disable all online metadata scrapers to avoid conflicts
  • Try a full library rescan
  • Check file permissions - media server must be able to read .nfo files

Channel Posters Not Displaying

Problem: Channel folders don't show artwork/posters. NOTE: Plex does not support channel posters, this is only supported on Kodi/Jellyfin/Emby

Solution:

  • Verify poster.jpg exists in each channel folder
  • Check that "Copy channel poster.jpg files" is enabled in Configuration
  • Ensure media server has read permissions for image files
  • Some servers cache artwork - try:
    • Clearing server cache
    • Restarting the media server
    • Removing and re-adding the library

Special Characters in Titles/Metadata

Problem: Titles with $, &, or other special characters display incorrectly.

Solution:

  • Youtarr properly escapes XML characters in NFO files
  • For Plex: Embedded metadata handles special characters automatically
  • If issues persist:
    • Check media server logs for XML parsing errors
    • Verify you're running the latest version of Youtarr
    • Report specific character issues on GitHub

NFO Files Not Being Created

Problem: Videos download but no .nfo files are generated.

Solution:

  • Check that "Generate video .nfo files" is enabled in Configuration
  • Verify post-processing completed (check container logs)
  • Ensure write permissions in video directories
  • Look for errors in logs during post-processing phase

Getting Help

If these solutions don't resolve your issue:

  1. Check the GitHub Issues page
  2. Provide details about your operating system
  3. Provide relevant logs when reporting issues: 
    docker compose logs --tail=100 youtarr
  4. Include your configuration (without sensitive data)
  5. Describe steps to reproduce the problem