I get this error message when I attempt to connect to my audio bookshelf using a cloud flared tunnel and my own domain. It works fine if I try to access my ABS server from my home network using an IP address. So I know it has something to do with the way I'm accessing it via the cloud flare tunnel. Couldn't have something to do with it being HTTPS? I also posted on discord under the general troubleshooting. Incidentally there is another client app out there for ABS called Lessin. It exhibits the same behavior however it doesn't give me an error message it simply won't connect.
Failed to contact server. (Error:
A java.security.cert.CertPathValidatorExceptior
Trust anchor for certification path not found.
Steps to Reproduce the Issue
Launch the application put in my cloud flared tunnel with domain address. Doesn't connect. Put in my IP address for ABS and it works.
What was Expected?
I just expected it to connect as normal.
Phone Model
Samsung Galaxy s 22 ultra
Phone OS
Android 15
Audiobookshelf App Version
Android App - 0.10.1
Installation Source
Google Play Store
Additional Notes
No response
Originally created by @trsmith78 on GitHub (Oct 27, 2025).
### I have verified that the [bug is not already awaiting release](https://github.com/advplyr/audiobookshelf-app/issues?q=is%3Aissue%20label%3A%22awaiting%20release%22)
Yes
### What was the Problem?
I get this error message when I attempt to connect to my audio bookshelf using a cloud flared tunnel and my own domain. It works fine if I try to access my ABS server from my home network using an IP address. So I know it has something to do with the way I'm accessing it via the cloud flare tunnel. Couldn't have something to do with it being HTTPS? I also posted on discord under the general troubleshooting. Incidentally there is another client app out there for ABS called Lessin. It exhibits the same behavior however it doesn't give me an error message it simply won't connect.
Failed to contact server. (Error:
A java.security.cert.CertPathValidatorExceptior
Trust anchor for certification path not found.
### Steps to Reproduce the Issue
Launch the application put in my cloud flared tunnel with domain address. Doesn't connect. Put in my IP address for ABS and it works.
### What was Expected?
I just expected it to connect as normal.
### Phone Model
Samsung Galaxy s 22 ultra
### Phone OS
Android 15
### Audiobookshelf App Version
Android App - 0.10.1
### Installation Source
Google Play Store
### Additional Notes
_No response_
adam
added the bug label 2026-04-24 23:56:44 +02:00
I have the same issue, so subscribing to this issue. FWIW, I was able to log in via my custom domain over http, which I am using as a workaround for the time being (ditto for Lissen by the way).
@appel commented on GitHub (Nov 2, 2025):
I have the same issue, so subscribing to this issue. FWIW, I was able to log in via my custom domain over http, which I am using as a workaround for the time being (ditto for [Lissen](https://play.google.com/store/apps/details?id=org.grakovne.lissen) by the way).
The developer over at Lissen has found the issue and is releasing a fix for Lissen.
Here is what he came up with and said. If it helps someone great just thought I'd share
"— this behavior comes from how Cloudflare’s tunnel presents the certificate chain. The intermediate certificate is fine, but the root CA isn’t included in the response, so Android’s default SSL stack can’t complete the validation. Browsers like Chrome can, because they maintain their own internal CA store and automatically rebuild the chain.
The new option (“Ignore SSL errors”) lets the app connect even in that situation — it’s still an HTTPS connection, fully encrypted, but the certificate validity isn’t verified. In other words, the traffic remains encrypted, but the app won’t try to prove that the server is who it claims to be.
And yes, this is likely the same reason other Android apps fail with Cloudflared tunnels — it’s not specific to Audiobookshelf or to your setup, but a general SSL chain issue with Cloudflare’s tunnel configuration.
The feature is already implemented, and I’ll publish an update to Google Play shortly — once it’s live, you’ll see the toggle under Advanced Preferences → SSL settings."
@trsmith78 commented on GitHub (Nov 3, 2025):
The developer over at Lissen has found the issue and is releasing a fix for Lissen.
Here is what he came up with and said. If it helps someone great just thought I'd share
"— this behavior comes from how Cloudflare’s tunnel presents the certificate chain. The intermediate certificate is fine, but the root CA isn’t included in the response, so Android’s default SSL stack can’t complete the validation. Browsers like Chrome can, because they maintain their own internal CA store and automatically rebuild the chain.
The new option (“Ignore SSL errors”) lets the app connect even in that situation — it’s still an HTTPS connection, fully encrypted, but the certificate validity isn’t verified. In other words, the traffic remains encrypted, but the app won’t try to prove that the server is who it claims to be.
And yes, this is likely the same reason other Android apps fail with Cloudflared tunnels — it’s not specific to Audiobookshelf or to your setup, but a general SSL chain issue with Cloudflare’s tunnel configuration.
The feature is already implemented, and I’ll publish an update to Google Play shortly — once it’s live, you’ll see the toggle under Advanced Preferences → SSL settings."
The feature is already implemented, and I’ll publish an update to Google Play shortly — once it’s live, you’ll see the toggle under Advanced Preferences → SSL settings."
Thanks @trsmith78! Looks like the dev pushed the update to the Play store yesterday (Nov 2). Works like a charm.
@appel commented on GitHub (Nov 3, 2025):
> The feature is already implemented, and I’ll publish an update to Google Play shortly — once it’s live, you’ll see the toggle under Advanced Preferences → SSL settings."
Thanks @trsmith78! Looks like the dev pushed the update to the Play store yesterday (Nov 2). Works like a charm.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @trsmith78 on GitHub (Oct 27, 2025).
I have verified that the bug is not already awaiting release
Yes
What was the Problem?
I get this error message when I attempt to connect to my audio bookshelf using a cloud flared tunnel and my own domain. It works fine if I try to access my ABS server from my home network using an IP address. So I know it has something to do with the way I'm accessing it via the cloud flare tunnel. Couldn't have something to do with it being HTTPS? I also posted on discord under the general troubleshooting. Incidentally there is another client app out there for ABS called Lessin. It exhibits the same behavior however it doesn't give me an error message it simply won't connect.
Failed to contact server. (Error:
A java.security.cert.CertPathValidatorExceptior
Trust anchor for certification path not found.
Steps to Reproduce the Issue
Launch the application put in my cloud flared tunnel with domain address. Doesn't connect. Put in my IP address for ABS and it works.
What was Expected?
I just expected it to connect as normal.
Phone Model
Samsung Galaxy s 22 ultra
Phone OS
Android 15
Audiobookshelf App Version
Android App - 0.10.1
Installation Source
Google Play Store
Additional Notes
No response
@roger-pilot commented on GitHub (Nov 2, 2025):
I am experiencing the exact same problem while using cloudflare tunnel. The web UI works just fine.
@appel commented on GitHub (Nov 2, 2025):
I have the same issue, so subscribing to this issue. FWIW, I was able to log in via my custom domain over http, which I am using as a workaround for the time being (ditto for Lissen by the way).
@trsmith78 commented on GitHub (Nov 3, 2025):
The developer over at Lissen has found the issue and is releasing a fix for Lissen.
Here is what he came up with and said. If it helps someone great just thought I'd share
"— this behavior comes from how Cloudflare’s tunnel presents the certificate chain. The intermediate certificate is fine, but the root CA isn’t included in the response, so Android’s default SSL stack can’t complete the validation. Browsers like Chrome can, because they maintain their own internal CA store and automatically rebuild the chain.
The new option (“Ignore SSL errors”) lets the app connect even in that situation — it’s still an HTTPS connection, fully encrypted, but the certificate validity isn’t verified. In other words, the traffic remains encrypted, but the app won’t try to prove that the server is who it claims to be.
And yes, this is likely the same reason other Android apps fail with Cloudflared tunnels — it’s not specific to Audiobookshelf or to your setup, but a general SSL chain issue with Cloudflare’s tunnel configuration.
The feature is already implemented, and I’ll publish an update to Google Play shortly — once it’s live, you’ll see the toggle under Advanced Preferences → SSL settings."
@appel commented on GitHub (Nov 3, 2025):
Thanks @trsmith78! Looks like the dev pushed the update to the Play store yesterday (Nov 2). Works like a charm.