Closed g055s00 closed 8 months ago
Thank you for providing logs. I'm failing to see what the issue is.
This relates to the comment made in another issue regarding the functioning of https-dns-proxy, which only seems to work after a manual restart.
Thank you for providing logs. I'm failing to see what the issue is.
Here's the problem: resolveip
is not listed as a dependency, so the service is stopping on boot. https://github.com/openwrt/packages/blob/04ac8c177d9ac662790ef5fec9b66cab038c341f/net/https-dns-proxy/files/etc/init.d/https-dns-proxy#L38
https://github.com/openwrt/packages/blob/04ac8c177d9ac662790ef5fec9b66cab038c341f/net/https-dns-proxy/files/etc/init.d/https-dns-proxy#L138
Are you saying you don't have resolveip on your OpenWrt install?
This relates to the comment made in another issue regarding the functioning of https-dns-proxy, which only seems to work after a manual restart.
In the non-working-after-restart state, please provide the output of:
logread -ehttps
service https-dns-proxy status
Are you saying you don't have resolveip on your OpenWrt install?
Yes, that's correct. I didn't have this package. After installing it, everything works fine now.
Are you saying you don't have resolveip on your OpenWrt install?
Should it be there? This package is not listed in the manifest file.
Are you saying you don't have resolveip on your OpenWrt install?
Should it be there? This package is not listed in the manifest file.
My understanding is that it's included with all systems, but you're right, there should be a dependency, I'll push a fix this weekend!
Thank you for pretty much solving the issue and presenting the solution!
Maintainer: @stangri Environment: mt7621, 23.05.2
Description: At device startup, the dnsmasq configuration reverts to the backup due to https-dns-proxy service stopping. To update the configuration, https-dns-proxy needs to be manually restarted.
The status of https-dns-proxy and dnsmasq after reboot:
https-dns-proxy restart: