Https-dns-proxy service stops in version 24.10

Installing and Using OpenWrt
1

https-dns-proxy doesn't really get along with the new 24.10.0
since 24.10.0-rc7 it worked fine
and the final version 24.10 has some kind of glitch
that is, the https-dns-proxy service stops
The reason for stopping the service may be the installation of any additional package
I temporarily solved the problem by adding ( sleep 10 && /etc/init.d/https-dns-proxy start ) to the rc.local file

2

Sounds like a race condition..

3

I agree, but so far I have no thoughts why this is happening

4

This was a couple of years ago, the https-dns-proxy service could stop by itself
i'm worried so that this does not happen :slight_smile:

5

if this helps in any way, then the error in the log is

https-dns-proxy [3317]: Stopping https-dns-proxy 2023.12.26-r2 on_failed_health_check
https-dns-proxy [3317]: Setting trigger (on_boot)

6

Yes, the problem has existed since the update to 24.10. In general, I'm not thrilled with 24.10 - it seems that the release was too fast, the number of luci modul updates for several days only confirms this.

7

yeah, truly sucks when stuff you get for free isn't perfect .. :frowning:

4 Likes
8

For free? Don't judge others by yourself. Unlike you, I support OpenWrt financially. BTW: as for you, if you don't have anything sensible to say, it's better not to speak out.

1 Like
9

Some people are experiencing issues with https-dns-proxy. It is probably frustrating. I am just going to put my experience here to show that the issue might not be universal or does not seem to appear for all. I have been using 24.10.x both for RC releases and now the stable release and the service is running nominally.

10

I am in contact with the author on github, so something is happening in the topic. With me, the problem occurs exactly since the update to 24.10 (I did not use the beta version) and only after the cold boot (not restart!), which is pretty darn strange. This whole situation is a big problem, because the encrypted DNS is currently the basis of the safety and privacy of the network, this must be used. This is not an additional service that can be omitted.

11

i´m having a hard time getting it working properly

Fri Feb 7 12:02:29 2025 daemon.err doh-client[6334]: 2025/02/07 11:02:29 Get "https://cloudflare-dns.com/dns-query?ct=application/dns-message&dns=AAABAAABAAAAAAABA3d3dwZpcGRlbnkDY29tAAABAAEAACkQAAAAAAAAAA": tls: failed to verify certificate: x509: certificate is valid for OpenWrt, not cloudflare-dns.com

so i dont get any name resolution

12

don't bring up LAN on boot

add a sleep and https-dns-proxy restart to rc.local
bring up lan after the restart of https-dns-proxy.

1 Like
14

Try another provider, such as Quad 9.

1 Like
15

This is not https-dns-proxy.

1 Like
16

I switched to SmartDNS - it is much better and newer piece of code. Example configuration:

obraz
obraz970×286 15 KB

17

It may be better for you, but not for me :slight_smile:

18

??? I gave a working solution to the problem, but if it doesn't suit you then don't use it. SmartDNS has much more possibilities, Https-Dns-Proxy seems very archaic in comparison.

1 Like
19

Working solution of what?
You just said that this program is better, but I do not agree with you
I did not have a question about an alternative
I wrote the working solution there, at the very beginning :slight_smile:

20

So don't use it. Bye.

21

i tried to install a program smartdns, it's just a hat