Frequently Asked Questions
This page collects common questions and answers encountered while using Ting Reader.
Q: What are the default account and password for first login?
Default account: admin
Default password: admin123
Please change the password promptly after your first login.
Q: How do I scrape book metadata?
Ting Reader has built-in automatic scraping. After adding the library that contains your books, click Scan and the system will automatically try to match audiobook information based on the file name or directory name. If automatic matching fails, you can manually edit the metadata or re-run a search match on the book details page.
Q: Which audio formats are supported?
Currently supported formats include MP3, M4A, M4B, WAV, FLAC, OGG, OPUS, AAC, etc.
Q: What should I do if the client cannot play audio or reports an audio playback error?
This project is a web app; audio playback depends on browser support, so formats the browser does not support cannot be played. You can install the Native Audio Support plugin to enable server-side transcoded playback (for formats such as WMA), and Native Audio Support also supports metadata writing and extraction for multiple formats.
Q: How do I access it externally?
It is recommended to use tools such as Nginx Proxy Manager (NPM), Lucky, or Frp for reverse proxy or NAT traversal. For the best experience (especially for mobile PWA features), configuring an HTTPS certificate is strongly recommended.
Q: The plugin does not appear after installation?
1. Check file permissions and make sure the container has permission to read the plugin files.
2. Check that the plugins directory mapping is correct.
3. Check the container logs (docker-compose logs) and search for the keyword “plugin” to see whether there are any loading errors.
Q: The Native plugin fails to load?
This is usually because the wrong architecture version was downloaded. Please confirm your NAS/server CPU architecture (you can check it with the uname -m command), then download the matching version again.
Q: Why doesn’t the Widget CSS I wrote for positioning work?
Please check where you put the CSS.
- CSS that controls the position (position/right/bottom) must be written in your website HTML (on the div that wraps the iframe).
- CSS that controls the color/font must be written in Ting Reader’s “Custom CSS Injection” setting.
Q: Why can’t clicking the Widget cover go fullscreen?
iframe tag includes the allow="fullscreen" attribute. This is required by browser security policies.Q: The Widget doesn’t display fully on mobile?
150px.