Originally created by @swedishstyle on GitHub (Dec 23, 2023).
Steps to reproduce
Attempt to connect to audiobookshelf server that was working yesterday
??
Expected behaviour
I should be able to connect
Actual behaviour
"Failed to contact server (Error: java.security.cert.CertPathValidatorExeption)
Trust anchor for certification path not found
Note: This only occurs when attempting to connect to the server via a reverse proxy address behind NGINX. This worked as of yesterday, and no updates to the server have been made since then. I can still access it without issue on the web using the reverse proxy.
Environment data
Audiobookshelf Version:
[ X] Android App?
iOS App?
Android Issue
Android version: 0.9.70-beta
Device model:
Samsung S20FE
Stock or customized system:
Stock
iOS Issue
iOS Version:
N/A
iPhone model:
N/A
Originally created by @swedishstyle on GitHub (Dec 23, 2023).
### Steps to reproduce
1. Attempt to connect to audiobookshelf server that was working yesterday
2. ??
### Expected behaviour
- I should be able to connect
### Actual behaviour
- "Failed to contact server (Error: java.security.cert.CertPathValidatorExeption)
Trust anchor for certification path not found
Note: This only occurs when attempting to connect to the server via a reverse proxy address behind NGINX. This worked as of yesterday, and no updates to the server have been made since then. I can still access it without issue on the web using the reverse proxy.
### Environment data
Audiobookshelf Version:
- [ X] Android App?
- [ ] iOS App?
#### Android Issue
Android version: 0.9.70-beta
Device model:
Samsung S20FE
Stock or customized system:
Stock
#### iOS Issue
iOS Version:
N/A
iPhone model:
N/A
adam
added the bug label 2026-04-24 23:38:55 +02:00
Something went wrong with your reverse proxy. You can try using a SSL checking service like SSL Labs to see if there is an underlying issue with your setup / RP
@DieselTech commented on GitHub (Dec 23, 2023):
Something went wrong with your reverse proxy. You can try using a SSL checking service like SSL Labs to see if there is an underlying issue with your setup / RP
https://www.ssllabs.com/ssltest/index.html
Something went wrong with your reverse proxy. You can try using a SSL checking service like SSL Labs to see if there is an underlying issue with your setup / RP
I'm not sure where to look exactly, but nothing jumps out as obviously wrong for my proxy site. If you can tell me which section I should look at, I'd be happy to check it out
@swedishstyle commented on GitHub (Dec 23, 2023):
> Something went wrong with your reverse proxy. You can try using a SSL checking service like SSL Labs to see if there is an underlying issue with your setup / RP
>
> https://www.ssllabs.com/ssltest/index.html

I'm not sure where to look exactly, but nothing jumps out as obviously wrong for my proxy site. If you can tell me which section I should look at, I'd be happy to check it out
Unfortunately I have the same problem. SSL works without any problems in the browser, but in the application it throws the same error.
@dziurka commented on GitHub (Dec 28, 2023):
Unfortunately I have the same problem. SSL works without any problems in the browser, but in the application it throws the same error.
I just encountered this issue myself. I would get this error on the android app, but in Firefox it worked fine. The server is behind an nginx reverse proxy, with a certificate from Let's Encrypt. I believe this was caused by missing intermediate certificates (AFAIK Firefox has its own certificate store, so would not necessarily need to have the intermediate certificates provided by nginx).
I solved my issue by changing the ssl certificate directive in nginx from just cert.pem to fullchain.pem.
@ociaw commented on GitHub (Feb 6, 2024):
I just encountered this issue myself. I would get this error on the android app, but in Firefox it worked fine. The server is behind an nginx reverse proxy, with a certificate from Let's Encrypt. I believe this was caused by missing intermediate certificates (AFAIK Firefox has its own certificate store, so would not necessarily need to have the intermediate certificates provided by nginx).
I solved my issue by changing the `ssl certificate` directive in nginx from just `cert.pem` to `fullchain.pem`.
Oh apologies, yes it was a misconfiguration on my end! Bloody DNS :)
What was the solution? I'm suddenly having problems with the Android client with this error and as far as I know nothing changed.
@pjones112000 commented on GitHub (Apr 8, 2026):
> Oh apologies, yes it was a misconfiguration on my end! Bloody DNS :)
What was the solution? I'm suddenly having problems with the Android client with this error and as far as I know nothing changed.
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 @swedishstyle on GitHub (Dec 23, 2023).
Steps to reproduce
Expected behaviour
Actual behaviour
Trust anchor for certification path not found
Note: This only occurs when attempting to connect to the server via a reverse proxy address behind NGINX. This worked as of yesterday, and no updates to the server have been made since then. I can still access it without issue on the web using the reverse proxy.
Environment data
Audiobookshelf Version:
Android Issue
Android version: 0.9.70-beta
Device model:
Samsung S20FE
Stock or customized system:
Stock
iOS Issue
iOS Version:
N/A
iPhone model:
N/A
@DieselTech commented on GitHub (Dec 23, 2023):
Something went wrong with your reverse proxy. You can try using a SSL checking service like SSL Labs to see if there is an underlying issue with your setup / RP
https://www.ssllabs.com/ssltest/index.html
@swedishstyle commented on GitHub (Dec 23, 2023):
I'm not sure where to look exactly, but nothing jumps out as obviously wrong for my proxy site. If you can tell me which section I should look at, I'd be happy to check it out
@dziurka commented on GitHub (Dec 28, 2023):
Unfortunately I have the same problem. SSL works without any problems in the browser, but in the application it throws the same error.
@advplyr commented on GitHub (Jan 29, 2024):
Is this resolved? I'm not sure how this is a bug with Abs
@swedishstyle commented on GitHub (Jan 29, 2024):
Oh apologies, yes it was a misconfiguration on my end! Bloody DNS :)
@ociaw commented on GitHub (Feb 6, 2024):
I just encountered this issue myself. I would get this error on the android app, but in Firefox it worked fine. The server is behind an nginx reverse proxy, with a certificate from Let's Encrypt. I believe this was caused by missing intermediate certificates (AFAIK Firefox has its own certificate store, so would not necessarily need to have the intermediate certificates provided by nginx).
I solved my issue by changing the
ssl certificatedirective in nginx from justcert.pemtofullchain.pem.@pjones112000 commented on GitHub (Apr 8, 2026):
What was the solution? I'm suddenly having problems with the Android client with this error and as far as I know nothing changed.