Unable to reach AdGuard WebUI

[jokerigno]

Hi,

I installed this LXC some months ago and worked flawlessy till today when I noticed that webgui is no longer reachable. If I try with the defined IP (192.168.2.103) I receive the ERR_CONNECTION_REFUSED message (tried with edge and firefox.

Any advice?

[tteck]

What's the output from hostname -I?

[jokerigno]

that' exactly the same IP adress:

root@adguard:~# hostname -I
192.168.2.103

[X-Anonymous-Y]

Are you use a VPN? It was for me the same error yesterday with Wiregueard VPN

[jokerigno]

I'm running a Tailgate instance inside Home Assistant VM (that is running as an addon). But this worked without issue. Maybe something has broken recently? What do you suggest?

[X-Anonymous-Y]

I just created a new VPN tunnel and that worked for me.

[davethecripple]

Were you ever able to resolve this? I'm running into the same exact issue - unable to reach the WebUI - worked flawlessly up until 2 weeks ago - IP address matches still.

[tteck]

What does systemctl status AdGuardHome show?

[jokerigno]

nope. I recreated the container and now it seem working again.

[neyzm]

I'm having the same issue, Running systemctl seems fine, but when I run journalctl it shows the following:

Feb 03 20:15:45 adguard systemd[1]: Starting AdGuard Home: Network-level blocker...
Feb 03 20:15:45 adguard systemd[1]: Started AdGuard Home: Network-level blocker.
Feb 04 12:40:09 adguard systemd[1]: Stopping AdGuard Home: Network-level blocker...
Feb 04 12:40:09 adguard systemd[1]: AdGuardHome.service: Succeeded.
Feb 04 12:40:09 adguard systemd[1]: Stopped AdGuard Home: Network-level blocker.
Feb 04 12:40:09 adguard systemd[1]: AdGuardHome.service: Consumed 58.075s CPU time.```