Menu
ContentsLogs and reporting a problem

  1. Getting started

    1. What Kryspal Media is
    2. System requirements
    3. Install with Docker
    4. First-time setup
    5. Upgrade and back up

  2. Libraries

    1. Create and manage libraries
    2. File and folder naming
    3. Flexible file layout
    4. Metadata and NFO
    5. Tags
    6. Images
    7. strm and cloud drives
    8. StrmTool settings
    9. Subtitles
    10. Intro and outro
    11. Search tips
    12. Actors and people
    13. Duplicate videos

  3. Playback

    1. Web player
    2. Third-party players
    3. Remote access

  4. Members and devices

    1. Members
    2. Parental controls
    3. Devices and simultaneous streams

  5. Plugins

    1. Plugin center
    2. Plugins
    3. Third-party plugins

  6. Move from another server

    1. Move from Emby
    2. Move from Jellyfin

  7. Licenses and plans

    1. Compare plans
    2. PRO features in detail
    3. MAX features in detail
    4. Buy, activate and move a license
    5. Offline grace and expiry

  8. Troubleshooting

    1. Logs and reporting a problem

Logs and reporting problems

When something goes wrong, the logs say what happened. This page shows where to read them, how to turn on debug mode, what to include when you report a problem, and a few quick checks you can do yourself.

On this page
  1. Read the logs
  2. In the admin console
  3. In Docker
  4. Debug mode
  5. Get help
  6. Report a problem
  7. Quick checks

Read the logs#

In the admin console#

Open System → System log. It shows what the server has been doing, in English, for troubleshooting. Keys and URL signatures are masked when they are written.

  • Filter by level (Debug, Info and above, Warnings and above, Errors only), by module, and by text with Search the log. Plugin logs can be filtered too.
  • Live keeps the list updating. Newest lines are on top; Load older shows earlier ones.
  • Export saves the log as a plain text file, oldest first, one entry per line: time, level, module, message and details.
  • The log is kept for 7 days by default. Change it with Log retention (days) under System → Settings.

In Docker#

docker logs --timestamps <server-container>
docker compose logs server

Docker keeps and rotates this log (by default 10 files of 50 MB). Save it before you upgrade or recreate the container.

Debug mode#

Debug mode records every request as one line: method, path, status code and time taken. It does not record query parameters or headers, so tokens are never logged. Use it to see which endpoints a player actually calls.

  1. In compose.yaml, add command: ["-debug"] to the server service, then run docker compose up -d.
  2. Reproduce the problem.
  3. Remove the line again and run docker compose up -d. Debug mode makes the log grow quickly.

In the system log, choose All (with debug) as the level to see these lines.

Get help#

For questions and how-to help, ask in GitHub Discussions, where other users and we can answer.

Report a problem#

For a bug, open an issue in the product's GitHub Issues. Please include:

  • Version. Shown in the sidebar and under System → Status; it is also at the start of docker logs.
  • Environment. Host or NAS model, CPU architecture (x86 or ARM), Docker version, and whether you use Compose or docker run.
  • What happened. What you expected, what actually happened, how to reproduce it, and which players (name and version) are involved.
  • Logs. The part before and after the problem, exported from the admin console or taken from docker logs. Logs contain titles and file paths. Before you post, replace anything you do not want public with a placeholder, and read through it even though credentials are masked.
  • For playback problems. The video's container format and audio and video codecs (shown in the media info of the item's details), whether it played directly or through the proxy, and the player's settings.

Do not attach backup files, database files, key files, API keys, license keys or passwords.

Quick checks#

  • Files are not found. Check that the container sees the same path, and that the user the server runs as can read it (see the user: setting on the install page). If live monitoring hits the inotify limit, it falls back to scheduled scans. That is not a fault.
  • A player cannot connect. Check the port and the firewall. From outside your network, check that the reverse proxy forwards X-Forwarded-Host and X-Forwarded-Proto.
  • Start takes very long. After an upgrade the database may be updating. Wait for healthy and do not restart. See Upgrade and back up.