Https-dns-proxy sometimes stops and cutting the all internet off

bosukes · March 22, 2026, 8:50am

Sometimes this happens for no reason at all. I wake up and see internet is gone. Turns out https-dns-proxy is stopped. Which cuts off the internet for some reason.

root@OpenWrt:~# ubus call system board
{
	"kernel": "6.12.74",
	"hostname": "OpenWrt",
	"system": "MediaTek MT7621 ver:1 eco:3",
	"model": "TP-Link Archer AX23 v1",
	"board_name": "tplink,archer-ax23-v1",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "25.12.1",
		"firmware_url": "https://downloads.openwrt.org/",
		"revision": "r32768-b21cfa8f8c",
		"target": "ramips/mt7621",
		"description": "OpenWrt 25.12.1 r32768-b21cfa8f8c",
		"builddate": "1773711117"
	}
}

ncompact · March 22, 2026, 8:55am

See if you can get "https-dns-proxy" to restart with a hotplug event:

bosukes · March 22, 2026, 9:10am

Or should I just use something else than https-dns-proxy? Is it better alternatives?

ncompact · March 22, 2026, 9:13am

You can add a little log to understand what's happening now (when the interface restarts) related to the issue you're having...

github.com/openwrt/packages

net/https-dns-proxy/files/etc/init.d/https-dns-proxy

fb591471c


      
          		. "${IPKG_INSTROOT}/lib/functions/network.sh"
          		network_flush_cache
          		network_find_wan wan
          		wan="${wan:-wan}"
          		if [ -n "$procd_trigger_wan6" ]; then
          			network_find_wan6 wan6
          			wan6="${wan6:-wan6}"
          		fi
          		output "Setting trigger${wan6:+s} for $wan ${wan6:+${wan6} }"
          		for i in $wan $wan6; do
          			procd_add_interface_trigger "interface.*" "$i" "/etc/init.d/${packageName}" reload 'on_interface_trigger' && output_ok || output_fail
          		done
          		output '\n'
          		procd_add_config_trigger "config.change" "$packageName" "/etc/init.d/${packageName}" reload 'on_config_change'
          	fi
          }
          
          service_started() { [ -n "$force_dns" ] && procd_set_config_changed firewall; }
          service_stopped() { [ -n "$force_dns" ] && procd_set_config_changed firewall; }
          restart() { reload "$@"; }

It's a matter of personal preference; you have to decide what you want to use.

else if you want to switch from custom manual configurations (but as I said it's a matter of personal taste).

fantom-x · March 22, 2026, 8:43pm

“stubby”. I had the same stability issues with https-dns-proxy.