Selfhosted

42738 readers

487 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

216

Introducing Pi-hole v6 (pi-hole.net)

submitted 4 days ago by [email protected] to c/selfhosted

20 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 12 points 4 days ago* (last edited 4 days ago) (1 children)

Nice!

Upgrade went smoothly on docker, with some neat new additions. There's new filter options in the query log. There's a bunch of new metrics under Settings > System (enable 'advanced' in the top right). And overall there seems to be many more settings available under System > All Settings. For example you can easily set the TTL for blocked responses (this was a setting burried in config files before, I was looking for it like 2 weeks ago).

If you don't use/set a password in pihole, or you set one via .env variables; you'll probably have to reset it with the command:

sudo docker exec <container_name> sudo pihole setpassword <your password here>

(empty for no password)

/edit; seems that was a temporary solution.

These env variables have changed:

Was: webpassword=<your password>

DNS1=<upstream1>

DNS2=<upstream2>

Now: FTLCONF_dns_upstream=<upstream1;upstream2>

FTLCONF_webserver_api_password=<your password here>

[–] [email protected] 3 points 3 days ago

Hey, having all of this inside a docker-compose.yml file is even better.