Homarr can't connect to other local (docker hosted) servers. Dash. is not working either.
Hey folks, I've got the issue that I can't receive any information regards my other containers.
Dash. and Homarr are also in the same network.
The pings work on external websites (for example google.com)
The orange pings just say "waiting".
I assume that's the same reason why Homarr can't show any information from dash.
Any ideas there? The services are up and running.
55 Replies
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?
If it matters; I'm hosing on a Raspberry Pi 5 and use Portainer.
Hi, firstly make sure your homarr can communicate with the other services, you might need to configure a bridge.
Secondly, Dashdot is a clientside integration, so it's the browser that accesses it through an iframe, homarr backend does not interfere. You have to make sure that there's no protocol change (http to https) and that if you use https, your certificates are valid
due to the complexity of iframes though, this widget is currently not supported anymore. It is only provided for people to use to their own leisure, but we cannot offer help setting it up more than this
Dash. and Homarr are on the same network bridge and both run via HTTP
I see. Thank you though
Dashdot needs to be accessible using the provided address by your browser
Just to check; a regular iframe works.
Check your console, it may give you more info
It's strange but nothing much we can do.
If you do think it is a bug, you're always welcome to go ahead and contribute to the code to fix it, but as mentioned, this specific widget is getting deprecated
I guess it works like that via a regular iframe.
I'm quite new to docker and co. so it's most likely an issue caused by myself or Portainer I guess.
So I'm not good enough yet to fix anything there yet. 😄
Pro-tip, you're better of waiting for homarr V1, we'll have a real integration there that won't be buggy like that
Though any ideas why the other apps just show the orange dot saying "waiting..."?
Check your console and logs
Just wait 10 mintues for everything to load up
Could it be that it can't use the ports?
Firewall maybe
Has always been like that before
It's a timeout thing, you have to legit let the page load for 10 minutes and then check browser console logs
What is your docker network setup? Are you using just the IP addresses with ports or do you have a reverse proxy and use DNS?
Looks like hell haha, haven't done much thought about networks.
No reverse proxy and/or DNS.
Dash. is on the same network as Homarr though, so I'd assume it should work there at least.
I need to tidy that up. I'm aware of that. :V
So you are using IP:Port, right?
Jup.
Do you have UFW enabled on your server?
Nope, I don't. Where do I do that?
Or rather how?
Well if UFW is enabled, then it could cause an issue
Ah, okay. Thought otherwise because the U stands for uncomplicated after all. x)
If you want to check, go onto you machine and try replace port with the port that Dash uses
example sudo ufw allow 1234/tcp
I don't even have ufw on my device yet.
Can you check with ufw status?
I'd need to install ufw first.
Because the command's not getting found.
Got it
Can you ping from inside the container?
Yup, I can.
At least from dash. to homarr. Other way around doesn't work because "ping" was not found on the homarr volume.
wget instead
Okay, I get a connection refused!
I saw in your screenshot that the ip's were different groups too btw, not sure what that means
homarr is under 192, dash is under 172
Yeah, they're not anymore.
It's basically a virtual NIC.
Saw that one too and fixed it.
Why not host networking?
get them on the same ip, different ports
What's the difference?
Everything is the same network, which is the host
That way I can't access dash anymore because the connection refuses.
Maybe because the port it's trying to use is already occupied
It's not though. Using different ports on all services.
And the Ip should be the same one as homarr's
That shouldn't matter considering I go though server.local as name anyways?
Oh, you have a proxy
It's just the hostname. It reports to my router that it's name is server.local.
The routing within is probably done via Docker I guess?
The addresses displayed here are not internal addresses of the network but instead inside the virtual NIC.
The actual address of the device is 192.168.178.51
I wouldn't be able to connect to these addresses via my own PC.
Could also be something Portainer does.
I haven't set up a proxy.
Hi guys, just wanted to hook into the conversation as I am also having trouble connecting to my self hosted services using Homarr for some days now, previosly it worked fine. Funnily enough network devices as my printer get pinged properly.
They are all hooked up on the same standard network bridge.
Any clues on how to proceed?
This is the Docker Log, matches the Firefox log where a lot of timeouts are present
aaaaah fml, Marius saved the day again!
Homarr appearently does not like the Multiple Gateway Option present on DSM: https://kb.synology.com/en-nz/DSM/help/DSM/AdminCenter/connection_network_route?version=6
Network Routing | DSM - Synology Knowledge Center
Synology Knowledge Center offers comprehensive support, providing answers to frequently asked questions, troubleshooting steps, software tutorials, and all the technical documentation you may need.
Are the on the same Docker network, or do you have UFW enabled?
I literally postet a screenshot where you can see that they are all on the same standard bridge network (2nd screenshot)
but problem got resolved, I disabled DSMs Multiple Gate checkbox and things are good again. Marius recommended it (step 15) and by accident I stumbled over the guide:
https://mariushosting.com/how-to-install-homarr-on-your-synology-nas/
Marius Hosting
How to Install Homarr on Your Synology NAS
Trustworthy expert guide to your Synology NAS.