In the compose file for Audiobookshelf, you need to add the service itself to the network you defined at the bottom. Something like:
services:
audiobookshelf:
...
networks:
- default
- nginx
(The default network is to keep it in the network that is created on docker compose up).
I’ve been there, I used the “encrypted partition to be unlocked after boot via SSH”-option, but it quickly became tedious to have to input the password every time it rebooted. I wanted something that could recover by itself (I.e. start everything up again after a potential crash), so that I could maximize uptime and the investigate the crash later.
So I ended up disabling encryption. What I did instead was to find services with E2EE for my most sensitive stuff. Joplin for my personal notes is currently the only thing I have encrypted. Nextcloud has experimental E2EE, though I’m not really using it as of right now. Everything I deem too sensitive to trust my server with unencrypted, I store on encrypted flash drives.
I think the risk of the server itself being compromised/hacked is bigger than physical theft (at least in my case), and if you take some good precautionary measures, even that risk is pretty small unless you’re being directly targeted by a skilled adversary. If the latter is the case, don’t store sensitive stuff on something with an IP address.
Before you know it VPNs are gonna be subject to age verification.
Make your own VPN on a VP… Oh, VPS providers are gonna be subject to age verification eventually. Not a permanent solution either.
Tor seems to be the only resilient solution tbh.