Skip to content

Add validation for ntp.sync.server#2667

Merged
DL6ER merged 1 commit into
developmentfrom
fix/ntp_sync_server_ip_domain
Oct 31, 2025
Merged

Add validation for ntp.sync.server#2667
DL6ER merged 1 commit into
developmentfrom
fix/ntp_sync_server_ip_domain

Conversation

@DL6ER

@DL6ER DL6ER commented Oct 26, 2025

Copy link
Copy Markdown
Member

What does this implement/fix?

Validation should ensure that ntp.sync.server can only be either a valid IP or a hostname.

Fixes #2660

Note: I'm opening this as draft because - right now - the resulting crash was not reproducible by me. It is impossible on this branch, however, I'd still like to also fix the underlying issue in case the user responds with the requested backtrace. The actual crash is fixed by #2684

This PR also adds printing which NTP service has been detected when FTL decides not to launch its own NTP server. This makes it easier to see what needs to be disabled in order to test NTP related functionality on a given machine.


Related issue or feature (if applicable): N/A

Pull request in docs with documentation (if applicable): N/A


By submitting this pull request, I confirm the following:

  1. I have read and understood the contributors guide, as well as this entire template. I understand which branch to base my commits and Pull Requests against.
  2. I have commented my proposed changes within the code.
  3. I am willing to help maintain this change if there are issues with it later.
  4. It is compatible with the EUPL 1.2 license
  5. I have squashed any insignificant commits. (git rebase)

Checklist:

  • The code change is tested and works locally.
  • I based my code and PRs against the repositories development branch.
  • I signed off all commits. Pi-hole enforces the DCO for all contributions
  • I signed all my commits. Pi-hole requires signatures to verify authorship
  • I have read the above and my PR is ready for review.

…lid IP or a hostname

Signed-off-by: Dominik <dl6er@dl6er.de>
@DL6ER DL6ER added the Bugfix label Oct 26, 2025
@DL6ER DL6ER linked an issue Oct 26, 2025 that may be closed by this pull request
@DL6ER DL6ER mentioned this pull request Oct 27, 2025
1 task
@DL6ER DL6ER marked this pull request as ready for review October 30, 2025 18:22
@DL6ER DL6ER requested a review from a team as a code owner October 30, 2025 18:22
@DL6ER DL6ER linked an issue Oct 30, 2025 that may be closed by this pull request
@DL6ER DL6ER merged commit dab2107 into development Oct 31, 2025
18 checks passed
@DL6ER DL6ER deleted the fix/ntp_sync_server_ip_domain branch October 31, 2025 19:12
truecharts-admin added a commit to trueforge-org/truecharts that referenced this pull request Nov 5, 2025
#41431)

This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
|
[ghcr.io/pi-hole/pihole](https://redirect.github.com/pi-hole/docker-pi-hole)
| minor | `7f2dff3` -> `e28e239` |

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

Add the preset `:preserveSemverRanges` to your config if you don't want
to pin your dependencies.

---

### Release Notes

<details>
<summary>pi-hole/docker-pi-hole (ghcr.io/pi-hole/pihole)</summary>

###
[`v2025.11.0`](https://redirect.github.com/pi-hole/docker-pi-hole/releases/tag/2025.11.0)

[Compare
Source](https://redirect.github.com/pi-hole/docker-pi-hole/compare/2025.10.3...2025.11.0)

Re-release, the `riscv64` part of the image is not currently building
and preventing the image from being published for other architectures.

I have disabled the `riscv64` build for the time being until I have time
to debug what is happening with it. I

If you are running this image on `riscv64`, please get in touch via
issues if you are willing to help troubleshoot the process!

## Otherwise, nothing specific for Docker, tagging to get an FTL change
out:

#### What's Changed (FTL v6.3.3)

- Fix crash in NTP error handling code by
[@&#8203;DL6ER](https://redirect.github.com/DL6ER) in
[pi-hole/FTL#2684](https://redirect.github.com/pi-hole/FTL/pull/2684)
- Add validation for ntp.sync.server by
[@&#8203;DL6ER](https://redirect.github.com/DL6ER) in
[pi-hole/FTL#2667](https://redirect.github.com/pi-hole/FTL/pull/2667)
- Be more explicit about required path and query parameters for list
manipulation by [@&#8203;yubiuser](https://redirect.github.com/yubiuser)
in [pi-hole/FTL#2689](https://redirect.github.com/pi-hole/FTL/pull/2689)
- Pi-hole FTL v6.3.3 by
[@&#8203;DL6ER](https://redirect.github.com/DL6ER) in
[pi-hole/FTL#2693](https://redirect.github.com/pi-hole/FTL/pull/2693)

**Full Changelog**:
<pi-hole/FTL@v6.3.2...v6.3.3>

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Renovate
Bot](https://redirect.github.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS44Mi4xMCIsInVwZGF0ZWRJblZlciI6IjQxLjgyLjEwIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbImF1dG9tZXJnZSIsInJlbm92YXRlL2NvbnRhaW5lciIsInR5cGUvbWlub3IiXX0=-->
github-actions Bot pushed a commit to bigbeartechworld/big-bear-universal-apps that referenced this pull request Nov 8, 2025
This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [jacklul/pihole](https://redirect.github.com/pi-hole/docker-pi-hole) | minor | `2025.10.3` -> `2025.11.0` |

---

### Release Notes

<details>
<summary>pi-hole/docker-pi-hole (jacklul/pihole)</summary>

### [`v2025.11.0`](https://redirect.github.com/pi-hole/docker-pi-hole/releases/tag/2025.11.0)

[Compare Source](https://redirect.github.com/pi-hole/docker-pi-hole/compare/2025.10.3...2025.11.0)

Re-release, the `riscv64` part of the image is not currently building and preventing the image from being published for other architectures.

I have disabled the `riscv64` build for the time being until I have time to debug what is happening with it. I

If you are running this image on `riscv64`, please get in touch via issues if you are willing to help troubleshoot the process!

## Otherwise, nothing specific for Docker, tagging to get an FTL change out:

##### What's Changed (FTL v6.3.3)

- Fix crash in NTP error handling code by [@&#8203;DL6ER](https://redirect.github.com/DL6ER) in [pi-hole/FTL#2684](https://redirect.github.com/pi-hole/FTL/pull/2684)
- Add validation for ntp.sync.server by [@&#8203;DL6ER](https://redirect.github.com/DL6ER) in [pi-hole/FTL#2667](https://redirect.github.com/pi-hole/FTL/pull/2667)
- Be more explicit about required path and query parameters for list manipulation by [@&#8203;yubiuser](https://redirect.github.com/yubiuser) in [pi-hole/FTL#2689](https://redirect.github.com/pi-hole/FTL/pull/2689)
- Pi-hole FTL v6.3.3 by [@&#8203;DL6ER](https://redirect.github.com/DL6ER) in [pi-hole/FTL#2693](https://redirect.github.com/pi-hole/FTL/pull/2693)

**Full Changelog**: <pi-hole/FTL@v6.3.2...v6.3.3>

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/bigbeartechworld/big-bear-universal-apps).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNTkuNCIsInVwZGF0ZWRJblZlciI6IjQxLjE1OS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZSJdfQ==-->
github-actions Bot pushed a commit to bigbeartechworld/big-bear-universal-apps that referenced this pull request Nov 9, 2025
This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [pihole/pihole](https://redirect.github.com/pi-hole/docker-pi-hole) | minor | `2025.10.3` -> `2025.11.0` |

---

### Release Notes

<details>
<summary>pi-hole/docker-pi-hole (pihole/pihole)</summary>

### [`v2025.11.0`](https://redirect.github.com/pi-hole/docker-pi-hole/releases/tag/2025.11.0)

[Compare Source](https://redirect.github.com/pi-hole/docker-pi-hole/compare/2025.10.3...2025.11.0)

Re-release, the `riscv64` part of the image is not currently building and preventing the image from being published for other architectures.

I have disabled the `riscv64` build for the time being until I have time to debug what is happening with it. I

If you are running this image on `riscv64`, please get in touch via issues if you are willing to help troubleshoot the process!

## Otherwise, nothing specific for Docker, tagging to get an FTL change out:

##### What's Changed (FTL v6.3.3)

- Fix crash in NTP error handling code by [@&#8203;DL6ER](https://redirect.github.com/DL6ER) in [pi-hole/FTL#2684](https://redirect.github.com/pi-hole/FTL/pull/2684)
- Add validation for ntp.sync.server by [@&#8203;DL6ER](https://redirect.github.com/DL6ER) in [pi-hole/FTL#2667](https://redirect.github.com/pi-hole/FTL/pull/2667)
- Be more explicit about required path and query parameters for list manipulation by [@&#8203;yubiuser](https://redirect.github.com/yubiuser) in [pi-hole/FTL#2689](https://redirect.github.com/pi-hole/FTL/pull/2689)
- Pi-hole FTL v6.3.3 by [@&#8203;DL6ER](https://redirect.github.com/DL6ER) in [pi-hole/FTL#2693](https://redirect.github.com/pi-hole/FTL/pull/2693)

**Full Changelog**: <pi-hole/FTL@v6.3.2...v6.3.3>

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/bigbeartechworld/big-bear-universal-apps).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNTkuNCIsInVwZGF0ZWRJblZlciI6IjQxLjE1OS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZSJdfQ==-->
github-actions Bot pushed a commit to bigbeartechworld/big-bear-universal-apps that referenced this pull request Nov 14, 2025
…ag to v2025.11.0

This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [bigbeartechworld/big-bear-pihole-unbound](https://redirect.github.com/pi-hole/docker-pi-hole) | minor | `2025.08.0` -> `2025.11.0` |

---

### Release Notes

<details>
<summary>pi-hole/docker-pi-hole (bigbeartechworld/big-bear-pihole-unbound)</summary>

### [`v2025.11.0`](https://redirect.github.com/pi-hole/docker-pi-hole/releases/tag/2025.11.0)

[Compare Source](https://redirect.github.com/pi-hole/docker-pi-hole/compare/2025.08.0...2025.11.0)

Re-release, the `riscv64` part of the image is not currently building and preventing the image from being published for other architectures.

I have disabled the `riscv64` build for the time being until I have time to debug what is happening with it. I

If you are running this image on `riscv64`, please get in touch via issues if you are willing to help troubleshoot the process!

## Otherwise, nothing specific for Docker, tagging to get an FTL change out:

#### What's Changed (FTL v6.3.3)

- Fix crash in NTP error handling code by [@&#8203;DL6ER](https://redirect.github.com/DL6ER) in [pi-hole/FTL#2684](https://redirect.github.com/pi-hole/FTL/pull/2684)
- Add validation for ntp.sync.server by [@&#8203;DL6ER](https://redirect.github.com/DL6ER) in [pi-hole/FTL#2667](https://redirect.github.com/pi-hole/FTL/pull/2667)
- Be more explicit about required path and query parameters for list manipulation by [@&#8203;yubiuser](https://redirect.github.com/yubiuser) in [pi-hole/FTL#2689](https://redirect.github.com/pi-hole/FTL/pull/2689)
- Pi-hole FTL v6.3.3 by [@&#8203;DL6ER](https://redirect.github.com/DL6ER) in [pi-hole/FTL#2693](https://redirect.github.com/pi-hole/FTL/pull/2693)

**Full Changelog**: <pi-hole/FTL@v6.3.2...v6.3.3>

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/bigbeartechworld/big-bear-universal-apps).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNzMuMSIsInVwZGF0ZWRJblZlciI6IjQxLjE3My4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZSJdfQ==-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FTL v6.3.2: Crash Multiple IP Addresses defined in ntp.sync.server causes crash loop

3 participants