After the core update (on Odroid N2) the addon doesn’t work anymore. Get message “Error fetching addon info: Unknown error, see supervisor logs”
Logfile:
Logger: homeassistant.components.hassio.handler
Source: components/hassio/handler.py:575
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 12:43:39 (11 occurrences)
Last logged: 12:59:31
/addons/a0d7b954_adguard/info return code 500
/addons/a0d7b954_esphome/info return code 500
Are there more people with this problem and how to solve this?
After 3 times reboot still not work. Also problem to start SSH so decided to cutt off the power completly. After shut down and power cycle everthing works. So problem solved. Thnx for the support.
You would want to focus on getting your pixelserv docker running.
First of all, check your metal box. Is it x86 or arm?
Edit: Forgot to add - the reason I am asking x86 or arm is because the imthai docker image was for x86… and I’m sure there are arm equivalent pixelserv docker out there.
Having installed the Adguard Home add-on, I want to be able to send it cURL requests from custom switch/rest/configuration (to block specific client lists). However, I can only access the web interface through the HA admin instance (on the web interface running on 8123). How do I open Adguard to be able to query it via cURL requests (from within HA) ? where do I find the user/pass and ip/port that Adguard will receive these cURL requests on?
I am trying to configure access via username and password. I enabled the web port in the configuration but as soon as I do that the add-on won’t start anymore. I tried different port making sure that I don’t overlap with an existing service. The log file only says
[06:26:10] INFO: Successfully send discovery information to Home Assistant.
s6-rc: info: service discovery successfully started
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service discovery: stopping
s6-rc: info: service discovery successfully stopped
s6-rc: info: service adguard: stopping
Does anyone know the file that stores the DHCP records in Adguard home?
I would like to export them to another instance of Adguard running on a raspberry pi
I’ve spent two days trying to get that to run. Container all set up , when I start it, it gives error code 139 and then restarts. over and over. also nothing in the log files so I wouldn’t know where to start . It is on a pi 5, so perhaps there’s some incompatibility with Pi os bookworm ?
---
version: "2.1"
services:
adguardhome-sync:
image: ghcr.io/bakito/adguardhome-sync
container_name: adguard_sync
command: run
ports:
- 8083:8080
restart: unless-stopped
environment:
# Main adguard home instance on HA
- ORIGIN_URL=http://192.168.2.110:85
- ORIGIN_USERNAME=bowie
- ORIGIN_PASSWORD=life_on_mars
# Second adguard instance on Synology
- REPLICA_URL=http://192.168.2.12:3000
- REPLICA_USERNAME=bowie
- REPLICA_PASSWORD=life_on_mars
- CRON=*/2 * * * * # run every x minutes
- RUN_ON_START=true
I redirected Adguard Sync port 8080 to 8083 to prevent conflict with another app.
Did you open Adguard port 85 on Home Assistant?
Verify the port on your 2nd Adguard instance. Mine is using 3000.
I set them both to 3000, and I’ve tested them both through a browser to confirm port and login…
I’ll cut and paste your script in (and change the needed bits) and see if that helps. But just reading what you have it looks pretty much the same.
The thing is, my container log file is empty. Even if I got a port wrong or something, surely there would be an error saying that it tried but couldn’t connect right?
Don’t want you to break your setup but surely if you change the port or even unplug a server for a second, the log would show something?
Not sure how to get into the container to see if there is even any files etc in there. Still learning this stuff…
This is my log for the container… Not even a tumble weed blowing through there
My log displays the Adguard Sync version and build date, followed by cron info, and the IP of each Adguard instance. So, it does seem your container is crashing early on. I’d report the issue on github, the author seems to be active there.
Ok, I’ll report it. Just did a test on my portainer setup to be sure it was working, made a container called hello, and told it to use the docker hello-world image.
That worked, log for that had the hello world stuff in it so looks like it’s not just a “me being an idiot” error… Haha