Plex HTPC logs are missing on Linux: use the package’s own path

Identify the application and package

Confirm that the affected application is Plex HTPC and note how it was installed. The publisher’s getting-started guide identifies Linux store routes, while its log guide separates Flatpak and Snap paths. A path copied from a Windows tutorial will not describe either Linux package.

Also record which machine runs Plex Media Server. If the server is on another computer or NAS, its log is a different file from the HTPC client’s log on the viewing computer. The word Plex appearing in a folder name is not enough to identify the component that recorded an event.

Collect the log around one clear reproduction

Plex recommends quitting and restarting the HTPC app, reproducing the issue and then gathering the app log. Its documented Flatpak location is $HOME/.var/app/tv.plex.PlexHTPC/data/plex/Logs; its Snap location is ~/snap/plex-htpc/common/Logs.

Keep the reproduction time and the exact action with the file. For example, failure when selecting a library item is different from a black screen only after playback starts. A short, repeatable sequence helps the person reading the log relate an event to the behaviour you saw.

Share the relevant component evidence

If support requests server evidence as well, label the two sources explicitly: HTPC client and Media Server. Do not substitute the server log merely because it was easier to find. Preserve the original diagnostic file before making any redacted copy for a public discussion.

Inspect material for private server addresses, account information or tokens and use the support channel’s requested sharing method. Plex’s guide prefers an attached log file to pasting its entire contents into a forum post. The useful result is a correctly identified package-specific file linked to one observed event, rather than a large collection of unrelated Plex files.

Sources and further reading

• Plex HTPC app and server logs
• Plex HTPC getting started and desktop installation