I'm trying to set up local DNS using Pi-hole.

I have successfully set up Pi-hole and added a local DNS record local.com, pointing it to the server running the Pi-hole container 192.168.0.101.

Then I set up the Audiobookshelf container using the guide from Audiobookshelf, where I set up Nginx Proxy Manager with the following compose file:

services:
  nginx-proxy-manager:
    image: docker.io/jc21/nginx-proxy-manager:latest
    container_name: nginx-proxy-manager
    ports:
      - 80:80
      - 443:443
      - 81:81
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
    restart: unless-stopped

And Audiobookshelf with the following compose file:

services:
  audiobookshelf:
    image: ghcr.io/advplyr/audiobookshelf:latest
    container_name: audiobookshelf
    volumes:
      - ./audiobooks:/audiobooks
      - ./podcasts:/podcasts
      - ./metadata:/metadata
      - ./config:/config
    restart: unless-stopped
networks:
  nginx:
    name: nginx-proxy-manager_default
    external: true

I did not specify a port, hoping that Nginx could manage it.

Then I set up Nginx Proxy Manager following the guide from Audiobookshelf by adding a proxy host. Trying to resolve audiobookshelf.local.com to I simply followed the guide and wasn’t sure why the “Forward Hostname / IP” should be the container name audiobookshelf.

I also created a self-signed certificate.

But I cannot access https://audiobookshelf.local.com/ or http://audiobookshelf.local.com/ (it automatically forwards to HTTPS).


I tried adding a local DNS record:
audiobookshelf.local.com → 192.168.0.101 in Pi-hole.
Now, when I access audiobookshelf.local.com, the site shows:
502 Bad Gateway – openresty


I think the problem lies in the Docker network setup. I suspect the Audiobookshelf Docker container is not communicating with Nginx.


Would appreciate any help!

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 year ago* (2 children)

Just to make sure, your issue is :

But I cannot access https://audiobookshelf.local.com/ or http://audiobookshelf.local.com/ (it automatically forwards to HTTPS).

If so, well, you're forcing SSL, which means it'll automatically transmit http request to https. If you don't want that, turn it off. Anyway, it's going to be used only locally, correct?

  • source
  • hideshow 2 child comments
  • [–] [S] 3 points 1 year ago (1 child)

    I have turned it off and tried again, this time it allows me to go to http://audiobookshelf.local.com/, however still giving me the 502 Bad Gateway error.

    Anyway, it’s going to be used only locally, correct?

    yes that's correct. But I still want to use self signed certificate just for extra security and get to know how to successfully configure it.

  • source
  • parent
  • hideshow 1 child comment