Saw an user with this issue where /etc/resolv.dnsmasq.conf ended up being empty for some reason ... I think because of some old ".ynh" file while in fact never gets deleted nor recreated ...
Solution
We already detect if /etc/resolv.dnsmasq.conf is suspiciously empty, which breaks dnsmasq, so let's regenerate it with what the script from yunohost does (basically cat /list/of/resolvers | shuf > $conf)
Problem
Saw an user with this issue where /etc/resolv.dnsmasq.conf ended up being empty for some reason ... I think because of some old ".ynh" file while in fact never gets deleted nor recreated ...
Solution
We already detect if /etc/resolv.dnsmasq.conf is suspiciously empty, which breaks dnsmasq, so let's regenerate it with what the script from yunohost does (basically
cat /list/of/resolvers | shuf > $conf)PR Status
Yolo