nginx-proxy path based routing gives 404 error for application assets

[paulheil]

I'm attempting to use the path based routing feature of nginxproxy/nginx-proxy to host dozzle at http://media.local/dozzle/.

version: "3"

services:
  nginx-proxy:
    image: nginxproxy/nginx-proxy
    restart: always
    ports:
      - "80:80"
    volumes:
      - "/var/run/docker.sock:/tmp/docker.sock:ro"
      - "./nginx/vhost.d:/etc/nginx/vhost.d"

  dozzle:
    container_name: dozzle
    image: amir20/dozzle:latest
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    restart: unless-stopped
    environment:
      - VIRTUAL_HOST=media.local
      - VIRTUAL_PATH=/dozzle/
      - VIRTUAL_PORT=8080

When I load http://media.local/dozzle/ in chrome, I get a blank page with the dozzle favicon. The chrome dev tools report

/dozzle/:15     GET http://media.local/assets/main-aeb02c57.css net::ERR_ABORTED 404 (Not Found)
/dozzle/:16     GET http://media.local/assets/main-299e3767.js net::ERR_ABORTED 404 (Not Found)

obviously, I want the browser to request http://media.local/dozzle/assets/main-aeb02c57.css instead

I've tried this with services other than dozzle and the result is the same, so I do not think this is a dozzle-specific issue. How can I get the path based routing to include all of the application assets?

[SchoNie]

You also have to let Dozzle know the adjusted base path.
changing-base-url in Dozzle docs.

See also the environment variables where it shows the --base as environment for your use in docker compose.

[paulheil]

You're right and that does work for the specific Dozzle container. Thank you

I'm a bit disappointed though - does that mean there won't be a generic solution to this? I'll need to find some variable or setting like that for every application I want to host and if there isn't a setting, then nginx-proxy just won't work for it?

[SchoNie]

Most applications give you options to specify some kind of basedir, root or domain.
You have another example application giving issues?

Personally I mostly use subdomains instead of paths (dozzle.domain.tld).
Then an app listening on / will work.

[paulheil]

I was successful with Dozzle, Portainer, and ESPHome. But, I haven't yet found a way to get homeassistant/home-assistant to work with a different base url directory.

Subdomains is probably a better solution. I thought mDNS would be simpler (no need to purchase a domain or set up a DNS on my local network) and I didn't see a way to get subdomains using mDNS. I could also make subdomains work by editing the hosts file on every pc I have, but that seems like a pain.