To support this new functionality, we migrated the list storage from individual files in /etc/pihole to a new gravity database in the same directory. Blocklists, blacklist and whitelist can all be individually enabled/disabled.

Groups can be created and block lists, blacklist, and whitelist can be applied to groups. This is something that users have been asking for for a long time, and we are proud to be finally able to offer this awesome feature. Quite a lot, actually, but we’ll go over the bigger things briefly here. Read all the notes before you make the jump, and make a backup! What’s new? Once you move from 4.x to 5.0, there is no way to go back you will need to restore from a backup. There are many fundamental changes between Pi-hole 4.x and 5.0 – as such, this is strictly a one way operation.

After a successful beta testing and development period (many thanks to the beta testers!), we are pleased to announce the release of 5.0 for general availability! Important notice I think it is just a matter of port forwarding, but because i am already forwarding 80 and 443 to my original instance, what do i have to do to either allow for a secondary instance on my router, or updating the vm instance from 80 and 443 to 80008 and 444 (or something like that?įurther, i can get to the new instance using my internal address of.

I am still able to get to my original (and still working) instance on.

My issue is, after updating NGINX and DuckDNS entries, i still cannot work out how to get to my dashboard using the standard. I then took a backup of my current (working) HA and restored it to the new virtual env.Įventually i would like to host a second instance from the proxmox nuc as a dev instance, but that will come later. I have recently purchased a NUC, installed Proxmox and setup Hassio using the single line command by whiskerz007 (worked out great). As background, i have a fully configured instance of Hassio running on an RPi, which sometimes slows down due to RPi resources.

Nxfilter and pihole