Guides · Troubleshooting
SoundLeaf error messages and how to fix them (Audiobookshelf on iPhone)
What each SoundLeaf error message means and how to fix it: signing in, connecting to Audiobookshelf, OpenID, downloads, podcasts, the reader and more.
Find the message you saw below, word for word. Each one says what usually causes it and what to do about it.
Most messages about connecting come down to the server address. If you’re not sure yours is right, start with What to type as your server address.
Signing in and connecting
”Could not connect with HTTPS or HTTP”
You typed the address without http:// or https://, so SoundLeaf tried both and neither worked. The rest of the message gives the reason for each try.
Type the address with http:// (for a home IP or Tailscale) or https:// (for a domain), then read the single reason you get back. Check the port too: a home server usually needs :13378.
”Enter a full server address, starting with https:// or http://.”
The start of the address is wrong, for example htp:// or http//, or there’s nothing after it. Retype it, like http://192.168.1.50:13378.
”Network error: Cannot connect to server. Please check your internet connection.”
Nothing answered at that address and port. Usual causes: the wrong IP or port, localhost (which means the phone itself), a server that’s off, or a firewall on the server computer.
Open the same address in Safari on the phone. If that fails too, see Audiobookshelf works in the browser but the app can’t connect.
”Network error: No internet connection. Please check your internet connection.”
The phone has no working connection right now. Check Wi-Fi or mobile data. Downloaded books still play, see Listen offline.
”Request timed out. Please check your connection and try again.”
The phone asked and got no reply in time. Common causes: a home IP while you’re away from home, a Docker container address starting with 172., or a firewall that drops the request.
Check you’re using an address that works where you are. For home and away, see Home and away server addresses.
”Secure connection failed. Check your server’s SSL certificate.”
HTTPS didn’t work. If you connect straight to Audiobookshelf on a home IP or Tailscale address, use http:// instead, because Audiobookshelf itself doesn’t serve HTTPS. On a domain, check your certificate is valid and not self-signed.
”No Audiobookshelf server was found at this address. Check the address, including any path after the host name.”
Something answered, but it said there was nothing there. The path is usually the problem: a missing or extra /audiobookshelf, or a typo after the server name.
”The address did not return an Audiobookshelf status response. Check the address and any proxy sign-in requirements.”
Something answered with a reply SoundLeaf couldn’t read as Audiobookshelf. Often it’s a sign-in page in front of your server, such as Cloudflare Access or Authelia.
Let the app through that sign-in page. For Cloudflare Access, add a service token, see Cloudflare Access setup. Headers like that go in Connection settings on the sign-in screen.
”This address does not lead to an Audiobookshelf server.”
The address works, but a different app answered. Check the port. Another program on the same computer may use the port you typed.
”Finish setting up the server, then try again.”
The server is brand new and has no first account yet. Open it in a browser, create the first user, then come back to SoundLeaf.
”The server denied access (401). Check the address and any required connection headers.”
Something in front of Audiobookshelf asked for a login before the app could even check the server. That’s usually a proxy with its own sign-in. Add the headers it needs in Connection settings, or let the app’s requests through the proxy. See Reverse proxy setup.
”Access was denied (403).”
The server, or a proxy in front of it, refused the request. The rest of the message is what the server said. A 403 often comes from a proxy rule, a firewall such as Cloudflare’s, or a missing service token. Check your proxy’s rules for requests from the app.
”Invalid username or password. Check both and try again.”
The server didn’t accept the login. Passwords are case-sensitive. Usernames aren’t. If you forgot the password, see Reset your Audiobookshelf password.
If your server uses OpenID, sign in with the OpenID button instead. SoundLeaf has no API key login.
”Too many requests. Please wait a moment and try again.”
Audiobookshelf limits sign-in attempts. Since version 2.26.0 it allows 40 attempts in 10 minutes by default, and your server admin can change that. Wait a few minutes, then try once with the right details.
”The server did not send a sign-in token. Try again.”
The server accepted the login but didn’t send back what the app needs. Try again. If it keeps happening, update Audiobookshelf.
”Authentication failed. Please check your credentials or try logging in again.”
The server stopped accepting your sign-in. Sign in again when SoundLeaf asks. If it happens again and again, see Audiobookshelf keeps logging me out.
”Your session has expired. Please log in again.”
Your sign-in has run out. Sign in again. Your downloads and saved progress stay on the phone.
”Sign in again to reconnect this account. Your saved content is still available.”
SoundLeaf couldn’t renew your sign-in for this account, so it needs you to sign in again. Nothing on the phone has been deleted. Sign in and it carries on.
”The server could not be reached. Try again shortly.”
SoundLeaf tried to renew your sign-in and couldn’t reach the server. It’s usually a short outage or a poor connection. Wait a moment and try again.
”Couldn’t reach your server”
This shows on Home when the app can’t load your shelves and has nothing saved to show. Tap Retry. If it keeps failing, check the server is running and the address works in Safari.
”Not reachable, or not an Audiobookshelf server”
This shows next to an address in your server’s address list. The app tested that address and it didn’t work from where you are. That’s normal for a home address when you’re away. See Home and away server addresses.
”Reconnecting” at the top of Settings
The line under your server address says Reconnecting while SoundLeaf’s live connection to the server is down. That happens when the server is down too. If books still stream and the server is otherwise fine, only the live connection is blocked: playback and progress keep working, and only live updates, like progress from another device, have to wait. The usual cause is a reverse proxy that doesn’t pass WebSocket traffic. See Socket failed to connect.
Signing in with OpenID
OpenID lets you sign in through another login service instead of an Audiobookshelf password. Some messages call it SSO (single sign-on). All of these are covered in more detail in Sign in with OpenID.
”Your server hasn’t allowed OpenID sign-in for SoundLeaf.”
The server admin needs to add soundleaf://oauth to Allowed Mobile Redirect URIs in Audiobookshelf’s OpenID Connect settings. Keep any entries that are already there.
”The server did not start the SSO login. Check that OpenID is set up on the server.”
The server didn’t open the login page. Check OpenID is turned on and set up in Audiobookshelf, and that a proxy isn’t blocking the request.
”SSO login failed:”
The server or the identity provider (the service you sign in with, like Authentik or Pocket ID) said no. The reason follows the colon. See Audiobookshelf OpenID login errors.
”The SSO answer did not match this login attempt. Please try again.”
The login that came back belongs to a different attempt. This can happen when an older login page was left open. Close the login page and start again.
”The SSO login session was lost (the server may have restarted). Please try again.”
The server forgot the login halfway through, usually because it restarted. Start the login again.
”The identity provider did not send a login code. Please try again.”
The login came back without the code SoundLeaf needs to finish. Try again, and finish signing in on the provider’s page.
Downloads
More on downloads in Downloads.
”This book can’t be downloaded”
This alert says the download couldn’t start. The reason is in the message below the title, and the entries below explain each one.
”Not enough storage.”
The phone doesn’t have room. The message says how much the download needs, how much SoundLeaf keeps free, and how much is left. Free some space, or remove finished downloads.
”This book has no audio files, so there is nothing to download.”
The library item has no audio on the server, for example an ebook on its own. Check the item in Audiobookshelf.
”The server returned incomplete audio file details. Rescan this book in Audiobookshelf, then try downloading again.”
The server didn’t list all of the book’s audio files properly. In Audiobookshelf, open the book and scan it again, then download.
”Your server denied access to a file. Your sign-in may have expired during the download.”
The server said no partway through, usually because the sign-in ran out on a long download. SoundLeaf tries again by itself. If it keeps failing, check your account has the Can Download permission in Audiobookshelf, see Users and permissions.
”Your server does not have one of this book’s files.”
A file the book lists is missing on the server, often after files were moved or renamed. Scan the library in Audiobookshelf, then tap Try again.
”Your server returned error 500 while downloading a file.”
The number can differ. A 500-type error means the server had a problem. SoundLeaf tries again by itself. If it keeps failing, check the server’s logs.
”A connection problem interrupted the download.”
The connection dropped. SoundLeaf tries again the next time you open the app with a working connection, or you can tap Try again.
”Couldn’t reach your server to finish the download.”
The server stopped answering partway through, for example when you left home Wi-Fi on a home-only address. SoundLeaf tries again the next time you open the app and the server can be reached.
”The download has stopped receiving data.”
The download is still open, but nothing is arriving. Tap Try again. If it happens often away from home, a tunnel or proxy may be cutting long downloads.
”One file did not download completely.”
A file arrived cut short. SoundLeaf tries again. If it keeps happening, look at any proxy or tunnel between the phone and the server.
”The secure connection to your server failed.”
HTTPS failed during the download, often a certificate problem. Check your server’s certificate.
”This device is out of room, so the file could not be saved. Free some space and try again.”
The phone filled up during the download. Free some space, then tap Try again.
”Changed on the server. Delete it and download it again.”
The book’s files changed on the server after you downloaded it. Delete the download and download it again so you have the new files. This book changed on the server is the same notice on the book’s page.
Podcasts
More in Podcasts.
”Your server refused the download. Sign in again?”
The server said no to an episode download. Sign in again. If that doesn’t help, check your account can download.
”Your server does not have that episode’s file.”
The episode’s file is gone from the server. Download the episode to the server again in Audiobookshelf.
”Your account does not have download permission.”
Your Audiobookshelf user can’t download. A server admin can turn on Can Download for your user, see Users and permissions.
”Episode isn’t downloadable yet”
The server has no audio file for this episode yet. Download the episode to the server in Audiobookshelf first.
”Only a server admin can add podcasts to Audiobookshelf. Share the RSS feed with them.”
Your account isn’t an admin, so you can’t add a show. Send the show’s RSS feed to your server admin.
”Couldn’t check for new podcasts. Showing the ones on this device.”
The app couldn’t reach the server, so it shows the podcasts it already has. They update the next time the app reaches your server.
”Discovery is unavailable. Try again shortly.”
Podcast search isn’t working right now. Try again later. Couldn’t reach discovery. Try again when you’re connected. means SoundLeaf couldn’t load podcast results. Check your connection and try again.
Reader and Read Along
More in Ebook reader.
”Couldn’t open ebook”
The ebook didn’t open. The reason is below the title. Tap Retry. If it fails again, check the ebook opens in the Audiobookshelf web reader. Could not open ebook is the same problem from the Read button, and it offers Ebook options to pick another ebook.
”Read Along requires on-device speech recognition, which isn’t available on this device.”
Read Along listens to the audio on your phone to match it to the text, and this device can’t do that. The rest of the reader still works.
”Allow Speech Recognition in Settings to find audio.”
Speech Recognition is turned off for SoundLeaf. Turn it on in the iPhone Settings app, under SoundLeaf.
”Download the audio to find this passage.”
Read Along and Play from this page need the audio downloaded to your phone. Download the book, then try again.
”No confident match in 60s.”
SoundLeaf couldn’t find that passage in the audio. Select a longer passage, or lower Match strictness in Settings > Reading & listening, under Read Along.
”Read Along wasn’t ready after 40s. Try again.”
Read Along couldn’t prepare your place in time, so it stopped. Try again, or let SoundLeaf prepare books ahead of time with When to prepare automatically in Settings > Reading & listening, under Read Along.
”The book’s files have changed. Read Along needs to process this version again.”
The audio or ebook changed on the server. Read Along has to match them again before it can follow along.
Companion ebooks
These come from ebook servers you connect in Settings > Integrations. More in Calibre and KOReader.
”Enter an HTTP or HTTPS catalog address without a username or password in the address.”
Type the catalog address on its own, starting with http:// or https://. Put the username and password in their own fields.
”This address did not return a supported ebook catalog.”
The address works, but there’s no ebook catalog at it. Check the address and the server type you chose.
”The download is not a complete, supported EPUB.”
The ebook file came through broken or isn’t an EPUB. Try another copy of the book.
”Calibre-Web cannot save reading positions.”
Plain Calibre-Web has no way to store your place. Your place stays on this device. Calibre-Web Automated with KOReader sync turned on can save it.
”This Calibre account is read-only, so Calibre cannot save the reading position.”
Your Calibre user is set to read-only, so your place can’t be saved there. Connect with a Calibre user that is allowed to make changes, or keep your place on the phone.
”KOReader sync is off on this server. An admin can turn it on in Calibre-Web Automated settings.”
A Calibre-Web Automated admin needs to turn on KOReader sync.
”Your place changed in BookOrbit. Open this ebook to choose where to continue.”
Your reading position changed on another device. Open the ebook and choose which place to keep. Your place on this phone has been kept.
”Another reading position needs attention. Open the ebook to choose your place.”
Two places for the same book don’t agree. Open the ebook and pick one.
SharePlay
More in SharePlay.
”Couldn’t find a matching copy in your library. Add the same book or episode to your server, then join again.”
Everyone in SharePlay plays their own copy, and you don’t have this one. Add the same book or episode to your server, then join again.
”More than one copy in your library matches this audio. SharePlay couldn’t choose one.”
More than one book or episode in your library matches, and SoundLeaf can’t tell which to play. Check for duplicates in Audiobookshelf before you remove anything, then join again.
”SharePlay couldn’t start. Check your FaceTime call, then try again.”
SharePlay needs a FaceTime call. Make sure the call is connected, then try again.
Links, NFC tags and QR codes
More in NFC tags and QR codes.
”This link needs a newer version of SoundLeaf. Update the app and scan it again.”
The tag or code was made with a newer SoundLeaf. Update the app from the App Store.
”Add the linked server in Settings and sign in. Personal links also require the account that created them.”
The link points at a server you haven’t added on this phone. Add it and sign in. A personal link also needs the account that made it.
”No matching playable episode is saved for this podcast.”
The link wants an episode you don’t have ready to play. Download or refresh the podcast, then try again.
”This link needs X bytes, but the tag holds Y. Try a larger tag or remove the sleep timer.”
The link doesn’t fit on that NFC tag. Use a tag with more room, or make the link shorter by leaving out the sleep timer.
Apple Watch
More in Apple Watch.
”Phone out of reach”
The watch can’t talk to your phone right now. Keep the phone nearby, or play something downloaded to the watch.
”Watch download failed, tap to send again”
The book or episode didn’t make it to the watch. Tap the row to send it again.
”Not currently connected · last updated”
This is on the phone, in Settings > Apple Watch. The watch isn’t talking to the phone right now. That’s often because the watch app is closed, and it’s not a problem on its own. The time says when the watch last checked in.
Purchases
More in Pro and Supporter.
”Purchase could not be completed. Please try again.”
The App Store didn’t finish the purchase. Check you’re connected and signed in to the App Store, then try again.
”Could not restore purchases. Please try again.”
SoundLeaf couldn’t restore your purchases. Make sure you’re signed in with the same Apple Account you bought with, then tap Restore Purchases again.