nope, I also tried with the stable release of dnsproxy, I stop the servivce and try to start it with that command, and it is not starting.
2025/02/02 14:15:21.340113 ERROR running dnsproxy err="creating proxy: validating general upstreams: no upstream specified"
the upstream is there and this is a test with the version that is working well
I just installed dnsproxy (0.74.1-r1, from RC7)
Only thing done in the config file was to enable it.
It runs just fine, zero errors in the log
root@OpenWrt:~# netstat -tulp | grep proxy
tcp 0 0 localhost:mdns 0.0.0.0:* LISTEN 20232/dnsproxy
tcp 0 0 localhost:mdns :::* LISTEN 20232/dnsproxy
udp 0 0 localhost:mdns 0.0.0.0:* 20232/dnsproxy
udp 0 0 localhost:mdns :::* 20232/dnsproxy
20207 root 2984 S {dnsproxy} /sbin/ujail -t 5 -n dnsproxy -U dnsproxy -C /etc/capabilities/dnsproxy.json -l -o -r /etc/hosts -r /etc/ssl/certs/ca-certificates.crt -- /usr/bin/dnsproxy --listen
20232 dnsproxy 1207m S /usr/bin/dnsproxy --listen 127.0.0.1 --listen ::1 --port 5353 --bootstrap tls://8.8.8.8 --fallback tls://9.9.9.9 --upstream tls://1.1.1.1 --hosts-file-enabled false
our command lines are very different though
Yes as I said, 0.74 is fine, but update it to 0.75.0 and you will see...
seems there's already a workaround/solution posted in your github ticket ?
I did tell you to look at the init file
2 Likes
Yep I compare both, it was identical
OK I saw, it is adguard who changed something in the last update, so it affects the Open Wrt init.
Nice I will try.