Homarr•2mo ago

Pings and integrations through reverse proxy failing

I recently (today) migrated from using a jail running docker on truenas scale to native docker with dockge. Same compose file, same paths, same everything except for which docker engine is running and which IP it's bound to. All of my other apps seem to be fine, but homarr absolutely refuses to successfully ping anything that's going through my reverse proxy. Apps like notifiarr that are monitoring some of the same services work fine also. I've managed to reconfigure those that I can to use the internal docker network hostname and port, but that's not an option for everything. Additionally, I can shell into the homarr container, install curl, and run curl https://sonarr.xx.cx and get the proper response. Also interestingly, OIDC won't work either (it times out) -- but it does work in my v1 testing container (but pings don't work there either). Get the below for example

homarr  |  ERROR  Ping timed out for app with id '88fa977f-886e-4458-a038-f6aeaa56b687' in config 'default' -> url: https://sonarr.xxx.cx)

homarr  |  ERROR  Ping timed out for app with id '88fa977f-886e-4458-a038-f6aeaa56b687' in config 'default' -> url: https://sonarr.xxx.cx)

Solution:

OK, I think I figured it out 1) OIDC -- Had to remove trailing slash, not sure why that was a new problem 2) Pings-- IT WAS DNS... I have two pihole DNS servers, and previously the first one was in a seperate docker instance, moving everything into the second docker instance caused DNS resolution delays when it uses the one on the same docker instance. Swapping to the other external DNS server fixed the resolution issues. (as configured on Truenas scale network configuration)....

Jump to solution

5 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?

KrispyOP•2mo ago

Logs attached OS: TrueNAS SCALE ElectricEel-24.10.0.2 Homarr: ghcr.io/ajnart/homarr:0.15.7 Reverse proxy is caddy (everything else here seems to work as I said)

homarr_logs.txt

KrispyOP•2mo ago

Compose file (sanitized):

 version: "3"
#---------------------------------------------------------------------#
#     Homarr - A simple, yet powerful dashboard for your server.      #
#---------------------------------------------------------------------#
services:
  homarr:
    container_name: homarr
    image: ghcr.io/ajnart/homarr:0.15.7
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - /mnt/data/homearr/config:/app/data/configs
      - /mnt/data/homearr/icons:/app/public/icons
      - /mnt/data/homearr/data:/data
      #    ports:
      #      - '7575:7575'
    environment:
      AUTH_PROVIDER: credentials
      #AUTH_PROVIDER: oidc
      AUTH_OIDC_URI: https://auth.domain.cx/application/o/homarr/
      BASE_URL: homepage.domain.cx
      AUTH_OIDC_CLIENT_ID: CLIENT_ID
      AUTH_OIDC_CLIENT_SECRET: SECRET
      AUTH_OIDC_CLIENT_NAME: homarr
      AUTH_OIDC_ADMIN_GROUP: homarr_admin
      AUTH_OIDC_OWNER_GROUP: homarr_owner
      AUTH_OIDC_AUTO_LOGIN: false
      NEXTAUTH_URL: https://homepage.domain.cx
    networks:
      - caddy
    labels:
      - com.caddyserver.http.enable=true
      - com.caddyserver.http.network=caddy
      - com.caddyserver.http.upstream.port=7575
      - com.caddyserver.http.matchers.host=homepage.domain.cx
      - wud.tag.include=^\d+\.\d+\.\d+$$
networks:
  caddy:
    external: true
x-dockge:
  urls:
    - https://homepage.domain.cx

 version: "3"
#---------------------------------------------------------------------#
#     Homarr - A simple, yet powerful dashboard for your server.      #
#---------------------------------------------------------------------#
services:
  homarr:
    container_name: homarr
    image: ghcr.io/ajnart/homarr:0.15.7
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - /mnt/data/homearr/config:/app/data/configs
      - /mnt/data/homearr/icons:/app/public/icons
      - /mnt/data/homearr/data:/data
      #    ports:
      #      - '7575:7575'
    environment:
      AUTH_PROVIDER: credentials
      #AUTH_PROVIDER: oidc
      AUTH_OIDC_URI: https://auth.domain.cx/application/o/homarr/
      BASE_URL: homepage.domain.cx
      AUTH_OIDC_CLIENT_ID: CLIENT_ID
      AUTH_OIDC_CLIENT_SECRET: SECRET
      AUTH_OIDC_CLIENT_NAME: homarr
      AUTH_OIDC_ADMIN_GROUP: homarr_admin
      AUTH_OIDC_OWNER_GROUP: homarr_owner
      AUTH_OIDC_AUTO_LOGIN: false
      NEXTAUTH_URL: https://homepage.domain.cx
    networks:
      - caddy
    labels:
      - com.caddyserver.http.enable=true
      - com.caddyserver.http.network=caddy
      - com.caddyserver.http.upstream.port=7575
      - com.caddyserver.http.matchers.host=homepage.domain.cx
      - wud.tag.include=^\d+\.\d+\.\d+$$
networks:
  caddy:
    external: true
x-dockge:
  urls:
    - https://homepage.domain.cx

Solution

Krispy•2mo ago

KrispyOP•2mo ago

Don't ask why it affected homarr and not notifarr

Gaming

Programming

Pings and integrations through reverse proxy failing