Taro Su

[use this docker-compose.yml](https://github.com/OCSInventory-NG/OCSInventory-Docker-Stack/blob/master/docker-compose.yml)

How about 172.30.0.0/16 --interface=eth0 ? this kind configuration work or not ? If from eth0 can ping 172.30.0.0/16 whole network no problem, does Pi.Alert can also scan whole 172.30.0.0/16 network...

> As I understand - it increases the time to scan the network. You can increase the time between scans (in @leiweibau's fork I think via a cron change and...

This error not just for domain name access or reverse proxy access, also happen when direct use http://ip_address:3001/

Useless discussion....

Same sympton here: root@docker219 ~# netbird status -d Peers detail: pve.netbird.selfhosted: NetBird IP: 100.86.4.26 Public key: dIuwdZzyZpSQPx64I7wo8uzl/su75PaNpklHVhZFkCw= Status: Connected -- detail -- Connection type: Relayed Direct: false ICE candidate (Local/Remote):...

root@netbird:~# netbird status Daemon version: 0.25.9 CLI version: 0.25.9 Management: Connected Signal: Connected Relays: 2/2 Available FQDN: netbird.netbird.selfhosted NetBird IP: 100.86.138.236/16 Interface type: Kernel Peers count: 4/5 Connected root@netbird:~# ping...

ping hostname (FQDN) can been translate to the IP address, only use default ALL group, and Default all pass Access Control setting.

Found root cause for my network environment, all cannot ping or been ping system network already install Tailscale daemon, after remove/uninstall the Tailscale daemon, cannot ping issue gone/solved.

Just build a docker/container, and deply a nginx web browser, than monitor it, shutdown it....the alert notify should be work....