Homarr•19h ago

Dash. Integration Not Working in Beta

I have 3 servers with Dash.. Server #1: Hosted on the same cloud server as the homarr dashboard. Using an iframe with the domain name works. Using nginx reverse proxy to forward the dash. container via a domain name. dashdot.somedomain.com Server #2: Hosted on a separate cloud server. Using an iframe with the domain name works. Using nginx reverse proxy to forward the dash. container via a domain name. dashdot.somedomain2.com Server #3: Hosted on a local server at my apartment. Using cloudflare tunnels to forward the dash. container via a domain name. dashdot-california.somedomain2.com I am currently away from my apartment (if you're wondering if my internet connection is the same as Server #3 it is not) Dash. works fine on Server #3, but produces the error in the photo on Servers #1 and #2.

13 Replies

Cakey Bot•19h 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?

beanbeanjuiceOP•19h ago

Exact homar version is "0.1.0"

beanbeanjuiceOP•19h ago

  beanbeanjuice-dashboard:
    container_name: beanbeanjuice-dashboard
    image: ghcr.io/homarr-labs/homarr:beta
    restart: unless-stopped
    volumes:
      - /home/beanbeanjuice/projects/homarr:/appdata
    networks:
      - nginx-network
      - default
    depends_on:
      - beanbeanjuice-dashdot

  beanbeanjuice-dashboard:
    container_name: beanbeanjuice-dashboard
    image: ghcr.io/homarr-labs/homarr:beta
    restart: unless-stopped
    volumes:
      - /home/beanbeanjuice/projects/homarr:/appdata
    networks:
      - nginx-network
      - default
    depends_on:
      - beanbeanjuice-dashdot

Using this YML produces the same result

  beanbeanjuice-dashboard:
    container_name: beanbeanjuice-dashboard
    image: ghcr.io/homarr-labs/homarr:beta
    restart: unless-stopped
    volumes:
      - /home/beanbeanjuice/projects/homarr:/appdata
    networks:
      - nginx-network
      # - default
    depends_on:
      - beanbeanjuice-dashdot

  beanbeanjuice-dashboard:
    container_name: beanbeanjuice-dashboard
    image: ghcr.io/homarr-labs/homarr:beta
    restart: unless-stopped
    volumes:
      - /home/beanbeanjuice/projects/homarr:/appdata
    networks:
      - nginx-network
      # - default
    depends_on:
      - beanbeanjuice-dashdot

beanbeanjuiceOP•19h ago

fixed this issue by doing this;

        location / {
                proxy_pass      http://beanbeanjuice-dashboard:7575/;
                #include                proxy_params;
                proxy_http_version      1.1;
                proxy_set_header        Upgrade $http_upgrade;
                proxy_set_header        Connection "Upgrade";
                proxy_set_header        Host $host;
        }

        location / {
                proxy_pass      http://beanbeanjuice-dashboard:7575/;
                #include                proxy_params;
                proxy_http_version      1.1;
                proxy_set_header        Upgrade $http_upgrade;
                proxy_set_header        Connection "Upgrade";
                proxy_set_header        Host $host;
        }

However, the issues above still persist

Serenaphic•19h ago

Hi, this is an issue with the old schema for dashdot that still requires it to give the temps for the CPU. The new version will take that into account. Is it possible that you have disabled the cpu temps handling in dashdot? reenabling that would solve the issue.

beanbeanjuiceOP•19h ago

Hey! I have this here as my configuration for Server #1 and Server #2 (everything is the same aside from the container name)

  beanbeanjuice-dashdot:
    container_name: beanbeanjuice-dashdot
    image: mauricenino/dashdot:latest
    restart: unless-stopped
    privileged: true
    volumes:
      - /:/mnt/host:ro
    environment:
      DASHDOT_ENABLE_CPU_TEMPS: 'true'
    networks:
      - nginx-network

  beanbeanjuice-dashdot:
    container_name: beanbeanjuice-dashdot
    image: mauricenino/dashdot:latest
    restart: unless-stopped
    privileged: true
    volumes:
      - /:/mnt/host:ro
    environment:
      DASHDOT_ENABLE_CPU_TEMPS: 'true'
    networks:
      - nginx-network

Server #3 has this configuration

services:
  dashdot:
    container_name: dashdot
    image: mauricenino/dashdot:latest
    restart: unless-stopped
    privileged: true
    volumes:
      - /:/mnt/host:ro
    environment:
      DASHDOT_ENABLE_CPU_TEMPS: 'true'
    networks:
      - cloudflare-network

networks:
  cloudflare-network:
    name: cloudflare-network
    external: true

services:
  dashdot:
    container_name: dashdot
    image: mauricenino/dashdot:latest
    restart: unless-stopped
    privileged: true
    volumes:
      - /:/mnt/host:ro
    environment:
      DASHDOT_ENABLE_CPU_TEMPS: 'true'
    networks:
      - cloudflare-network

networks:
  cloudflare-network:
    name: cloudflare-network
    external: true

It seems as though CPU temps is already enabled, i'll try disabling and seeing if that makes a difference Disabling fixed it! How odd... Nonetheless, CPU temps aren't super important for me but yeah I'm glad it's working now. If you need me to debug further to get CPU temps working please let me know!

Serenaphic•18h ago

wat So, as we can see in the 3rd screenshot, homarr is expecting to receive a "temp" value. receiving null or undefined would not work lemme check one thing

beanbeanjuiceOP•18h ago

It's weird, Server #3 (cloudflare tunnel) works without commenting out the environment variable.

Serenaphic•18h ago

Yeah so as mentioned here, temp is expected, not receiving one would end up in the error you get. What's strange is that when you disable it, it suddenly shows? something inverted in the logic on dashdot's side

beanbeanjuiceOP•18h ago

Yes, except it works fine regardless if its enabled/disabled for Server #3 which uses cloudflare tunnel

Serenaphic•18h ago

it shouldn't have anything to do with cloudflare though, it's just about your machine

Gaming

Programming

Dash. Integration Not Working in Beta