Just wondering if you can do me a favour to see what happens.
Can you please go into your portainer , create a new container and as the image just put:
ghcr.io/bakito/adguardhome-sync
and deploy it, nothing else, no settings… The see what the log says
I created a container using this:
version: "2.1"
services:
adguardhome-sync:
image: ghcr.io/bakito/adguardhome-sync
container_name: adguard_syncTest
command: run
ports:
- 8084:8080
restart: unless-stopped
It builds fine, but when it runs the log reports an error:
“Error: origin URL is required”
BTW, I’m on a Synology NAS, running Container Manager, which is Synology’s version of Portainer.
thanks, yeah even with as little as that I get nothing I’ll file that report
got it working. @bakito had to compile a version that ran on raspberry pi 5, so now it works! 
My next question is , an adguardhome, where can you set the secondary DNS server for DHCP clients?
I want to have it so that:
if people get a DHCP address from AGH_1 , then their DNS is set to AGH_1 and secondary DNS is AGH_2
if they get a DHCP address from AGH_2 , then their DNS is set to AGH_2 and secondary DNS is AGH_1
that way if either goes down, it all still works…
Glad you finally got it working! Not sure about multiple DHCP servers as I only use my two Adguard instances as DNS servers and delegate DHCP to my router.
Maybe set a unique range of addresses each Adguard can serve? AGH_1 serves addresses 2 to 100. AGH_2 serves 100 to 200. The client chooses one of them.
Still need to tell all the clients on the network to have DNS1: AGH_1_IP, DNS2: AGH_2_IP
Otherwise, you only get the DNS server of the one that gave you your ip address, and if that one goes down…
I’ve found out what I need to edit. Option 6, It’s in the adguardhome.yaml file.
Blockquote
‘options’:
–‘6 ips 1.2.3.4,1.2.3.5’
Just need to find where that is stored…
Ok, I’ve looked everywhere… Where does home assistant store the adguardhome.yaml file?
I’ve looked everywhere…
Otherwise I have to back up adguard, open the archive, edit the file in the backup by hand and then restore it 
The file is not easily accessible. I believe it’s within a HASSOS container, but that’s way over my head.
Hi folks,
I’m seeking confirmation on the setup of Adguard.
I use a SKY router which does not have the ability to modify any DNS settings.
The Adguard addon has installed on my Home Assistant installation HAOS on a Pi4.
All seems to be running ok.
On my home laptop I have changed the wifi adapter IPV4 protocol to use the DNS address of my Pi4.
When I use the laptop and look at the pi4 dashboard for adguard I do see DNS queries and block by filters increasing so I was presuming this is working ok?
On the laptop however I am seeing limited blocking of adverts? Even using extra blocklists.
As an experiment if I set Youtube as a blocked service on the adguard pi4 setup, youtube still works and does not appear to be blocked.
I’m confused that the dashboard ‘appears’ to show it is working but in practise I’m seeing limited adverts being blocked?
I have not changed any DHCP settings in Adguard. The router is still the DHCP server.
Any advice if this is correct?
Thanks…
How can I disable blocking for certain devices?
Hi all, I’m trying to understand how to acces to the AG web interface without passing trough the HA interface. Is it possible or I’m getting crazy for nothign?
Tnx for your reply
If you haven’t changed any default settings then I guess homeassistant.local:8020
I recently migrated my HA/AdGuard Home/NGINX Proxy Manager setup from individual containers/VMs on Proxmox to HAOS on Raspberry Pi5, with AdGuard Home (AGH) and NPM running as Add-ons. I was able to migrate my existing configurations with only minor modifications, and things seem to be generally working as hoped with one random, recurring issue. At least once a day, I’m unable to access hosts on my LAN that are proxied behind NPM and configured with a URL that uses a local domain name to identify the host. Then, 10 minutes to an hour later, it all works fine again. Easier to explain with an example - during this blackout period,
https://host.my.domain returns a 502 - Bad Gateway error from NGINX when the host being proxied is configured as host.localdomain:<port> in NPM, buthost.localdomain:<port> to <host_ip>:<port> in the NPM host entry I can access the requested service just fine at https://host.my.domainhost.localdomain is assigned with a DNS rewrite in AGH, so it seems that for that brief period DNS rewrites aren’t working, but when this issue is happening if I try pinging host.localdomain from another host on the network, or even from inside the AGH or NPM containers, it resolves to the proper IP and pings just fine. My LAN is configured on my router (Unifi Dream Machine) to use the IP of HAOS (hosting AGH) as the only DNS server, so all lookups are directed to the HAOS IP. And that all works 96% of the time. I really don’t know if the hiccup lies with AGH or NPM or HAOS. I have UptimeKuma tracking the availablility of those resource by pinging their proxied URLs, which is how I’ve become aware of the recurrence of the issue.
I didn’t have this issue before the migration, so I’m wondering if I botched something in the config migration, or if there’s just something off about the HAOS Add-ons that I’m not picking up on. Also not sure if this is the right forum for this, but perhaps someone will have some insight that might help me track down the issue.
Any ideas where to look next?
@frenck I have the AdGuard server up and running in the network and is fine.
I installed your AdGuard integration, native, but I cannot login in any way.
Can you help?