Help troubleshooting web interface that quits working

[cacack]

Hello! I'm trying out AGH and running into a strange problem -- the web interface quits working after some time. I'm trying to get my head around what is going on here as my setup might be a little different than most..

I'm running AGH in an LXC container on a host with multiple VLANs. One VLAN is kinda the "management" LAN where the web interface is accessible. AGH is then providing DNS resolution to all VLANs. AGH's container is connected to the VLANs using bridges and is configured with static IPs.

I successfully run through the setup wizard on port 3000, then am able to access using port 80 for some time (minutes/hours) before it quits responding. This let's me setup AGH using the web interface before going dark. Afterwards, I muck with the config by editing the YAML file directly. AGH continues to serve DNS resolution though while in this state.

Using tcpdump within the LXC container, I can see the HTTP packets getting directed towards AGH but no response back out.

root@adguard:~# tcpdump -i eth-hosted                                                                                                                                                                                                                                                 
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth-hosted, link-type EN10MB (Ethernet), snapshot length 262144 bytes
15:36:57.141720 IP 192.168.16.205.50734 > adguard.http: Flags [S], seq 3218016099, win 65535, options [mss 1460,nop,wscale 6,nop,nop,TS val 1008642333 ecr 0,sackOK,eol], length 0
15:37:02.335794 ARP, Request who-has adguard tell 10.10.128.1, length 46
15:37:02.335843 ARP, Reply adguard is-at 00:16:3e:d5:36:87 (oui Unknown), length 28
^C
3 packets captured
3 packets received by filter
0 packets dropped by kernel

Routing:

root@adguard:~# ip r
default via 10.10.128.1 dev eth-hosted proto static 
10.10.10.0/24 dev eth-guest proto kernel scope link src 10.10.10.5 
10.10.32.0/24 dev eth-iot proto kernel scope link src 10.10.32.5 
10.10.128.0/24 dev eth-hosted proto kernel scope link src 10.10.128.5 
10.10.144.0/24 dev eth-storage proto kernel scope link src 10.10.144.5 
10.10.192.0/24 dev eth-main proto kernel scope link src 10.10.192.5 
192.168.16.0/24 dev eth-old proto kernel scope link src 192.168.16.6 

I enabled verbose logging, but nothing seems to be logged regarding the web interface, just DNS-related actions.

root@adguard:~# tail -f /tmp/aghlog.txt 
2023/08/20 15:47:13.692791 204#59 [debug] clients: added 1 client aliases from arp neighborhood
2023/08/20 15:47:13.692805 204#24 [info] dnsproxy: listening to udp://10.10.128.5:53
2023/08/20 15:47:13.692876 204#24 [info] dnsproxy: creating tcp server socket 10.10.128.5:53
2023/08/20 15:47:13.693005 204#24 [info] dnsproxy: listening to tcp://10.10.128.5:53
2023/08/20 15:47:13.693228 204#60 [info] dnsproxy: entering udp listener loop on 10.10.128.5:53
2023/08/20 15:47:13.693311 204#65 [debug] querylog: the oldest log entry: 2023-08-20T02:27:47.746461916Z
2023/08/20 15:47:13.693381 204#65 [debug] querylog: 2023-08-20T15:47:13Z <= 2023-11-18T02:27:47Z, not rotating
2023/08/20 15:47:13.693474 204#63 [debug] filtering: starting updating
2023/08/20 15:47:13.693544 204#63 [debug] filtering: finished updating, 0 updated
2023/08/20 15:47:13.693641 204#61 [info] dnsproxy: entering tcp listener loop on 10.10.128.5:53

At this point all signs point to AGH's HTTP listener. What am I missing or not troubleshooting? Is this a bug? What else can I troubleshoot before opening up a bug ticket?

Thanks!
-Chris