Namenloss

Log has endless messages, started with alpha 9 (no any manual changes done to base nginx): Http::Nginx::Config: there are errors in config, reconfigure. Dec 17 16:51:44 ndm Http::Manager: unable to update configuration, retry.

4.2a5: Apr 22 12:05:21 https-dns-proxy 71CC: "https://dns.nextdns.io/xxxxxx": curl error message: Operation timed out after 3000 milliseconds with 0 bytes received (28) Apr 22 12:05:21 https-dns-proxy F9CB: "https://dns.nextdns.io/xxxxxx": curl error message: Operation timed out after 3001 milliseconds with 0 bytes received (28) Apr 22 12:05:22 https-dns-proxy 0327: "https://dns.nextdns.io/xxxxxx": curl error message: Operation timed out after 3003 milliseconds with 0 bytes received (28) Apr 22 12:05:23 https-dns-proxy DB9E: "https://dns.nextdns.io/xxxxxx": curl error message: Operation timed out after 3001 milliseconds with 0 bytes received (28) Apr 22 12:05:23 https-dns-proxy 5C31: "https://dns.nextdns.io/xxxxxx": curl error message: Operation timed out after 3001 milliseconds with 0 bytes received (28) Apr 22 12:05:23 https-dns-proxy "https://dns.nextdns.io/xxxxxx": too many failed requests, try to downgrade to HTTP/2 1 router KN-3810, 1 wired client... just connected to the router

Thanks for explanation about bootstrap, maybe should be documented somehow, I thought it should take less time. QUIC is not blocked for sure, since https://quic.nginx.org/quic.html test can be executed endlessly with no issues. Thank you for implementing fallback.

Test router is connected to main KN-1811 ("Titan"), 'Cloud-based content filtering and ad blocking' is not installed, remove all DNS except provider one, configure DoH Google - Stubby is not able to bootstrap, fails immediately according to the logs. Add 1.1.1.1 as a common DNS. Use for some time (it works, able to bootstrap, able to resolve using DoH - at least DNS leak test confirms Google DNS as an upstream), after it starts to create issues as above. Will add self-test at evening.

4.2 a4, hopper (KN-3810): Apr 13 23:56:17 https-dns-proxy 5028: "https://dns.google/dns-query": curl error message: QUIC connection has been shut down Apr 13 23:56:17 https-dns-proxy 12C4: "https://dns.google/dns-query": curl error message: QUIC connection has been shut down Apr 13 23:56:17 https-dns-proxy 5199: "https://dns.google/dns-query": curl error message: QUIC connection has been shut down Apr 13 23:56:17 https-dns-proxy F834: "https://dns.google/dns-query": curl error message: QUIC connection has been shut down Apr 13 23:56:17 https-dns-proxy F565: "https://dns.google/dns-query": curl error message: QUIC connection has been shut down Apr 13 23:56:17 https-dns-proxy D596: "https://dns.google/dns-query": curl error message: QUIC connection has been shut down Apr 13 23:56:28 https-dns-proxy E61E: "https://dns.google/dns-query": curl error message: QUIC connection has been shut down Apr 13 23:56:28 https-dns-proxy "https://dns.google/dns-query": too many failed requests, try to reload process Apr 13 23:56:28 ndm Service: "DoH "System" proxy #0": unexpectedly stopped. Region: EU. Works for some time, after fails. AdGuard Home on a separate server works without issues with DoH and same Google DNS. Also still issue with bootstrap is not fixed, provider DNS is not enough, you need to add something like 1.1.1.1/8.8.8.8 .

+1 за добавление данного функционала

+1