Pi-hole https://pi-hole.net Network-wide Ad Blocking Tue, 17 Feb 2026 20:54:41 +0000 en-US hourly 1 https://wp-cdn.pi-hole.net/wp-content/uploads/2016/12/cropped-Vortex-R-32x32.png Pi-hole https://pi-hole.net 32 32 Pi-hole FTL v6.5, Web v6.4.1 and Core v6.4 Released! https://pi-hole.net/blog/2026/02/17/pi-hole-ftl-v6-5-web-v6-4-1-and-core-v6-4-released/ Tue, 17 Feb 2026 20:54:38 +0000 https://pi-hole.net/?p=82971 Read more]]> As always, please read through the changelogs before updating with pihole -up

Don’t forget, you can use Teleporter to export your configuration. It can be found under the settings menu of the web interface or on the command line with pihole-FTL --teleporter

This release has also been tagged on Docker as 2026.02.0

Highlights

Security fixes

Two security vulnerabilities in the web interface have been patched in this release.

Performance improvements

Faster startup (FTL #2725)

FTL now imports historical queries from the database asynchronously on startup. Previously, DNS resolution was blocked until the entire query history had been loaded into memory. Now, FTL begins accepting DNS queries immediately and imports history in a dedicated background thread. The garbage collector is held off until the import is complete to ensure data consistency.

Low-memory hardware optimizations (FTL #2757)

A new database.forceDisk configuration option forces FTL’s in-memory SQLite3 database to live on disk instead of in RAM. This can notably reduce FTL’s memory footprint, which is beneficial on resource-constrained hardware such as older Raspberry Pi models. On NVMe-backed systems no measurable performance difference was observed, though some slowdown may be seen on slower storage.

Faster gravity updates (FTL #2710)

Several cumulative efficiency gains have been applied to the main domain validation loop that runs during pihole -g. While each individual improvement is modest, they add up across every entry in your blocklists and allowlists:

  • A lookup table now validates domain characters using a single comparison per character, replacing multiple branching comparisons
  • IP address testing is short-circuited: IPv4 tests only run if the token starts with a digit, and IPv6 tests only run if a colon is present within the first 5 characters
  • The unicode BOM check is now performed once per file rather than once per line

In testing with ~5 million domains across several lists, gravity update time dropped from ~27s to ~23s (roughly a 16% reduction in real time, and ~22% reduction in CPU time).

FTL v6.5

What’s Changed

  • Tweak undocumented wait-for option subtly by @DL6ER in #2707
  • update gravity – improve domain validation processing speed by @rrobgill in #2710
  • Update embedded SQLite3 to 3.51.1 by @DL6ER in #2731
  • Update embedded dnsmasq to 2.92rc1 by @DL6ER in #2730
  • Fix documentation – Do not use equal sign with pihole-FTL --config command by @rdwebdesign in #2736
  • Add dns.cache.rrtype by @Manakuremati in #2740
  • Enhancements to the documentation markdown generator by @PromoFaux in #2741
  • Network Overview – obtain MAC and hostname from dhcp.leases by @rrobgill in #2727
  • fix: make get_domains parameters optional by @tien in #2278
  • Escape unprintable characters in invalid host names by @DL6ER in #2601
  • Implement better allOf handling in API verifier by @DL6ER in #2745
  • Update build containers to Alpine 3.23 by @DL6ER in #2743
  • Add option to hide network connection errors by @DL6ER in #2749
  • Harden default Content Security Policy (CSP) by @Erasure5959 in #2754
  • Fix computation of NTP server’s root delay by @DL6ER in #2760
  • Teleporter: Fix for custom gravity.db path by @DL6ER in #2758
  • Upgrade embedded Lua to 5.5 by @DL6ER in #2626
  • Add missing [forwarded] property in GET /api/history/database by @DL6ER in #2750
  • Update SQLite3 to 3.51.2 by @DL6ER in #2761
  • Low-memory hardware optimizations by @DL6ER in #2757
  • Reduce startup delay by @DL6ER in #2725
  • home.arpa and internal TLDs may be non-local without revServer by @DL6ER in #2772

New Contributors

Full Changelog: v6.4.1…v6.5

Web v6.4.1

What’s Changed

  • Set the end date for live query update to end of epoch by @rrobgill in #3677
  • Improve initial loading of Query Log by @DL6ER in #3715

Full Changelog: v6.4…v6.4.1

Core v6.4

What’s Changed

Full Changelog: v6.3…v6.4

]]> Pi-hole FTL v6.4, Web v6.4 and Core v6.3 Released! https://pi-hole.net/blog/2025/11/27/pi-hole-ftl-v6-4-web-v6-4-and-core-v6-3-released/ Thu, 27 Nov 2025 20:00:26 +0000 https://pi-hole.net/?p=80887 Read more]]> As always, please read through the changelogs before updating with pihole -up

Don’t forget, you can use Teleporter to export your configuration. It can be found under the settings menu of the web interface or on the command line with pihole-FTL --teleporter

This release has also been tagged on Docker as 2025.11.1

Highlights

Performance & Optimization

  • FTL Optimizations: We’ve improved string processing, memory management, and enabled new compiler flags (such as -funroll-loops) to make FTL faster and more efficient (#2571).
  • Reduced Locking: We’ve reduced DNS resolver locking during database interactions (#2700).

User Interface & Experience

  • TOTP Autofill: Logging in with 2FA is now smoother. The TOTP input field now supports autocomplete="one-time-code", allowing browsers and password managers to automatically suggest the code (#3658).
  • “All Time” Query Log: The “All Time” date range in the Query Log now accurately reflects the earliest timestamp in your database, giving you a true historical view (#3657, #2706).
  • Optional Colour Output: The Gravity API now defaults to plain text output, only sending ANSI colour codes when explicitly requested (?color=true). This fixes issues for API consumers that don’t handle escape codes well (#2718).

API & Networking

  • Extended Hardware Addresses: The API now correctly handles hardware addresses longer than 48 bits (e.g., InfiniBand), ensuring they are displayed and managed correctly (#2724).
  • Partial Regex Matching: The search API now supports simple partial matching for regex, making it easier to find domains within your blocklists (#2705).
  • Security: We’ve added rate-limiting for TOTP validation (max 1 attempt/second) to prevent brute-force attacks on 2FA (#2719).

FTL v6.4

What’s Changed

  • Fix API specs and example for dns.upstreams in config.yaml by @rdwebdesign in #2696
  • gravity update – silently discard unicode BOM if present by @rrobgill in #2702
  • Update embedded SQLite to 3.51.0 by @DL6ER in #2704
  • Get earliest query timestamp from database by @PromoFaux in #2706
  • Increase buffer length for query string by @mwoolweaver in #2709
  • Reduce DNS resolver locking during database interaction by @DL6ER in #2700
  • Make colour output optional in streaming gravity API call by @PromoFaux in #2718
  • api/dhcp/leases Allow for hwaddr > 48 bits by @rrobgill in #2724
  • Add rate-limiting for TOTP validation by @DL6ER in #2719
  • Implement simple partial matching for regex in /api/search/{domain} by @DL6ER in #2705
  • Performance optimizations: string processing, memory management, and compiler flags by @Copilot in #2571
  • Fix authentication redirect when webhome is / (fixes #2518) by @averyvigolo in #2610
  • Reduce database locking and add timing debug setting by @DL6ER in #2688

New Contributors

Full Changelog: v6.3.3…v6.4

Web v6.4

What’s Changed

  • Start using commented tags for editorconfig-checker by @yubiuser in #3643
  • Remove some unused code (leftover from v5) by @rdwebdesign in #3636
  • Make sure the table is redrawn after the dnssec API call returns by @rdwebdesign in #3645
  • Add hint that partial matching may not return all possible results by @DL6ER in #3654
  • Enable one-time code autofill for TOTP input by @sebastianlivoni in #3658
  • Set “All Time ” range for query log datepicker based on Database ranges (moment) by @PromoFaux in #3657
  • Request ANSI colour codes when calling gravity API by @PromoFaux in #3662

New Contributors

Full Changelog: v6.3…v6.4

Core v6.3

What’s Changed

New Contributors

Full Changelog: v6.2.2…v6.2.3

]]> Pi-hole FTL v6.3, Web v6.3 and Core v6.2 Released! https://pi-hole.net/blog/2025/10/25/pi-hole-ftl-v6-3-web-v6-3-and-core-v6-2-released/ Sat, 25 Oct 2025 11:52:23 +0000 https://pi-hole.net/?p=80848 Read more]]> As always, please read through the changelogs before updating with pihole -up

Don’t forget, you can use Teleporter to export your configuration. It can be found under the settings menu of the web interface or on the command line with pihole-FTL --teleporter

This release has also been tagged on Docker as 2025.10.0

Highlights

Security & TLS Enhancements

Shorter validity for self-signed TLS certificate (#2463) – The default validity period for self-signed TLS certificates has been reduced, aligning with modern security best practices and ensuring compatibility with Apple devices. To compensate for the shorter validity, automatic renewal has been implemented. Certificates now default to a 47-day validity period (configurable via webserver.tls.validity) and automatically renew when nearing expiration.

Improved Content Security Policy (#2575) – Improved default CSP headers provide better protection against XSS attacks while maintaining functionality.

Security Advisories:

Thank you to the folks who responsibly disclosed potential vulnerabilities since our last realease. Details of which can be read at the following links:

Network & DNS Improvements

Smart Interface Detection (#2456, #2607) – FTL now automatically detects the appropriate DNS interface when dns.interface is empty in pihole.toml, eliminating manual configuration in most scenarios.

Netlink ARP Cache Handling (#2600) – Replaced external ip neigh show calls with internal netlink-based communication, dramatically improving performance and reducing resource usage. This addresses “database locked” issues seen in some environments.

Special Domain Handling (#2474) – Added support for .internal domain blocking (following RFC draft-davies-internal-tld-03), preventing these queries from being sent to upstream DNS servers while still allowing local resolution.

DNS Localization (#2524) – New dns.localise configuration option provides better control over DNS query handling.

IPv6 DHCP Support (#2554) – Enhanced the DHCP API to properly support IPv6 addresses and configurations.

Platform & Installation

Alpine Linux Support (pi-hole/pi-hole#6275) – Full native support for Alpine Linux has been added, including proper package management with apk, OpenRC init system support, and comprehensive testing. This expands Pi-hole’s reach to lightweight container environments and minimal installations.

User Interface & Experience

CLI Autocomplete (#2593, pi-hole/pi-hole#6376) – Added bash-style completion support for pihole-FTL commands, making configuration much more user-friendly. Tab completion works for the entire --config path and suggests appropriate values.

Web Interface Improvements (web#3530, web#3551, web#3533, web#3592, FTL#2645, FTL#2647, FTL#2644, web#3622) – Many small improvements: better visualization of DNS metrics, improved query log handling, enhanced gravity output with colors, refined button styling for blocked/allowed domain actions, improved load average detection and better system information gathering.

Configuration & Management

Advanced Web Server Options (#2635) – New webserver.advancedOpts configuration for fine-tuning web server behavior.

Enhanced API Endpoints (#2530, #2632, #2466) – Multiple API improvements including better error handling, optional restart parameters, and enhanced response formatting.

Web documentation for the config file – https://docs.pi-hole.net/ftldns/configfile/ – we have added some automation and a Python script to parse the latest pihole-FTL config file and to keep the documentation up to date on the web

Performance & Reliability

Updated Core Components (#2544, #2576, #2592, #2570, #2587, #2603, #2614, #2621, #2579):

  • SQLite3 updated to 3.50.4 for better database performance
  • dnsmasq updated to v2.92test21 with latest fixes
  • CivetWeb updated for improved web server functionality
  • Migrate TOML library to tomlc17 (tomlc99 has been marked as deprecated)

Memory Management (#2617) – Improved memory handling throughout the codebase to reduce resource usage and improve stability.

Database Resilience (#2605, #2602, #2646) – Enhanced gravity database handling with custom SQLite busy callbacks and better error recovery.

Bug Fixes & Stability

  • Fixed PTR query handling for .localhost domains (#2517)
  • Resolved DHCP string processing issues (#2519)
  • Fixed cache-optimizer query display in logs (#2619)
  • Improved NTP IPv6 crash handling (#2569)
  • Better foreign fork PR handling in CI (#2543)
  • Enhanced debug output and logging throughout (#2594)

Diagnostics

Improved Debug Output (#2600, #2594) – More comprehensive debug information across networking, ARP processing, and system diagnostics.

Full Release Notes can be found below.

FTL v6.3

What’s Changed

New Contributors

Full Changelog: https://github.com/pi-hole/FTL/compare/v6.2.3…v6.3

Core v6.2

What’s Changed

New Contributors

Full Changelog: https://github.com/pi-hole/pi-hole/compare/v6.1.4…v6.2

Web v6.3

What’s Changed

New Contributors

Full Changelog: https://github.com/pi-hole/web/compare/v6.2.1…v6.3

]]> Compromised Donor Emails: A post-mortem https://pi-hole.net/blog/2025/07/30/compromised-donor-emails-a-post-mortem/ Wed, 30 Jul 2025 23:16:02 +0000 https://pi-hole.net/?p=76152 Read more]]> What Information Was Exposed (and What Was Not)

The breach is limited to names and email addresses provided during the donation process, when using the form at https://pi-hole.net/donate (now fixed…)

It is important to mention that we don’t have access to or store any credit card numbers or verified names or addresses or phone numbers. Any PII is maintained directly by the card processors, Stripe or PayPal. We make it clear in the donation form that we don’t even require a valid name or email address, it’s purely for users to see and manage their donations.

It is also important to note that Pi-hole the product is categorically not the subject of this breach. There is no action needed from users with a Pi-hole installed on their network

What Happened

We first became aware of the issue on Monday 28th July, when we started to receive emails suggesting that we were facing a possible data breach

And a couple of Reddit posts let us know about the same thing.

And a post on our Discourse forum….

The email addresses that people were receiving these emails to were emails that had been used exclusively when leaving us a donation.

How could this be? Had someone gotten access to the admin page of our WordPress site? Were we running some out of date plugin that had a known vulnerability against it? Had the payment providers suffered a breach?

One of many threads we pulled at was checking the user account list. Our hypothesis leaning toward an integration with a plugin creating user accounts, as Dan commented on Reddit. (Spoiler alert… the post has been edited with the actual reason)

Checking with the plugin authors

So, we reached out to the authors of the plugin we use for our donations page (GiveWP) to see if they knew of anything that might be the cause of this. Nobody else had reported anything similar

The next day, we discovered that the donation plugin we use, GiveWP, had released an update with the description: “Security: Addressed an issue with donor information visibility.”

Further investigation revealed a public issue had been filed on their GitHub repository by another user, detailing the vulnerability. (For transparency, we have archived a copy of the report here).

The names and email addresses of anyone that had ever donated via our donation page was there for the entire world to see (provided they were savvy enough to right click->View page source)

Within a couple of hours of this report, they had patched the bad code and released 4.6.1

While the patch was released quickly, we were concerned by the 17.5-hour delay (“4 business hours”…) between the critical security fix and any official notification from the GiveWP team. However, In our view, their public statement did not sufficiently address the potential impact of exposing donor names and email addresses.

And with that, the conversation is effectively shut down.

And yes, while no billing or payment info was at risk, they really downplay the impact that the accidental reveal of names and email addresses can have. (To quote: “there’s no evidence that the exposure of emails that happened here has been linked to any real-world exploitation”)

If we’re being entirely honest, the response from the GiveWP team has been disappointing.

Where we’re left

We take full responsibility for the software we deploy. We placed our trust in a widely-used plugin, and that trust was broken. This incident exposed our donors’ information and put our reputation at risk. This is an unacceptable outcome.

While there is no way for us to have forseen this happening, we cannot apologise enough to anyone of our donors who have seen an increase in spam due to this. We put our trust in a WordPress plugin, and they broke that trust – in turn putting our own reputation at risk.

It sucks, and it’s not a position we ever thought we’d be in, but here we are. We hope that we can gain back the trust of those affected by this.

]]> Pi-hole Core v6.1.4 Released https://pi-hole.net/blog/2025/07/14/pi-hole-core-v6-1-4-released/ Mon, 14 Jul 2025 21:17:29 +0000 https://pi-hole.net/?p=75948 This is a bugfix release for the core Pi-hole code.

Fixes

  • Fix issue where web interface cannot run gravity by @PromoFaux in #6345
  • Fix pihole api command by not setting the some variabes as readonly by @PromoFaux in #6346

]]> Pi-hole Core v6.1.3 Released https://pi-hole.net/blog/2025/07/14/pi-hole-core-v6-1-3-released/ Mon, 14 Jul 2025 14:13:49 +0000 https://pi-hole.net/?p=75872 This is a bugfix release for the core Pi-hole code.

Fixes

  • Prevent gravity from failing due to an empty shell variable. #6191
    This fixes a case where calls to pihole -g failed during list downloads.
  • Require privileged status (root or sudo) for all user calls to pihole. #6312
    This fixes cases where users are unable to change or update the admin password.
  • Exit installation if FTL binary can not be downloaded. #6316
    Abort update if FTL branch does not exist. #6329
    These fix cases where the installation did not fully complete or an update left the installation with mismatched binary and repository versions. Both fixes contributed by @MichaIng
  • Restore pihole -q function. #6284
    This fixes a case where running a query immediately failed with an error message for an unknown file.

Miscellaneous Fixes and Improvements

  • Display output from FTL commands in color on the terminal. #6314
  • Add note to final installation dialog box showing users where to find instructions for allowing a user to run Pi-hole commands without authentication. #6152
  • Allow pihole tail to search for strings beginning with the hyphen character. #6318 Contributed by @rrobgill
  • Do not update the package cache on updates. #6282
  • Improve default route detection in debugging process. #6303 Contributed by @rrobgill
  • Improve detecting loopback interfaces in the installer. #6269 Contributed by @deHakkelaar

]]> Pi-hole FTL v6.2.3 Released https://pi-hole.net/blog/2025/06/12/pi-hole-ftl-v6-2-3-released/ Thu, 12 Jun 2025 15:37:38 +0000 https://pi-hole.net/?p=75455 Read more]]> We have now released FTL v6.2.3.

This patch release contains fixes for almost all reported bugs (most importantly, it fixes a logging regression where types are missing from pihole.log as well as a crash in filter_servers() deep down in dnsmasq code).

Note:

If you had switched to FTL v6.1 or a different branch following the previous posts, you may now switch back the released version pihole checkout ftl master should get you to v6.2.3.

There is one remaining known issue about the behavior of server=/example.com/1.2.3.4 having changed which we are still working on with the maintainers of dnsmasq.

FTL Changes

Full Changelog: v6.2.2...v6.2.3

Join the Community

Pi-hole thrives thanks to our vibrant and supportive community. Whether you’re looking to share your experience, get advice, or stay informed about the latest updates, there’s a place for you. Join the conversation on our official forum or connect with fellow users on our subreddit. We look forward to welcoming you!

Thank You for Your Support

We want to express our heartfelt thanks to everyone who has supported Pi-hole throughout the years.

Your community contributions and donations are the lifeblood of this project, allowing us to maintain and continually improve Pi-hole while keeping it free for everyone. If you’d like to contribute to our ongoing efforts, please consider donating through our official donation page. Every contribution, big or small, makes a significant difference in helping us deliver the best project that we can.

Thank you for being part of the Pi-hole community!

]]> Pi-hole FTL v6.2.2 Released https://pi-hole.net/blog/2025/06/06/pi-hole-ftl-v6-2-2-released/ Fri, 06 Jun 2025 11:42:20 +0000 https://pi-hole.net/?p=75358 Read more]]> Following on from our previous post, we have now released FTL v6.2.2, which contains fixes for some underlying bugs in dnsmasq that should now resolve the majority of cases where we have seen crashes. We have also downgraded the embedded version of SQLite from 3.50.0, as this was also causing issues.

Full details and converation around the issues can be found in pi-hole/FTL#2473

If you had switched to FTL v6.1 following the previous post, you may now switch back the released version pihole checkout ftl master should get you to v6.2.2

There are still a couple of outliers (pi-hole/FTL#2494, and pi-hole/FTL#2496)  – though there is a fix on the FTL branch fix/filter_servers which should resolve those, though it is pending feedback. If you find that 6.2.2 still crashes for you, you are invited to try above branch with pihole checkout ftl fix/filter_servers and provide feedback on the above mentioned issues, or via our Discourse forum.

FTL Changes

This release addresses crashes reported in #2473 #2475 #2481 and friends.

What’s Changed

Full Changelog: v6.2...v6.2.2

Join the Community

Pi-hole thrives thanks to our vibrant and supportive community. Whether you’re looking to share your experience, get advice, or stay informed about the latest updates, there’s a place for you. Join the conversation on our official forum or connect with fellow users on our subreddit. We look forward to welcoming you!

Thank You for Your Support

We want to express our heartfelt thanks to everyone who has supported Pi-hole throughout the years.

Your community contributions and donations are the lifeblood of this project, allowing us to maintain and continually improve Pi-hole while keeping it free for everyone. If you’d like to contribute to our ongoing efforts, please consider donating through our official donation page. Every contribution, big or small, makes a significant difference in helping us deliver the best project that we can.

Thank you for being part of the Pi-hole community!

 

]]> PSA: FTL v6.2 / FTL v6.2.1 crashes workaround https://pi-hole.net/blog/2025/06/02/psa-ftl-v6-2-ftl-v6-2-1-crashes-workaround/ Mon, 02 Jun 2025 12:08:16 +0000 https://pi-hole.net/?p=75319 Read more]]> We are currently aware of FTL crashing with a segmentation fault on some systems – more detailed information about this issue can be followed on Github, here: https://github.com/pi-hole/FTL/issues/2473.

If you are currently affected by this issue, the easiest way to get things back up and running is to downgrade FTL to the previous version. There are instructions in the above Github thread that describe the steps to do so, however to make the process of downgrading more straightforward, we have created a special branch named release/v6.1 and you will be able to switch to it with the following command:

sudo pihole checkout ftl release/v6.1

Once we have gotten to the bottom of the issue, we will release a new version of FTL and announce it in all the usual places.

Huge apologies to anyone affected by this – and thank you for those that have reported the issue to us.

]]> Pi-hole FTL v6.2, Web v6.2 and Core v6.1 Released! https://pi-hole.net/blog/2025/05/30/pi-hole-ftl-v6-2-web-v6-2-and-core-v6-1-released/ Fri, 30 May 2025 22:27:22 +0000 https://pi-hole.net/?p=75280 Read more]]> As always, please read through the changelogs before updating with pihole -up. (A new tag for docker image will follow shortly!)

Don’t forget, you can use Teleporter to export your configuration. It can be found under the settings menu of the web interface or on the command line with pihole-FTL --teleporter

FTL Changes

What’s Changed (FTL v6.2)

  • Fix minor spelling mistake in API docs by @PromoFaux in #2399
  • fix: batch request body spec by @tien in #2389
  • fix: make getAuth security optional by @tien in #2388
  • fix: incorrect session field requirements by @tien in #2387
  • Add privacy_level to /padd endpoint by @yubiuser in #2402
  • Parameter is called length not n in GET /queries by @DL6ER in #2407
  • Fix duplicate web port information output in FTL startup by @PromoFaux in #2410
  • Fix logfile warning port length truncation (bug #2408) by @rrobgill in #2409
  • Remove dns.watch from upstream DNS server list by @rdwebdesign in #2411
  • Prevent home.arpa queries from being upstreamed. RFC 8375 by @rrobgill in #2405
  • Fix redirecting when redirecting from /admin/ to /admin/login and back by @DL6ER in #2415
  • Move manual filtering to FTLs file parsing by @DL6ER in #2381
  • Various small fixes by @DL6ER in #2392
  • Update embedded dnsmasq to v2.92test2 by @DL6ER in #2417
  • Fix signedness error in the NTP total round-trip delay calculation by @DL6ER in #2420
  • Use webhome variable also on the API documentation page by @DL6ER in #2406
  • Report RFC6598 shared address space as “Carrier-Grade NAT” by @rrobgill in #2423
  • Fix mishanding of CONF_UINT16 config options by @shawnanastasio in #2426
  • Feature/fix yocto cross build by @rehsack in #2425
  • Update embedded civetweb by @DL6ER in #2428
  • Check for existing NTP client when starting FTL by @DL6ER in #2416
  • Validate received NTP packets for version and server synchronisation by @rrobgill in #2431
  • Use CODEOWNERS instead of deprecated dependbot/reviewers by @yubiuser in #2437
  • Modify how we use xxd to compile assets into the FTL binary by @DL6ER in #2446
  • Update dnsmasq to v2.91test5 by @DL6ER in #2433
  • Update embedded SQLite3 to 3.49.2 by @DL6ER in #2447
  • Gravity: support for arbitrary HOSTS-like list formats by @DL6ER in #2439
  • Set dns.interface to eth0 by default by @yubiuser in #2448
  • Update embedded dnsmasq by @DL6ER in #2457
  • Adjust write_to_file function to include the CA certificate by @nathansmeal in #2465
  • Update SQLite to 3.50.0 by @DL6ER in #2469

New Contributors

Full Changelog: v6.1...v6.2

Web Changes

What’s Changed (Web v6.2)

New Contributors

Full Changelog: v6.1...v6.2

Core Changes

What’s Changed (Core v6.1)

  • build gravityDBfile_default like the other variables by @mwoolweaver in #6133
  • Add CentOS 10 to test suite by @yubiuser in #6126
  • Ensure gravity_Cleanup() checks the correct directory by @mwoolweaver in #6131
  • Add recommended fields to the deb package by @yubiuser in #6054
  • Add webserver log to piholeLogFlush.sh by @jacklul in #6049
  • Update update.sh, updatecheck.sh and uninstall.sh to honour pihole.to… by @nexusgoblin in #5981
  • Move list parsing entirely into FTL by @DL6ER in #6105
  • Remove no-longer-needed pihole sudoers file by @PromoFaux in #6143
  • versions file should readable by others (make pihole -v work for non-root users) by @yubiuser in #6002
  • Reduce code duplication in piholeLogFlush by @PromoFaux in #6148
  • Add ON DELETE CASCADE to FOREIGN KEY REFERENCES in gravity.db by @DL6ER in #6113
  • Install on IPv6-only/DNS64/NAT64 system by @rrobgill in #6144
  • Treat FTL return data as strings – part II by @yubiuser in #6184
  • Remove duplicated code checking if adlist domain is blocked locally by @yubiuser in #6183
  • Fix gravity waiting forever for DNS by @yubiuser in #6196
  • Remove check for supported OS by @yubiuser in #6206
  • Remove unused $target from gravity by @yubiuser in #6192
  • Remove reference to telnet and chronometer in README by @rrobgill in #6188
  • Add Fedora 42 to tests by @darkexplosiveqwx in #6177
  • Extend .gitignore by @darkexplosiveqwx in #6215
  • Use CODEOWNERS instead of deprecated dependbot/reviewers by @yubiuser in #6213
  • Set dns.interface during installation by @yubiuser in #6216
  • Allow alternative cron daemons on Debian by @z0rc in #6180
  • Fix API logic in api.sh by @yubiuser in #6193
  • Do not try to upgrade gravity if it does not exist by @yubiuser in #6218
  • All gravity related files and dirs should be owned by pihole:pihole by @yubiuser in #6186
  • Give FTL 60 seconds for graceful shutdown by @yubiuser in #6187
  • Use shell parameter expansion to split http_code and payload for api.sh by @dschaper in #6230
  • Change FTLcheckUpdate to use api.github.com and jq to retrieve tag_name by @rdwebdesign in #6229
  • Update get_available_interfaces() to correctly filter loopback device (lo) by @PiotrTyrakowski in #6236
  • Allow simple pihole api output, containing only the JSON payload by @rdwebdesign in #6096
  • Function gravity_CheckDNSResolutionAvailable() should return 0 if DNS resolution is available by @rdwebdesign in #6240
  • Use a more general method to determine whether systemd is the init system by @DL6ER in #6043
  • Use PID1 to determine which command to use when toggeling services by @yubiuser in #6245
  • Allow to get API URL from local.api.ftl even if DNS port has changed by @yubiuser in #6252

New Contributors

Full Changelog: v6.0.6...v6.1

Join the Community

Pi-hole thrives thanks to our vibrant and supportive community. Whether you’re looking to share your experience, get advice, or stay informed about the latest updates, there’s a place for you. Join the conversation on our official forum or connect with fellow users on our subreddit. We look forward to welcoming you!

Thank You for Your Support

We want to express our heartfelt thanks to everyone who has supported Pi-hole throughout the years.

Your community contributions and donations are the lifeblood of this project, allowing us to maintain and continually improve Pi-hole while keeping it free for everyone. If you’d like to contribute to our ongoing efforts, please consider donating through our official donation page. Every contribution, big or small, makes a significant difference in helping us deliver the best project that we can.

Thank you for being part of the Pi-hole community!

 

]]>