Coma

COMA Media Server

Troubleshooting

Step-by-step COMA Media Server troubleshooting for playback, transcoding, remote access, downloads, database locks, backups, cloud portal refreshes, and support packs.

Before you change settings

Make one change at a time, test again, and keep a note of the exact error shown in COMA Admin or the browser player.

Duplicate Or Missing Files

Fixes

  1. Open Admin > Library Tools.
  2. Review duplicate groups.
  3. Confirm whether files are truly duplicated or just renamed.
  4. Use merge or delete missing-file workflows.
  5. Run Empty Trash only after confirming the file is gone intentionally.

Playback Will Not Start

Symptoms

  • Black player
  • Spinner never ends
  • Browser says media cannot be played
  • Playback starts on one device but not another

Fixes

  1. Try another browser first.
  2. Open Admin > Dashboard and check active streams.
  3. Open Admin > Transcodes and check whether a transcode failed.
  4. Confirm FFmpeg is available.
  5. Try a lower quality option such as 10 Mbps or 4 Mbps.
  6. If subtitles are enabled, try playback with subtitles off.
  7. If HDR video looks wrong, try SDR fallback or transcode mode.
ffmpeg -version

Transcoding Is Slow

Likely causes

  • CPU is too weak for the selected quality
  • Multiple transcodes are active
  • Subtitles require burn-in
  • HDR to SDR conversion is required
  • Hardware acceleration is unavailable or misconfigured

Fixes

  1. Check Admin > Dashboard for CPU and RAM.
  2. Check Admin > Transcodes for active jobs.
  3. Lower remote quality.
  4. Prefer Direct Play where possible.
  5. Use text subtitles instead of image subtitles where possible.
  6. Enable hardware acceleration only when drivers and FFmpeg support it.

Remote Access Not Available

Symptoms

  • Works locally but not outside the house
  • Cloud portal sees the server but cannot play media
  • Remote access says unavailable

Fixes

  1. Open Admin > Networking.
  2. Check public URL, Cloudflare Tunnel status, port check, HTTPS status, and bandwidth test.
  3. For direct WAN access, confirm router port forwarding points to the COMA server.
  4. For Cloudflare Tunnel, confirm the public hostname points to:
  5. http://localhost:31314
  6. Confirm the external URL in COMA is correct.
  7. Confirm firewall allows inbound traffic if not using a tunnel.
cloudflared tunnel list
curl -I http://localhost:31314

Downloads Do Not Appear

Fixes

  1. Admin must enable downloads.
  2. User or profile must have download permission.
  3. The account plan and offline access rules must allow downloads.
  4. For TV shows, check the episode card rather than only the show page.
  5. Try original download first, then optimized download.

Database Is Locked

Symptoms

  • database is locked
  • Admin pages hang
  • Scan stops during heavy activity

Fixes

  1. Wait one minute and retry.
  2. Stop active scans or transcodes.
  3. Restart COMA.
  4. Avoid storing the SQLite database in cloud-sync folders like OneDrive, Dropbox, or network shares.
  5. Run Backup before repair operations.
systemctl restart coma
systemctl status coma

Backup Or Restore Fails

Fixes

  1. Confirm the backup folder exists.
  2. Confirm the service user has write access.
  3. Ensure enough disk space is available.
  4. Stop scans and transcodes before restoring.
  5. Restart the server after restore.
df -h
ls -la /path/to/backups

Cloud Portal Cannot Refresh Libraries

Symptoms

  • Account session expired or revoked
  • No libraries found
  • No servers found

Fixes

  1. Log out and back into the cloud portal.
  2. Open local COMA Admin > Licence and click Validate.
  3. Open local COMA Admin > Linked Servers and refresh.
  4. Confirm the local server is online.
  5. Confirm the server is claimed to the same cloud account.
  6. Confirm the licence allows the server count.

Safe Support Pack

Fixes

  1. COMA version
  2. Operating system
  3. Install type: Windows installer, Linux installer
coma --version
uname -a
systemctl status coma

Click-Through Troubleshooter

Choose the closest issue and follow the first focused checks before contacting support.

Keep support packs safe

Do not send passwords, licence keys, API keys, payment secrets, private media paths you do not want shared, or full database files unless support explicitly asks for them.