I can’t add/remove files to properly configure pi-hole, after " This computer " everything is in read-only, even the unbound & pi-hole file, so i’m blocked here. Any ideas of what can be done to give me permissions to access all the files and write?
What steps did you do before trying do write to files?
I don’t totally remember, but I know that I downloaded pi-hole normally with apt, then I get on the admin panel and I put a AppVM ip in " Client group " to test if i’m still seeing ads while using random website on Firefox.
The problem is that i’m still seeing ads on that AppVM, so it doesn’t work.
What I would like to modify was the Qubes Firewall script, because from google I saw that it could be the issue.
I tried both chain :
AppVM => sys-firewall => sys-pihole => sys-net
AppVM => sys-pihole => sys-firewall => sys-net
edit : After using sudo nano, i’ve been setup the Unbound server correctly. But i’m still seeing ads.
Thanks for that, but reinstalling everything would be a pain for me. I already have a StandaloneVM with pi-hole and unbound server, both seems working correctly the problem is that i’m still seeing ads on another ProxyVM that use the standaloneVM as network.
I installed Pi-hole & Unbound, I configured the pi-hole.conf file in /etc/unbound/unbound.conf.d/pi-hole.conf. Then manually set the ip 127.0.0.1#5335 on pi hole web server.
Should I open another post about my issue on pi-hole?
I don’t think you have said how you created the stand alone, or
exactly what you have done to it.
You haven’t said how you installed and configured unbound.(I think.)
I think you have resolved the issue about not being able to edit files,
although your original post suggested that you could edit nothing,
which suggests that somewhere along the way you changed the ownership of
every thing under / .
Either that, or what you meant was, I cant edit these files that I want
Assuming that you are now able to edit files (using sudo), restart the
stand alone. Look in the logs using journalctl for any warnings or
errors, particularly relating to pihole and unbound.
Use systemctl status X to check on what is happening.
Use ss -lnp to see what is listening and on what ports.
Report back any errors you find, and what you see about unbound and
I never presume to speak for the Qubes team.
When I comment in the Forum or in the mailing lists I speak for myself.