In the Plex Web interface on the Dashboard the bandwidth graph is offset by 30 seconds. From “now” to 30 is always empty, then from 30 on, it shows the info. The graph is Real Time.
Any ideas?
Verify that the local time of both your client and your server devices are in sync.
Best way to ensure that is to make them sync automatically to a ntp server.
Oh ok, interesting. Is there an option to sync plex directly to an NTP server?
PMS is running in a container. But the host system (OMV) syncs via NTP,
There is no need to perform such a low level function in Plex. That is the job of the OS.
I am not a Linux guru, so I don’t know if any containerization tech has the power to use its own, separate RTC. But I doubt it.
Keep in mind that the clock of the system which is running Plex web app, has to be correct as well.
LXC containers get their time from the host, unless you go out of your way to disable it.
Interesting. Maybe I can bypass OMV and set up NTP directly in Debian as a test.
Is the time on OMV itself accurate?
Is the time on the computer with the web browser accurate?
If those are both correct, perhaps it’s the container. But I’d start there first.
Even though it was set to sync via NTP, the time in OMV was off by about 30 seconds. I’ve never seen that before. I manually set the time, then re-enabled NTP. So far so good.
Yay!
Some NTP implementations won’t sync if they’re significantly off when they start.
Another scenario is a system that can sync once at startup, but then can’t stay synced and drifts slowly over time.
There’s usually a mechanism in the GUI or CLI (ntpq, chronyc) to monitor NTP system health.
