Cannot Access Web Interface after installing NTP.

[bartix]

I installed Proxmox on 2 new server and all the procedure from the iso went ok. I configured cluster and tested it, all work like a charm.
Now, after I installed NTP on both servers I cannot Access Web Interface.

NTP logs:
24 Apr 21:43:34 ntpd[7252]: Listen and drop on 0 v6wildcard [::]:123
24 Apr 21:43:34 ntpd[7252]: Listen and drop on 1 v4wildcard 0.0.0.0:123
24 Apr 21:43:34 ntpd[7252]: Listen normally on 2 lo 127.0.0.1:123
24 Apr 21:43:34 ntpd[7252]: Listen normally on 3 vmbr0 192.168.0.4:123
24 Apr 21:43:34 ntpd[7252]: Listen normally on 4 lo [::1]:123
24 Apr 21:43:34 ntpd[7252]: Listen normally on 5 vmbr0 [fe80::201:2eff:fe00:80c%4]:123
24 Apr 21:43:34 ntpd[7252]: Listening on routing socket on fd #22 for interface updates
24 Apr 21:43:34 ntpd[7252]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
24 Apr 21:43:34 ntpd[7252]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
24 Apr 21:52:22 ntpd[7252]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
24 Apr 21:54:57 ntpd[817]: Listen and drop on 0 v6wildcard [::]:123
24 Apr 21:54:57 ntpd[817]: Listen and drop on 1 v4wildcard 0.0.0.0:123
24 Apr 21:54:57 ntpd[817]: Listen normally on 2 lo 127.0.0.1:123
24 Apr 21:54:57 ntpd[817]: Listen normally on 3 lo [::1]:123
24 Apr 21:54:57 ntpd[817]: Listening on routing socket on fd #20 for interface updates
24 Apr 21:54:57 ntpd[817]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
24 Apr 21:54:57 ntpd[817]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
24 Apr 21:55:02 ntpd[817]: Listen normally on 4 vmbr0 192.168.0.4:123
24 Apr 21:55:02 ntpd[817]: bind(24) AF_INET6 fe80::201:2eff:fe00:80c%4#123 flags 0x11 failed: Cannot assign requested address
24 Apr 21:55:02 ntpd[817]: unable to create socket on vmbr0 (5) for fe80::201:2eff:fe00:80c%4#123
24 Apr 21:55:02 ntpd[817]: failed to init interface for address fe80::201:2eff:fe00:80c%4
24 Apr 21:55:02 ntpd[817]: new interface(s) found: waking up resolver
24 Apr 21:55:04 ntpd[817]: Listen normally on 6 vmbr0 [fe80::201:2eff:fe00:80c%4]:123
24 Apr 21:55:04 ntpd[817]: new interface(s) found: waking up resolver
24 Apr 22:04:52 ntpd[817]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
25 Apr 17:26:23 ntpd[835]: Listen and drop on 0 v6wildcard [::]:123
25 Apr 17:26:23 ntpd[835]: Listen and drop on 1 v4wildcard 0.0.0.0:123
25 Apr 17:26:23 ntpd[835]: Listen normally on 2 lo 127.0.0.1:123
25 Apr 17:26:23 ntpd[835]: Listen normally on 3 lo [::1]:123
25 Apr 17:26:23 ntpd[835]: Listening on routing socket on fd #20 for interface updates
25 Apr 17:26:23 ntpd[835]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
25 Apr 17:26:23 ntpd[835]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
25 Apr 17:26:25 ntpd[835]: Listen normally on 4 vmbr0 192.168.0.4:123
25 Apr 17:26:25 ntpd[835]: bind(24) AF_INET6 fe80::201:2eff:fe00:80c%4#123 flags 0x11 failed: Cannot assign requested address
25 Apr 17:26:25 ntpd[835]: unable to create socket on vmbr0 (5) for fe80::201:2eff:fe00:80c%4#123
25 Apr 17:26:25 ntpd[835]: failed to init interface for address fe80::201:2eff:fe00:80c%4
25 Apr 17:26:25 ntpd[835]: new interface(s) found: waking up resolver
25 Apr 17:26:27 ntpd[835]: Listen normally on 6 vmbr0 [fe80::201:2eff:fe00:80c%4]:123
25 Apr 17:26:27 ntpd[835]: new interface(s) found: waking up resolver
25 Apr 17:31:53 ntpd[835]: ntpd exiting on signal 15 (Terminated)
25 Apr 17:31:53 ntpd[835]: 109.205.50.68 local addr 192.168.0.4 -> <null>
25 Apr 17:31:53 ntpd[835]: 149.156.70.60 local addr 192.168.0.4 -> <null>
25 Apr 17:31:53 ntpd[835]: 178.215.228.24 local addr 192.168.0.4 -> <null>
25 Apr 17:31:53 ntpd[835]: 188.165.17.91 local addr 192.168.0.4 -> <null>

 

[remark]

Check for duplicate IP addresses first.

 

[bartix]

There are no duplicate IP addresses. My servers IP addresses are 192.168.0.4 and 192.168.0.5. When I try to access the server page it says "Server 192.168.0.4 took too long to respond." Did I do something wrong in the NTP configuration?

# Leap seconds definition provided by tzdata
leapfile /usr/share/zoneinfo/leap-seconds.list

# Enable this if you want statistics to be logged.
#statsdir /var/log/ntpstats/

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


# You do need to talk to an NTP server or two (or three).
#server ntp.your-provider.example

# pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will
# pick a different set every time it starts up. Please consider joining the
# pool: <http://www.pool.ntp.org/join.html>
#pool 0.debian.pool.ntp.org iburst
#pool 1.debian.pool.ntp.org iburst
#pool 2.debian.pool.ntp.org iburst
#pool 3.debian.pool.ntp.org iburst

server 0.pl.pool.ntp.org
server 1.pl.pool.ntp.org
server 2.pl.pool.ntp.org
server 3.pl.pool.ntp.org

# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
# details. The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions>
# might also be helpful.
#
# Note that "restrict" applies to both servers and clients, so a configuration
# that might be intended to block requests from certain clients could also end
# up blocking replies from your own upstream servers.

# By default, exchange time with everybody, but don't allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery limited
restrict -6 default kod notrap nomodify nopeer noquery limited

# Local users may interrogate the ntp server more closely.
restrict 8.8.8.8 // maybe 127.0.0.1 ???
restrict ::1

# Needed for adding pool entries
restrict source notrap nomodify noquery

# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
restrict 192.168.0.1 mask 255.255.255.0 notrust


# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
#broadcast 192.168.123.255

# If you want to listen to time broadcasts on your local subnet, de-comment the
# next lines. Please do this only if you trust everybody on the network!
#disable auth
#broadcastclient

logfile /var/log/ntp.log
:wq