# Failed to adjust time during NTP sync: Insufficient permissions

**URL:** <https://discourse.pi-hole.net/t/failed-to-adjust-time-during-ntp-sync-insufficient-permissions/70966>\
**Category:** Beta 6.0\
**Created:** [June 30, 2024, 11:48am UTC](https://discourse.pi-hole.net/t/failed-to-adjust-time-during-ntp-sync-insufficient-permissions/70966 "2024-06-30T11:48:58Z")\
**Posts on this page:** 1\
**Showing post:** 60

<div class="post-metadata">

**Author:** ![SoBo7a](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/sobo7a/32/45904_2.png) [@SoBo7a](https://discourse.pi-hole.net/u/SoBo7a)\
**Post date:** [February 21, 2025, 6:34pm UTC](https://discourse.pi-hole.net/t/failed-to-adjust-time-during-ntp-sync-insufficient-permissions/70966/60 "2025-02-21T18:34:01Z")

</div>

I am not a Proxmox expert, so I might be wrong...

However, I wouldn't recommend setting the container as privileged, since you might introduce a vulnerability to your host by doing so.

By default, your Proxmox host should already have working NTP synchronization, and your LXC containers get the time from your host. I believe that if you set the container to privileged, Pi-hole will also attempt to update the time on the host, which is not necessary since the host already does that. So all you accomplish by setting the container as privileged is introducing a potential vulnerability to your entire host/cluster.

So, in my opinion, the best fix for this is to simply empty the `ntp.sync.server` and set the `ntp.sync.interval` to `0`, as mentioned in the marked solution by DL6ER.

---

_[View the full topic](https://discourse.pi-hole.net/t/failed-to-adjust-time-during-ntp-sync-insufficient-permissions/70966)._
