Homarr•2mo ago

Status check fails for services using caddy docker proxy

All of my services that use caddy docker proxy keep getting errors saying the ping failed and the operation was aborted. None of these services are exposed to the public. I'm just using a reverse proxy so I can go to "jellyfin.home" or "whoogle.home" for example, instead of IP:port.

Solution:

Yes, but the pings are within the docker network and probably don't know about caddy except you would define it as proxy (which is currently not possible). So if you have other services in the caddy network you should be able to just use http://<containerName>:<exposedPort>

Jump to solution

10 Replies

Cakey Bot•2mo ago

Thank you for submitting a support request. Depending on the volume of requests, our team should get in contact with you shortly.

⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)

Frequently Asked Questions | Homarr documentation

Can I install Homarr on a Raspberry Pi?

jenksOP•2mo ago

Homarr Version 1.36.1 Operating system: UGOS Docker compose:

services:
  homarr:
    container_name: homarr
    image: ghcr.io/homarr-labs/homarr:latest
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - ./homarr/appdata:/appdata
    networks:
      - caddy
    labels:
      caddy: http://dash.home
      caddy.reverse_proxy: "{{upstreams 7575}}"
    environment:
      - SECRET_ENCRYPTION_KEY=redacted
    # ports:
      # - '7575:7575'
networks:
  caddy:
    external: true

services:
  homarr:
    container_name: homarr
    image: ghcr.io/homarr-labs/homarr:latest
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - ./homarr/appdata:/appdata
    networks:
      - caddy
    labels:
      caddy: http://dash.home
      caddy.reverse_proxy: "{{upstreams 7575}}"
    environment:
      - SECRET_ENCRYPTION_KEY=redacted
    # ports:
      # - '7575:7575'
networks:
  caddy:
    external: true

Meierschlumpf•2mo ago

Pings are done from your homarr instance, so you'll need to use the internal names like http://homarr:7575

jenksOP•2mo ago

When using the caddy reverse proxy, IP:port doesn't work anymore, the only way I can access the services are via the new address like "dash.home" in the example above

Meierschlumpf•2mo ago

But they are all internally accessible within this network, no?

jenksOP•2mo ago

Yeah everything is internally accessible, it’s just that they’re only accessible via that address. Prior to using caddy I would access jellyfin at localipaddress:port, but now I go to jellyfin.home, for example. And ipaddress:port doesn’t work anymore But jellyfin.home works just fine, so long as I’m on my home network (or on tailscale)

Solution

Meierschlumpf•2mo ago

jenksOP•2mo ago

Ohhh I misunderstood. Yes that worked!

Meierschlumpf•2mo ago

Okay nice 😄

jenksOP•2mo ago

I'm using the "Use different URL for ping" feature, works great Thank you, you can mark as solved 🙂

Gaming

Programming

Status check fails for services using caddy docker proxy

Did you find this page helpful?