Skip to Content
TroubleshootingStart Here

Troubleshooting

Two ways in. Scan the symptom index for a line that sounds like what you are seeing, or search the error index for the text on your screen. Every entry points at the page that explains it.

The rest of this section is procedure rather than pointers. Collecting Logs has the log commands for each install path. Reporting a Bug covers what belongs in a report.

72 of 479 Tracearr issues needed a request for more information, and those threads run a median of 6 comments against 2 for everything else. Collect logs before you open one.


Symptom Index

Connecting a Media Server

Sessions and Real-Time Updates

Locations and Geolocation

Signing In

The Mobile App

Automations

Importing History

Jobs and Data

Backups and Restores

Installing and Upgrading

Performance

Remote Access

Logs and Diagnostics


Error Message Index

Match the text on your screen against the strings below.

Media Server Connections

cannot reach [Plex/Emby/Jellyfin] server ... fetch failed

This comes up while adding a media server, usually from IPv6 resolution inside the container. See Disabling IPv6 in Docker.

jellyfin request failed: 500 Internal Server Error
System.MissingMethodException: Method not found: 'System.Collections.Generic.IEnumerable`1<...User> MediaBrowser.Controller.Library.IUserManager.get_Users()'.

The first appears on the Import page after Check Plugin. The second is the matching entry in the Jellyfin log. Both point at Playback Reporting on Jellyfin 10.11.9+.

The SSE Plugin

401 Unauthorized

The token isn’t reaching the server in a form it accepts. See 401 Unauthorized.

404 Not Found

Either the path is wrong for your server type or the plugin isn’t loaded. See 404 Not Found.

disconnected on buffer overflow

Your client is reading slower than events arrive. See Client Keeps Getting Disconnected.

Logs and the Debug Page

No such file or directory

The supervised log paths under /var/log/supervisor/ do not exist on a standard image. Pick your own install path in Collecting Logs.

PostgreSQL Database directory appears to contain a database; Skipping initialization
PostgreSQL init process complete; ready for start up

A captured database log that ends on one of these lines and holds nothing else is missing its stderr. PostgreSQL writes almost everything there. Collecting Logs has the redirect that keeps it.

Log explorer is only available in supervised mode

The Log Explorer switches on the image tag, so a pinned digest or a retagged image loses it even when the files are present. See the Debug Page.

Messages in the Web UI

That doesn't look like a Tracearr share code This code looks cut off That's too big to be a Tracearr automation This needs Tracearr 2.2.0 or newer That's a lot of codes in one minute

All five come from pasting a share code. See Codes That Won’t Read.

already running

A job in SettingsJobs that says this without progressing has stale state from a previous crash. See the FAQ entry.

Invalid QR code Pairing Failed

Pairing tokens last 15 minutes and work once. See Mobile App troubleshooting.

Last updated on