first file must be corrupt. the full download is 10mb.
delete both and retry.
(edit) your yaml file is corrupt i suspect.
Change directory to your /opt/AdGuardHome folder
then run this. ./AdGuardHome --check-config
it will tell you if your yaml file is ok. If it is not. Delete it and re-set AGH back up by going to your router page at port 3000 as per first install. http://192.168.1.1:3000
it failed to install the service because it was already installed.
apt install sudo
then rerun the script if you want it to clean properly.
However AGH should start and alllow you to configure it right now.
Also take note of the file it downloaded for your router. Looks like you were using the wrong mips version. Which is why it was failing to start. Your version is mipsle not plain mips.
That is what the script pulls. That is also what your cpu is.
Might explain why it doesn't self update as well. May be worth filing an issue with the AGH team as to why you do not get an "update" button on your version like the rest of us do.
(edit) so if you replace the download link from my script with your le version it will work. But be aware this makes NO checks at all and will just download the new version and replace your old one over the top.
@mercygroundabyss, do you use cloudflare for any specific reason? Unfortunately, my network is very unstable when I use cloudflare dns, it has much less latency compared to adguard itself, but the most interesting thing is that even with a higher latency, adguard dns is much better than it on my network. Would it be okay if I use adguard instead of cloudflare?
Of course. You can use which ever dns you prefer. Its why i list the options. I just use cloudflare as its quicker and regionally based for me. In theory it should work worldwide.
Any particular reason you set your wan with one specific dns host - (cloudflare) in this case, as opposed to like 127.0.0.1 (if AGH runs on your main router and not another device connected to your LAN).
In my config I have the fastest (based on my location) and most trusted public dns providers lined up one after the other and then set AGH to Load Balancing mode.
Therefore my wan interface gets the benefit of both not querying the same server all the time as well as potentially resolving quicker in the event where other providers on my list are able to resolve quicker as determined by AGH's Load Balancing algorithm.
Just wondering if I'm missing something here logically or perhaps technically...