atoy3731/adguard-sync

Sync tool for local Adguard Home DNS instances

adguard-sync's Issues

Is it possible to synchronize with Adguard running on a port other than 80?

Im running primary Adguard on the OPNsense and port 80 is used.
And primary Adguard admin GUI running on port 3000

-e "ADGUARD_PRIMARY=http://192.168.1.2:3000" \

Im getting an error:

Running Adguard Sync for 'http://192.168.1.2:3000' => 'http://192.168.1.5'.

• Syncing custom rules
  ERROR: Not able to reach AdGuard. Is it running?

ERROR: Unable to acquire cookie.

It worked for a long time, thank you very much, and then I noticed that it stopped synchronizing with an error:

ERROR: Unable to acquire cookie.
Message: only content-type application/json is allowed

All 3 containers are the latest.

Error during sync

Hi,

I'm just trying out AGHsync for the first time and I'm getting this error but have no idea where to go from here.

Running Adguard Sync for 'http://10.79.1.108' => 'http://10.79.8.2'..,
Traceback (most recent call last):,
  File "app.py", line 89, in <module>,
    custom_rules.reconcile(primary_filtering_status, secondary_filtering_status, ADGUARD_SECONDARY, secondary_cookie),
  File "/opt/app/custom_rules/__init__.py", line 53, in reconcile,
    secondary_custom_rules = _get_custom_rules(secondary_filtering_status),
  File "/opt/app/custom_rules/__init__.py", line 17, in _get_custom_rules,
    custom_rules_str = '\n'.join(custom_rules_array),
TypeError: can only join an iterable,

Any help would be appreciated.

Optimize backend requests

Currently a majority of filter metadata can be pulled from a single backend request, but it is being pulled for every individual element. One request to the status endpoint per reconciliation loop should suffice.

The process seems to get stuck upon start of the container and doesn't sync any changes

Thanks for creating this software, it will be very handy for me when I get it up and running. I'm having some issues and wondered if you could help?

Here is my environment:

Primary AdGuard host

• Host IP: 192.168.88.174
• Docker container image for AdGuard: adguard/adguardhome:latest
• AdGuard container name: adguard
• AdGuard container exposed ports: 53:53/tcp, 53:53/udp, 853:853/tcp, 3000:3000/tcp
• Also running on this host is the Docker container image for adguard-sync: atoy3731/adguard-sync:latest

Secondary AdGuard host

• Host IP: 192.168.88.35
• Docker container image for AdGuard: adguard/adguardhome:latest
• AdGuard container name: adguard
• AdGuard container exposed ports: 53:53/tcp, 53:53/udp, 853:853/tcp, 3000:3000/tcp

adguard-sync docker-compose.yml file contents

version: "3.3"
services:
  agsync:
    image: atoy3731/adguard-sync:latest
    container_name: agsync
    hostname: agsync
    restart: always
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - ADGUARD_PRIMARY=http://192.168.88.174:3000
      - ADGUARD_SECONDARY=http://192.168.88.35:3000
      - ADGUARD_USER=admin
      - ADGUARD_PASS=********************************
      - REFRESH_INTERVAL_SECS=10

Issue
When I do a docker-compose up -d on the adguard-sync folder, it gets created and starts running. However when I tail the logs with docker logs -tf adguard-sync it just has a single entry as follows:
2021-12-21T23:04:15.314397989Z Running Adguard Sync for 'http://192.168.88.174:3000' => 'http://192.168.88.35:3000'..

No further entries ever appear, and when I make changes to the configuration of my primary AdGuard container, they never get synchronised to the secondary one. Any ideas what might be going wrong in my setup?

Configs Sync

It would be great if this could sync the settings of each deployment as well rather than just the blacklists/whitelists.