Bluetesteur

Whatever binhex, thanks a lot for your time, all seems to work fine now with NAME_SERVERS=8.8.8.8,1.1.1.1

I tried without values, not working Expected using the default ones provided by the container as show in log: 2023-06-23 15:49:19.225366 [warn] NAME_SERVERS not defined (via -e NAME_SERVERS), defaulting to name servers defined in readme.md EDIT: Just tried with NAME_SERVERS=8.8.8.8,1.1.1.1, it seems to go forward better.. But I don't understand why it was not working without this line NAME_SERVERS in docker-compose, this line was never in my conf, and without it, container should use the ones provided by you and should works , no ?

Hello, I used this docker image since several month on synology without any issue. But since several days, my container arch-sabnzbdvpn didn't work any more. I use openvpn with privado VPN, Container is managed by docker-compose in portainer. 2023-06-23 14:03:27 Initialization Sequence Completed 2023-06-23 14:19:21,499 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... Inside the container: ping fra-001.vpn.privado.io PING fra-001.vpn.privado.io (91.148.232.10) 56(84) bytes of data. 64 bytes from fra-001.vpn.privado.io (91.148.232.10): icmp_seq=1 ttl=53 time=13.8 ms 64 bytes from fra-001.vpn.privado.io (91.148.232.10): icmp_seq=2 ttl=53 time=16.3 ms [root@4d82410dacab config]# nslookup fra-001.vpn.privado.io ;; communications error to 84.200.69.80#53: timed out ;; communications error to 84.200.69.80#53: timed out Thanks for you help 🙂