# Https-dns-proxy service stops in version 24.10

**URL:** <https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904>\
**Category:** Installing and Using OpenWrt\
**Created:** [February 6, 2025, 10:29am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904 "2025-02-06T10:29:23Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![fkl7834456](https://forum.openwrt.org/letter_avatar/fkl7834456/32/5_5575768a8748004e209b776fc1b2916d.png) [@fkl7834456](https://forum.openwrt.org/u/fkl7834456)\
**Post date:** [February 6, 2025, 10:29am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/1 "2025-02-06T10:29:23Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![frollic](https://forum.openwrt.org/user_avatar/forum.openwrt.org/frollic/32/30113_2.png) [@frollic](https://forum.openwrt.org/u/frollic)\
**Post date:** [February 6, 2025, 10:33am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/2 "2025-02-06T10:33:32Z")

</div>

> [@fkl7834456](#):
>
> temporarily solved the problem by adding ( sleep 10 && /etc/init.d/https-dns-proxy start ) to the rc.local file

Sounds like a race condition..

---

<div class="post-metadata">

**Author:** ![fkl7834456](https://forum.openwrt.org/letter_avatar/fkl7834456/32/5_5575768a8748004e209b776fc1b2916d.png) [@fkl7834456](https://forum.openwrt.org/u/fkl7834456)\
**Post date:** [February 6, 2025, 10:34am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/3 "2025-02-06T10:34:51Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![fkl7834456](https://forum.openwrt.org/letter_avatar/fkl7834456/32/5_5575768a8748004e209b776fc1b2916d.png) [@fkl7834456](https://forum.openwrt.org/u/fkl7834456)\
**Post date:** [February 6, 2025, 10:45am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/4 "2025-02-06T10:45:00Z")

</div>

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 🙂

---

<div class="post-metadata">

**Author:** ![fkl7834456](https://forum.openwrt.org/letter_avatar/fkl7834456/32/5_5575768a8748004e209b776fc1b2916d.png) [@fkl7834456](https://forum.openwrt.org/u/fkl7834456)\
**Post date:** [February 6, 2025, 10:59am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/5 "2025-02-06T10:59:00Z")

</div>

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)

---

<div class="post-metadata">

**Author:** ![p0k33m0n](https://forum.openwrt.org/user_avatar/forum.openwrt.org/p0k33m0n/32/113395_2.png) [@p0k33m0n](https://forum.openwrt.org/u/p0k33m0n)\
**Post date:** [February 7, 2025, 10:23am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/6 "2025-02-07T10:23:49Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![frollic](https://forum.openwrt.org/user_avatar/forum.openwrt.org/frollic/32/30113_2.png) [@frollic](https://forum.openwrt.org/u/frollic)\
**Post date:** [February 7, 2025, 10:25am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/7 "2025-02-07T10:25:36Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![p0k33m0n](https://forum.openwrt.org/user_avatar/forum.openwrt.org/p0k33m0n/32/113395_2.png) [@p0k33m0n](https://forum.openwrt.org/u/p0k33m0n)\
**Post date:** [February 7, 2025, 10:36am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/8 "2025-02-07T10:36:54Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Llethur](https://forum.openwrt.org/user_avatar/forum.openwrt.org/llethur/32/72907_2.png) [@Llethur](https://forum.openwrt.org/u/Llethur)\
**Post date:** [February 7, 2025, 10:56am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/9 "2025-02-07T10:56:37Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![p0k33m0n](https://forum.openwrt.org/user_avatar/forum.openwrt.org/p0k33m0n/32/113395_2.png) [@p0k33m0n](https://forum.openwrt.org/u/p0k33m0n)\
**Post date:** [February 7, 2025, 11:05am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/10 "2025-02-07T11:05:13Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![boxman](https://forum.openwrt.org/letter_avatar/boxman/32/5_5575768a8748004e209b776fc1b2916d.png) [@boxman](https://forum.openwrt.org/u/boxman)\
**Post date:** [February 7, 2025, 11:07am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/11 "2025-02-07T11:07:45Z")

</div>

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](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](http://cloudflare-dns.com)

so i dont get any name resolution

---

<div class="post-metadata">

**Author:** ![frollic](https://forum.openwrt.org/user_avatar/forum.openwrt.org/frollic/32/30113_2.png) [@frollic](https://forum.openwrt.org/u/frollic)\
**Post date:** [February 7, 2025, 11:09am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/12 "2025-02-07T11:09:00Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![p0k33m0n](https://forum.openwrt.org/user_avatar/forum.openwrt.org/p0k33m0n/32/113395_2.png) [@p0k33m0n](https://forum.openwrt.org/u/p0k33m0n)\
**Post date:** [February 7, 2025, 11:11am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/14 "2025-02-07T11:11:41Z")

</div>

Try another provider, such as Quad 9.

---

<div class="post-metadata">

**Author:** ![stangri](https://forum.openwrt.org/user_avatar/forum.openwrt.org/stangri/32/58_2.png) [@stangri](https://forum.openwrt.org/u/stangri)\
**Post date:** [February 7, 2025, 7:59pm UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/15 "2025-02-07T19:59:38Z")

</div>

> [@boxman](#):
>
> 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](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](http://cloudflare-dns.com)
> 
> so i dont get any name resolution

This is not https-dns-proxy.

---

<div class="post-metadata">

**Author:** ![p0k33m0n](https://forum.openwrt.org/user_avatar/forum.openwrt.org/p0k33m0n/32/113395_2.png) [@p0k33m0n](https://forum.openwrt.org/u/p0k33m0n)\
**Post date:** [February 9, 2025, 10:38am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/16 "2025-02-09T10:38:09Z")

</div>

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

 ![obraz](https://forum.openwrt.org/uploads/default/original/3X/b/5/b55fd34cb0cd8ffc5c8b87028138699a118b3f64.png)

---

<div class="post-metadata">

**Author:** ![fkl7834456](https://forum.openwrt.org/letter_avatar/fkl7834456/32/5_5575768a8748004e209b776fc1b2916d.png) [@fkl7834456](https://forum.openwrt.org/u/fkl7834456)\
**Post date:** [February 10, 2025, 9:47am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/17 "2025-02-10T09:47:20Z")

</div>

It may be better for you, but not for me 🙂

---

<div class="post-metadata">

**Author:** ![p0k33m0n](https://forum.openwrt.org/user_avatar/forum.openwrt.org/p0k33m0n/32/113395_2.png) [@p0k33m0n](https://forum.openwrt.org/u/p0k33m0n)\
**Post date:** [February 10, 2025, 10:02am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/18 "2025-02-10T10:02:15Z")

</div>

??? 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.

---

<div class="post-metadata">

**Author:** ![fkl7834456](https://forum.openwrt.org/letter_avatar/fkl7834456/32/5_5575768a8748004e209b776fc1b2916d.png) [@fkl7834456](https://forum.openwrt.org/u/fkl7834456)\
**Post date:** [February 10, 2025, 10:24am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/19 "2025-02-10T10:24:30Z")

</div>

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 🙂

---

<div class="post-metadata">

**Author:** ![p0k33m0n](https://forum.openwrt.org/user_avatar/forum.openwrt.org/p0k33m0n/32/113395_2.png) [@p0k33m0n](https://forum.openwrt.org/u/p0k33m0n)\
**Post date:** [February 10, 2025, 10:35am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/20 "2025-02-10T10:35:53Z")

</div>

So don't use it. Bye.

---

<div class="post-metadata">

**Author:** ![fkl7834456](https://forum.openwrt.org/letter_avatar/fkl7834456/32/5_5575768a8748004e209b776fc1b2916d.png) [@fkl7834456](https://forum.openwrt.org/u/fkl7834456)\
**Post date:** [February 10, 2025, 10:42am UTC](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904/21 "2025-02-10T10:42:09Z")

</div>

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

[Next page](https://forum.openwrt.org/t/https-dns-proxy-service-stops-in-version-24-10/223904.md?page=2)
