Dash. widget doesnt work when dash. is in docker or i am doing something wrong
.
29 Replies
i have dash. like this in my docker compose where i also have homarr:
setting it like this doesnt connect
setting it internally, does not embed the stats, cause that dns record for dash doesnt exist outside of docker network.
You should set it to the absolute IP address. Both Homarr and your browser must be able to connect
Your browser can't connect to localhost nor the internal docker hostname
why?
port is exposed
Because localhost means the local host. The client tries to connect to itself. Unless your running Homarr and Dash. on the same machine as your browser is, this won't work
Then just use the IP and port instead of localhost or the internal Docker hostname
yes, i am doing exactly that right now, but i will use a raspi later
it works with internal port(the connect), but then fails to embed
so it seems like, the connection is done on the backend and not in browser, and embed is done in browser only
which is very bad
which means its impossible to get this working
it would only work if i set a custom dash dns record
trying that out
No, it would also work if you used the IPv4.
But a custom DNS record will work as well
so
i was right
only works with dns
because
docker compose assigns a whole new network
and on that network
my ip is a lot different
and yes, ipv4 did not work
It should. Did you check the log?
this does not work
this does
as i said, your backend connects to the ip which is bad
No, it won't. Your client doesn't know this hostname
(after dns record)
adguard home
so, the problem is that your backend connects, and finds the ip from docker dns, but for browser to connect, it needs a custom dns record to work from its dns.
Backend doesnt connect with ipv4 because docker creates an isolated network for each docker compose setup which cant connect to local ips.
Browser could connect to that.
Backend:
- can connect to docker services.
- can't connect to local ipv4 because of network isolation
Frontend(Browser):
- can't connect to docker services
- can connect to local ipv4 because its on the router
Yes, that is true, if you use network isolation.
yes, docker compose does that by default.
just wanted to say that you should point that out
in docs if its not already
You can add it yourself:
https://github.com/ajnart/homarr-docs
GitHub
GitHub - ajnart/homarr-docs: The documentation of Homarr
The documentation of Homarr. Contribute to ajnart/homarr-docs development by creating an account on GitHub.
is this enough in installation?
Just create a pull request and we'll give feedback there
oh, and also, iframe is done correctly
that one doesnt wanna connect internally