Getting help & feedback

Something broke, looks wrong, or would be nicer another way? Open a report. It lands directly with us, we reply there, and you get an email when we do.

You don't need logs to open a report. Describe what happened and we'll ask for anything else we need. Prefer email? Write to [email protected].

Come talk to us#

There's a community Discord at tofa.tv/discord: release notes for every platform, setup questions, and people running the same hardware as you. It's the fastest way to reach us and each other for anything that isn't a bug report. Bugs still work best through Support in the app, which attaches diagnostics automatically.

What helps us fix it faster#

None of this is required, but each line saves a round trip:

• What you expected, and what actually happened.
• Where: the web app, Apple TV, Android TV, the server itself.
• Your setup: the operating system, native or Docker, and whether the server runs on the machine you watch from.
• For anything visual, a few seconds of screen recording beats a paragraph.

The in-app report (profile menu, Support) attaches client diagnostics automatically, so starting there usually covers the setup questions.

If you want to dig in yourself#

Skim If something is off in the server guide, and check the logs: open your server in the web app and go to Admin, Logs. Many issues explain themselves in the last few lines. The same logs live on disk in the logs folder inside tofa's data folder, and on Docker docker compose logs -f shows them too.

To attach logs to a report:

docker compose logs --tail=200 > tofa-logs.txt

Keep your data in place#

Keep tofa's data folder when updating or moving your server. It holds your database, settings, backups, and the keys tofa generated on first start. On native installs it lives at ~/.tofa (Linux), ~/Library/Application Support/tofa (macOS), or C:\ProgramData\tofa (Windows); on Docker it is the tofa-data volume. Leave it in place across updates, and if you move to a new machine, bring it with you.