Guides

Troubleshooting

Morrow cannot connect to the server

  1. Open the same server address in a browser on the affected device.
  2. Confirm the address includes the correct scheme (https:// or http://) and port.
  3. Confirm your username and password still work in the server web interface.
  4. Temporarily test from the same local network as the server.
  5. If you use a reverse proxy, check its logs and authentication rules.

The library is empty or incomplete

Covers, titles, or chapters look wrong

Morrow shows what your server has for each book: the cover, title, author, narrator, series, description, and chapter list all come from the server's metadata. When one of them is missing or wrong, fix it on the server, and Morrow picks up the change the next time it refreshes the library.

A few patterns worth knowing:

The library takes a long time to load

Under about 8,000 books: the first load streams in from the server, then Morrow keeps a local snapshot so the grid appears instantly next time, refreshing in the background. If it seems permanently stale, switch servers and back, or restart the app.

Above that, Morrow loads a page at a time as you scroll instead of caching the whole library. See Does Morrow handle very large libraries? in the FAQ. If the Library tab or search feels slow there, that's more likely your server needing a moment under load than the app being stuck.

Playback does not start, or starts slowly

Playback stops when the app is closed or the screen locks

Morrow plays in the background and on the lock screen. If audio stops when leaving the app, make sure you are on the latest build, then restart the device. Explicitly force-stopping the app stops playback on both platforms; normal backgrounding should not.

A book is missing from Home's Continue Listening

Progress is not updating

Downloads or caching won't start

Morrow keeps asking for my password

Some servers rotate or expire passwords. When a server rejects the saved password, Morrow offers to re-enter it. You can dismiss that prompt and it will stay quiet until the next launch.

For Audiobookshelf, the durable fix is an API key: open the server in Settings, switch Sign in with to API Key, and paste a key generated in the Audiobookshelf web UI under Settings → API Keys. API keys survive password changes.

My server is behind Cloudflare and Morrow can't reach it

Edge protection blocks requests that don't carry the right header, so the connection fails before your server ever sees it. Open the server in Settings → Advanced and add the required headers. There's a one-tap Cloudflare Access preset for the standard service-token pair.

Three things to check when it still won't connect:

Paste only the token itself. Each field takes the bare value and nothing else. Copying credentials out of the Cloudflare dashboard can pick up the header name or a label along with the value, and Morrow sends exactly what you give it, so CF-Access-Client-Secret: abc123 in the value field is rejected at the edge. Tap the eye icon on each field and confirm there is no header name, label, or stray space.

Set the SSL/TLS encryption mode to Full or Full (strict), not Flexible. On Flexible, Cloudflare contacts your server over plain HTTP, and a reverse proxy that requires HTTPS will redirect it straight back, looping until the request fails. If your server's own web interface also fails or loops in a browser at the same address, this is why, and it is a Cloudflare setting rather than anything in Morrow.

Set the Access policy action to Service Auth. Service tokens only work under that action. Cloudflare warns about this in the dashboard when the policy uses only service token selectors.

These headers work the same way for every server type Morrow supports.

Reporting a problem

Use the bug report form and include:

Never include passwords, API keys, access tokens, private server addresses, or unredacted logs containing credentials.