You’re missing the networks section in your audiobookshelf service definition - add networks: [nginx] to your audiobookshelf service to actually connect it to the network (just defining the network at the bottom doesn’t automatically attach your service to it, which is why npm can’t reach it and gives you that 502 error), and if you’re an audiobook fan you might wanna check out the soundleaf app for ios which works great with audiobookshelf.
Comment on set up local DNS using Pi-hole + nginx + audiobookshelf
happeningtofry99158@lemmy.world 5 days agothank you!
I have added
ports: - 13378:80
in audiobookshelf docker compose and changed npm settings
But it still gives me the same 502 Bad Gateway error.
MysteriousSophon21@lemmy.world 5 days ago
happeningtofry99158@lemmy.world 4 days ago
thank you! this works!
Malasaur@sh.itjust.works 5 days ago
I’ve just noticed: you’ve set your forward hostname/IP to
audiobookshelf. That should either be your PC’s IP address (if you’ve set up a static one in your router’s panel) or its hostname. Unless you’ve named your PCaudiobookshelfit still won’t work.clmbmb@lemmy.dbzer0.com 5 days ago
This is about addressing the containers in docker. It has nothing to do with the local network.