Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Dozzle 404 error #149

Open
mifbody opened this issue Mar 31, 2021 · 4 comments
Open

Dozzle 404 error #149

mifbody opened this issue Mar 31, 2021 · 4 comments

Comments

@mifbody
Copy link

mifbody commented Mar 31, 2021 •
edited
Loading

Hi there - hoping this is OK to submit as an issue. I copied your Dozzle docker-compose but I'm getting the 404 error message when I try to access my dozzle.(my domain) -- I'm not sure what I should do to troubleshoot. If I add the default network and define a port I can access it under my docker host's IP address, but I can't access through dozzle.(my domain) -- any ideas for troubleshooting?

  # Dozzle - Real-time Docker Log Viewer
  dozzle:
    image: amir20/dozzle:latest
    container_name: dozzle
    restart: unless-stopped
    networks:
      - t2_proxy
      - socket_proxy
#      - default
    depends_on:
      - socket-proxy
    security_opt:
      - no-new-privileges:true
#    ports:
#      - "9999:8080"
    environment:
      DOZZLE_LEVEL: info
      DOZZLE_TAILSIZE: 300
      DOZZLE_FILTER: "status=running"
      # DOZZLE_FILTER: "label=log_me" # limits logs displayed to containers with this label
      DOCKER_HOST: tcp://socket-proxy:2375
    # volumes:
    #  - /var/run/docker.sock:/var/run/docker.sock # Use Docker Socket Proxy instead for improved security
    labels:
      - "traefik.enable=true"
      ## HTTP Routers
      - "traefik.http.routers.dozzle-rtr.entrypoints=https"
      - "traefik.http.routers.dozzle-rtr.rule=Host(`dozzle.$DOMAINNAME0`)"
      ## Middlewares
      - "traefik.http.routers.dozzle-rtr.middlewares=chain-oauth@file"
      ## HTTP Services
      - "traefik.http.routers.dozzle-rtr.service=dozzle-svc"
      - "traefik.http.services.dozzle-svc.loadbalancer.server.port=8080"
@mifbody
Copy link
Author

mifbody commented Apr 1, 2021 •
edited
Loading

Got it working! I ended up copying all the labels from my working portainer section and it looks like the missing piece was the line about using TLS. Once I added that Dozzle works as intended.

  # Dozzle - Real-time Docker Log Viewer
  dozzle:
    image: amir20/dozzle:latest
    container_name: dozzle
    restart: unless-stopped
    networks:
      - t2_proxy
      - socket_proxy
#      - default
    depends_on:
      - socket-proxy
    security_opt:
      - no-new-privileges:true
#    ports:
#      - "9999:8080"
    environment:
      DOZZLE_LEVEL: info
      DOZZLE_TAILSIZE: 300
      DOZZLE_FILTER: "status=running"
      # DOZZLE_FILTER: "label=log_me" # limits logs displayed to containers with this label
      DOCKER_HOST: tcp://socket-proxy:2375
    # volumes:
    #  - /var/run/docker.sock:/var/run/docker.sock # Use Docker Socket Proxy instead for improved security
    labels:
      - "traefik.enable=true"
      ## HTTP Routers
      - "traefik.http.routers.dozzle-rtr.entrypoints=https"
      - "traefik.http.routers.dozzle-rtr.rule=Host(`dozzle.$DOMAINNAME`)"
      - "traefik.http.routers.dozzle-rtr.tls=true"
      ## Middlewares=
      - "traefik.http.routers.dozzle-rtr.middlewares=chain-oauth@file" # Google OAuth 2.0
      ## HTTP Services
      - "traefik.http.routers.dozzle-rtr.service=dozzle-svc"
      - "traefik.http.services.dozzle-svc.loadbalancer.server.port=8080"

@proddy
Copy link

proddy commented Apr 15, 2021

do you have a --entrypoints.https.http.tls.certresolver=dns-cloudflare in your traefik config?

@mifbody
Copy link
Author

mifbody commented Apr 15, 2021

No sir - I don't see that anywhere in the tutorial document -- https://www.smarthomebeginner.com/traefik-2-docker-tutorial/

@proddy
Copy link

proddy commented Apr 17, 2021

the doc is a little out of date with the latest changes. I think if you add this, you don't need to go and add "routers.<>.tls=true" everywhere. not 100% sure though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@proddy @mifbody