The time is lagging behind and NTP does not work

I have had an time update issue for a long time now.
I have OMV installed on a PC and the time is constantly lagging behind.
It falls behind an hour or more per day, so I need to update the time manually often.

And I have not succeeded to get the clock in 24 Hour mode either. I suspect that could be related.

Often when I update the time manually, I get a "504 Gateway Time-out" from nginx:

Not sure how to fix that...
But when I press Update one more time, the time is updated.

So I need help with two things, First and most important, Make sure the time is kept current and second, help to show the time as I want it, in 24 hour mode.

My ntp.conf looks like this (I have not edited this by hand):

# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help


driftfile /var/lib/ntp/ntp.drift


# Disable the panic feature.
tinker panic 0


statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable


server 127.127.1.0 # Local clock
fudge 127.127.1.0 stratum 12
server 0.se.pool.ntp.org iburst


# By default, exchange time with everybody, but do not allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery


# Local users may interrogate the ntp server more closely.
restrict 127.0.0.1
restrict ::1

Not sure if there is any other settings that is used for this...

That is true. Thanks, I'll edit those.

(I don't think I'll get a Rose tattoo, but hopefully I will get shipped up to Boston, in the state of Massachusetts. )

Not yet. But after I removed those two lines I can update the time with "ntpd -q".
So now I just need to figure out why it doesn't work automatically.

Tested a couple of other ntp-servers and noticed that when I save the change in the OMV UI, the "server 127.127.1.0 # local clock" and "fudge 127.127.1.0 stratum 12" returns.

Is that as expected or is there some other faulty setting that causes this?