70 lines
2.1 KiB
Markdown
70 lines
2.1 KiB
Markdown
# Debug Session: AdBlock Not Working + Device Connectivity
|
|
|
|
**Date:** 2026-01-25 13:20
|
|
**Status:** IN PROGRESS
|
|
|
|
---
|
|
|
|
## Initial Findings
|
|
|
|
### 1. AdGuardHome-Sync Container
|
|
- **Origin:** 192.168.31.1:80 (MikroTik AdGuard)
|
|
- **Replica:** 192.168.31.4:3000 (Unraid AdGuard)
|
|
- **Sync interval:** Every 30 minutes
|
|
- **Status:** Failing since 10:00 with "no route to host"
|
|
|
|
**Error:**
|
|
```
|
|
2026-01-25T10:00:01.349Z ERROR sync Error getting origin status
|
|
{"from": "192.168.31.1:80", "error": "dial tcp 192.168.31.1:80: connect: no route to host"}
|
|
```
|
|
|
|
### 2. AdGuard Filtering Configuration
|
|
- **Filters enabled:** 1 (AdGuard DNS filter only)
|
|
- **AdAway blocklist:** DISABLED
|
|
- **protection_enabled:** true
|
|
- **filtering_enabled:** true (global)
|
|
- **Multiple client profiles have filtering_enabled: false**
|
|
|
|
### 3. Architecture Discovery
|
|
There are TWO AdGuard instances:
|
|
1. **MikroTik AdGuard** - 192.168.31.1:80 (origin/master)
|
|
2. **Unraid AdGuard** - 192.168.31.4:3000 (replica)
|
|
|
|
Sync copies config from MikroTik → Unraid
|
|
|
|
### 4. Current Issue: Devices Have No Internet
|
|
- LG TV showing no connection
|
|
- Likely cause: DNS changes not propagated to DHCP clients
|
|
- Devices may have cached old DNS or DHCP lease hasn't renewed
|
|
|
|
## To Investigate
|
|
- [ ] Check MikroTik DHCP DNS settings
|
|
- [ ] Check if MikroTik AdGuard is running (container on MikroTik?)
|
|
- [ ] Verify DHCP leases are pushing correct DNS
|
|
- [ ] Check if NAT rules are redirecting properly
|
|
|
|
---
|
|
|
|
*Debug session paused - device connectivity issue reported*
|
|
|
|
## Debug Session 2 (13:55)
|
|
|
|
### Findings
|
|
- AdGuard IS receiving queries from clients (192.168.31.100, .134, .101, etc.)
|
|
- AdGuard IS responding (Elapsed times logged)
|
|
- MikroTik DNS working (resolve commands succeed)
|
|
- Internet reachable from Unraid (ping google.com works)
|
|
- Connectivity check URLs all return proper status codes
|
|
- Masquerade rules have packet counts (traffic flowing)
|
|
- No connectivity domains being blocked
|
|
|
|
### Status
|
|
All server-side tests pass. Issue may be:
|
|
1. Client-side caching of old DNS
|
|
2. Device needs reconnect after all the changes
|
|
3. Specific device issue
|
|
|
|
### Recommendation
|
|
Have user disconnect/reconnect device to get fresh DHCP lease and DNS.
|