no route to host about adguardhome-sync HOT 16 CLOSED

Same error for me. Any resolution found yet?

from adguardhome-sync.

Are AGH and the Sync pod running in the same dicker instance?
Are they allowed to connect?

Sounds Like a connectivity issue to me

from adguardhome-sync.

from adguardhome-sync.

It seems the docker container is not allowed to do the connection.
This would be an issue with docker and not this tool

from adguardhome-sync.

from adguardhome-sync.

for which IP did you have to do that?
Can you share your configuration?

I'd like to be able to reproduce this.

from adguardhome-sync.

from adguardhome-sync.

I'm having a 'no route to host' error for the replica as well. Having the / at the end of the IPs doesn't fix it. I can get to the IP:PORT that I have configured in my browser just fine, but getting 'no route to host' in the adguard-sync logs. The origin is running in docker on a Pi, and the replica is running in docker on Unraid with Br0 network.

2022-01-31T09:50:05.231-0800 ERROR sync sync/sync.go:193 Error getting replica status {"from": "192.168.1.128:8081", "to": "192.168.1.64:80", "error": "Get \"http://192.168.1.64:80/control/status\": dial tcp 192.168.1.64:80: connect: no route to host"}

from adguardhome-sync.

Have you tried to get more info from debug mode by setting env var LOG_LEVEL=debug ?

from adguardhome-sync.

I just figured it out.. kind of. The problem seemed to be adguard-sync being on a custom docker network. I have the origin instance running on a pi, while the replica was on the same unraid host as the sync docker, but on br0 network with it's own IP. I'm not sure why adguard sync can't access it though, since it has it's own IP and is accessible from other devices on the network. Is it expected that adguard-sync must be run on br0 or host network?

from adguardhome-sync.

To clarify, all I changed was Adguard-sync from custom docker bridge network to br0 network and gave it it's own IP and suddenly it could communicate fine with the 192.168.1.64:80 adguard instance, running on unraid br0 as well.

from adguardhome-sync.

To clarify, all I changed was Adguard-sync from custom docker bridge network to br0 network and gave it it's own IP and suddenly it could communicate fine with the 192.168.1.64:80 adguard instance, running on unraid br0 as well.

Thank you very much for this fix. I had the exact same issue and this resolved it.

Setup with failure:

Adguard 1 on Unraid 1 network: br0
Adguard 2 on Unraid 2 network: br0

Adguard-sync on Unraid 2 network: bridge

Once I changed adguard-sync on Unraid 2 from bridge -> br0, it works with no other changes required.

Must have something to do with traversal between br0 and bridge?

from adguardhome-sync.

I'm getting the same error after deploying this evening.

ERROR	sync	sync/sync.go:104	Error getting origin status	{"from": "10.0.1.2", "error": ": Get \"http://10.0.1.2/control/status\": dial tcp 10.0.1.2:80: connect: no route to host"}

My (master) instance is on the same host but set up as a macvlan on 10.0.1.2 with the host IP of the NAS as 10.0.1.100. Now I understand that in order for the host to be able to reach the macvlan, you need to create a bridge network. I did that using the instructions here and that has now at least allowed by Homer instance (same docker host) to access AGH on 10.0.1.2 but sadly, I still get an error from AGHS as above.

P.S The slave unit is on a Pi on 10.0.1.3

from adguardhome-sync.

I just fixed my issue by adding my AGH docker container to the bridge network created by AG-Sync (adguard-sync_default) and then changing the AG-sync config for my primary DNS server to the docker IP (172.20.0.2). Probably not the best way to do it but it works.

from adguardhome-sync.

I've updated my methodology after watching many hours of docker networking videos. Seems with a custom bridge network (not the default bridge), DNS name resolution is native so using the container name is the preferred method to ensure containers can always talk to one another.

If you have AG-Sync and AGH on the same host, simply join the AGH instance to the new bridge network that AG-Sync creates (adguard-sync_default) and the modify your config file to that below:

services:
  adguardhome-sync:
    image: ghcr.io/bakito/adguardhome-sync
    container_name: adguardhome-sync
    command: run
    environment:
      ORIGIN_URL: http://adguard-adguardhome #172.20.0.2/
      ORIGIN_USERNAME: username
      ORIGIN_PASSWORD: password
      REPLICA_URL: http://10.0.1.3/
      REPLICA_USERNAME: username
      REPLICA_PASSWORD: password

Your AGH instance should now be part of two networks; the macvlan and the adguard-sync_default.

from adguardhome-sync.

Adguard Sync did not make a new netrwork on my docker instance. I tried adding AdGuard Home to my default vlan and see if it could get there through the 172 address and it could not. I am not sure why it cannot get to it over it's own IP (10.100 address space).
I have AdGuard on it's own VLAN with it's own reserved IP. Different from the external address of the host PC. I can use all servics normally through this second IP, but for whatever reason. AdGuard Sync does route properly to it. It baffles me.

from adguardhome-sync.