Nathan Warawa

I don't think it's an SD card issue. Performance wise it's about twice the requirement. And if it was a bad block, I doubt the issue would be the same across two different images. As for logs... where? I tried running "sudo dmesg -T --color=always --level=err,warn | more" and nothing about AdGuard came up. I checked the AdGuardHome.yaml file and confirmed bind_host was set to 0.0.0.0 (I also tried setting it to 192.168.0.6... no improvement). The command "sudo netstat -tulnp | grep 3000" said command not found, and "journalctl -u AdGuardHome" came back with no entries.

I got an Orange Pi Zero 3 (1.5GB) to run Adguard Home. I tried the latest Armbian image (25.5.1), first with DE, then without... same problem. I run the config wizard and install AdGuard Home through it, set it up via the browser (192.168.0.6:3000), then reboot to make sure the service loads properly on boot... which it doesn't. Well, the service SEEMS to be running, according to the monitor, but I can no longer access AdGuard via the browser (and yes, I reserved 192.168.0.6 for the Orange Pi in the router).