There’s no conflict regarding ports. Each container can have the same ports open. You’re thinking about the host network here, but it’s not the case.
Comment on set up local DNS using Pi-hole + nginx + audiobookshelf
Malasaur@sh.itjust.works 5 days ago
I’m pretty sure you have to specify a different port. Audiobookshelf uses port 80 by default - which is already taken by NPM - and since you’re not mapping it to any other port those services will conflict.
Map the port to something easy to remember in the compose file. Not only is it required in your setup but it is good practice. If you have to manage a lot of services, it is hard to keep track of all the ports they use if you keep them on their default values. I personally chose a port range (like 12300 -> 12399) and map all of my services respectively (Komodo to 12300, Authentik to 12301, etc.).
Also remember to update the port in your NPM config.
TL;DR: Audiobookshelf’s default port is 80, which conflicts with NPM. Change it.
clmbmb@lemmy.dbzer0.com 5 days ago
happeningtofry99158@lemmy.world 5 days ago
thank 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.
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.
MysteriousSophon21@lemmy.world 4 days ago
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.happeningtofry99158@lemmy.world 4 days ago
thank you! this works!
BigDogDave@lemmy.world 5 days ago
If the port isn’t being explicitly exposed then it won’t expose by default. I have my containers set up in a similar way where nginx has it’s own network and I attach any containers I want to proxy to the same network. On most cases I’m able to remove the ports section from config and point nginx at the name of the container, and the container’s default http port. The way OP originally configured this should be fine IF nginx and audiobookshelf are on the same docker network.
Malasaur@sh.itjust.works 5 days ago
I honestly didn’t know that. I personally just configure a specific port for each stack and have NPM forward it directly without configuring any network.
I just noticed OP did configure a network, but tbh I don’t know how they work exactly and gave recommendations on what I knew.
If using networks is the standard way or OP feels better off that way then I’ll leave them to it