Integrations and ping not working on same host
Integrations / ping work fine on different hosts, e.g. both my RPi's running pihole. But all other apps get "ping timed out" whether they are a docker container or an app running locally on the same host (NAS). All of the links launch from homarr fine. I have tried different variations of the internal IP (host IP, container IP, container hostname) all with the same result. Several of the apps, like DSM, Radarr, and Sonarr, are not running in docker, but also unable to connect.
12 Replies
What are you hosting homarr in? (Docker, compose, portainer, etc?)
Because it's all icons, it's feels like a container wrapper, or DNS issue to me.
What response do you get from running curl?
@spacesloth
@explosive parrot remember to right click reply on the messages or to @ the person when replying to get help requests, discord threads are hard difficult to navigate to if you don’t get tagged
I have it running in docker. I recently relaunched it from portainer using compose to deal with the new update and added variable. I noticed it created its own network. I tried adding it to bridge and/or removing the network it created. @explosive parrot
@spacesloth others have had so issues with portainer and pings, search aroind the previous help logs to see if on of that solutions work for you.
Does a curl from inside the container work as expected?
testing...stay tuned.
@explosive parrot from inside homarr's container, curl is not a command 🤔. But I can use curl from a different container that has it loaded as part of the image.
@explosive parrot
@spacesloth so you can curl external addresses, but not local addresses?
Use wget
@explosive parrot Ok, I only previously tested with something external.🤦♂️ I just went through the same exercise internally and the container could only curl from a docker IP; not with the host IP. I also tried to curl an app running directly on the NAS, and it also could not reach it using the host IP. So it seems I have docker network issues. I know the docker IP's are dynamic, so I can't rely on those.
Unfortunately I can't help you with docker network issues.
@explosive parrot @ajnart Thank you for all the help up to this point. I think I may be able to resolve this if I can give my containers an alias for the user defined bridge. I need to work on that and to find if watchtower updates result in the hostname or alias of the container changing.