Dash. integration
Hi there. Was trying to integrate dash. on my raspberry pi (which is accessible through http://rpi.local:8001) and dash wasn't connecting until I changed it to my rpi local IP address. Is it a case of misconfiguration or does dash/homarr integration not support that "domain" and needs to be ip address?
I'm pretty new to self hosting so its likely to be something stupid on my part
39 Replies
Hi 👋,
do you use a reverse proxy for Dash.?
ahh since you answered on the other channel the thing about ping it might be the same thing actually
im not using a reverse proxy no
just using my raspberry pi hostname (rpi.local) followed by ports
i guess ping is having the same issue with it being unreachable, since dash. is reachable with an IP address instead of rpi.local:8001
Do you use a local DNS that points to the IP of Dash.?
wait i confused that, hold on lol
portainer is on https://rpi.local:9443 and is unreachable
dash. is on http://192.168.0.90:8001 and is reachable
dash. doesnt work with rpi.local:8001
and portainer doesnt ping with rpi.local:9443
so I'm guessing its something to do with hostname?
Can you try to use the local IP instead? You can still override using the on click url so it open the hostname when you click
yeap that worked on portainer
i guess i was trying to use hostname in case the IP changes
for complicated reasons I can't assign a static IP on my router
The ping can be a bit flaky with hostnames. The simplest solution is to use the IP instead - it's probably not your fault, that the ping didn't work with the hostname
yeah dash didnt work either. but I guess I can always try to keep the raspberry pi on the same IP without using the router for that
Sure, that's a possibility
@ajnart can you maybe investigate, why the ping does not work with hostnames? I feel like this should be working, as direct IPs have some disadvantages over hostnames
It never worked
Apparently nextjs doesn't support it
Don't we use axios?
https://github.com/ajnart/homarr/blob/dev/src/pages/api/modules/ping.ts
No we but still i think it's not supported
Or is it ?
I looked into it and found only very vague answers
my dash doesnt load
The same as before: Please give us some basic information. We can't help you with only this screenshot.
- Open the console and look for errors
- Show us your configuration for Dash.
- Explain what you did
yes i am getting it
services:
dash:
image: mauricenino/dashdot:latest
restart: unless-stopped
privileged: true
ports:
- '8765:3001'
volumes:
- /:/mnt/host:roI mean it's pulling data but doesn't display anything. That's strange
nginx problem?\
Most likely. Not sure how I can help but you have to enable iframes somehow
Our documentation even says how:
https://homarr.dev/docs/widgets/dashdot-widget#reverse-proxy-configuration
📟 Dash. | Homarr Docs
The Dash. widget will integrate your existing Dash. instance into Homarr. The graphs will be integrated using iframe.
how
confused
this is my nginx conf for homarr
location / {
#rewrite ^/panel/(.*) /$1 break;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Origin "";
proxy_pass http://127.0.0.1:7575;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}
Not Homarr. You need to allow iframes for your Dash., since we embed them using Iframes
can you help me on how to enable them in nginx
LetMeGoogleThat.com
Let Me Google That
For all those people that find it more convenient to bother you with their question than to google it for themselves.
This link also mentions everything you need to know 🙂
it tells me xframes
are they same?
What do you mean? Our documentation mentions the same as the other link. You just need to add that header and it should work
oh yes
i saw
i added this
location / {
#rewrite ^/panel/(.*) /$1 break;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Origin "";
add_header X-Frame-Options SAMEORIGIN always;
proxy_pass http://127.0.0.1:7575;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}
stil doesnt work out
need more research ig
umm
You can't downgrade your connection to HTTP, if you access Homarr via HTTPS. You should access Dash. with HTTPS too
okhei
new tip
do i need to expose internal dashdot port?
or add /api to nginx?
anyone?
@ajnart , any idea?
none
sad
but dash on port 3001 works fine
i exposed it
it shows everything correctly
Can you check for errors in the log of Homarr?
ok sure