ApatheticRiku

No, AdGuard is not exposed to the web. It's just a generally accepted best practice to have unique secure passwords for everything. I use a password manager to generate my passwords, so I enforce the same strict requirements no matter where I am creating accounts. What I was getting at was that AdGuard clearly supports all of the special characters that were in my previous password, as is evident by the fact that I had no issue authenticating normally. I would just recommend looking into the plugin to see if you are doing anything that might be mishandling the characters that AdGuard supports as valid. Again, I really like the plugin, and everything it manages to do, just some feedback.

I think I just figured out the AdGuard issue by myself. I dove through docker logs and saw an error on the AdGuard-Home container mentioning invalid Basic Authorization value. So I reset my AdGuard password to a new one that did not contain any special characters, and updated the exporter plugin. Using the UI, it started up and stayed running. Grafana now shows all of the content I would expect as well. I'm not sure what the difference would be between the UI and the console command, but somewhere along the line, the UI is not parsing the password value correctly and is failing authentication if it contains special characters. Thank you @ich777 for making a great plugin, but I think this warrants looking into in the codebase as special characters are supported by AdGuard and are a generally recommended part of a secure password.

@ich777 I ran the supplied command in the Unraid console and the HTTP server started up and ran for over 3 minutes with no errors. I also was able to get metrics in Grafana for the first time while letting it run. I stopped the process and went back to the UI and clicked Start, but the same issue I always have happened again. It came up saying "Running", but went back to "Stopped" after about 5 seconds. So running through console works flawlessly, but not through UI. I'll also point out, your command you sent had one typo in it. At the end, you refer to a variable named ${INERV} instead of ${INTERV}. Here's the output of the command before I stopped it: prometheus_adguard_exporter -adguard_hostname ${HOSTNAME} -adguard_port ${PORT} -adguard_protocol ${PROTO} -adguard_username ${USERNAME} -adguard_password ${PASSWORD} -server_port ${EXP_PORT} -interval ${INTERV}s 2022/04/30 17:52:54 --------------------------------------- 2022/04/30 17:52:54 - AdGuard Home exporter configuration - 2022/04/30 17:52:54 --------------------------------------- 2022/04/30 17:52:54 AdguardProtocol : http 2022/04/30 17:52:54 AdguardHostname : 192.168.10.250 2022/04/30 17:52:54 AdguardUsername : tony 2022/04/30 17:52:54 AdGuard Authentication Method : AdguardPassword 2022/04/30 17:52:54 AdguardPort : 3000 2022/04/30 17:52:54 ServerPort : 9617 2022/04/30 17:52:54 Interval : 10s 2022/04/30 17:52:54 LogLimit : 1000 2022/04/30 17:52:54 --------------------------------------- 2022/04/30 17:52:54 New Prometheus metric registered: avg_processing_time 2022/04/30 17:52:54 New Prometheus metric registered: num_dns_queries 2022/04/30 17:52:54 New Prometheus metric registered: num_blocked_filtering 2022/04/30 17:52:54 New Prometheus metric registered: num_replaced_parental 2022/04/30 17:52:54 New Prometheus metric registered: num_replaced_safebrowsing 2022/04/30 17:52:54 New Prometheus metric registered: num_replaced_safesearch 2022/04/30 17:52:54 New Prometheus metric registered: top_queried_domains 2022/04/30 17:52:54 New Prometheus metric registered: top_blocked_domains 2022/04/30 17:52:54 New Prometheus metric registered: top_clients 2022/04/30 17:52:54 New Prometheus metric registered: query_types 2022/04/30 17:52:54 New Prometheus metric registered: running 2022/04/30 17:52:54 New Prometheus metric registered: protection_enabled 2022/04/30 17:52:54 Starting HTTP server 2022/04/30 17:53:04 New tick of statistics: 2329 ads blocked / 46397 total DNS queries 2022/04/30 17:53:14 New tick of statistics: 2330 ads blocked / 46404 total DNS queries 2022/04/30 17:53:24 New tick of statistics: 2332 ads blocked / 46411 total DNS queries 2022/04/30 17:53:34 New tick of statistics: 2332 ads blocked / 46412 total DNS queries 2022/04/30 17:53:44 New tick of statistics: 2332 ads blocked / 46419 total DNS queries 2022/04/30 17:53:54 New tick of statistics: 2333 ads blocked / 46424 total DNS queries

I'm running the adguard-exporter, but it keeps stopping. I've verified that it is able to start, and it is able to pull data from AdGuard, but after about 10 seconds, it stops. I can restart it, but it never stays running. AdGuard is running in Docker, but I have it set up in a VLAN with an IP separate from my Unraid host. I've confirmed this issue occurs both when running in a host network, and when running in a custom network under a VLAN. Are there any logs I can find to diagnose why it might be stopping?