Why are you using a routable IP address for your server? It is generally a non routable IP address - 192.x.x.x or 10.x.x.x.
I also see some disk messages:
Nov 18 01:28:03 Tower emhttpd: Device inventory:
Nov 18 01:28:03 Tower emhttpd: ST10000NM0096_ZA28AN6X0000C84990VP_35000c500a6887b8f (sdj) 512 19532873728
Nov 18 01:28:03 Tower emhttpd: CT4000P3PSSD8_2240E671E196 (nvme1n1) 512 7814037168
Nov 18 01:28:03 Tower emhttpd: ST18000NM000J-2TV103_ZR5AATG8 (sdk) 512 35156656128
Nov 18 01:28:03 Tower emhttpd: ST10000NM0096_ZA289X5X0000C84970L4_35000c500a688f673 (sdh) 512 19532873728
Nov 18 01:28:03 Tower emhttpd: device /dev/sdg problem getting id
Nov 18 01:28:03 Tower emhttpd: CT2000P3PSSD8_2236E6620BCF (nvme2n1) 512 3907029168
Nov 18 01:28:03 Tower emhttpd: device /dev/sdw problem getting id
Nov 18 01:28:03 Tower emhttpd: WD4001FYYG-79SL3_WMC1F0678389_350000c0f011a8fc8 (sdd) 512 7814037168
Nov 18 01:28:03 Tower emhttpd: ST18000NM000J-2TV103_ZR5AASEN (sdt) 512 35156656128
Nov 18 01:28:03 Tower emhttpd: ST10000NM0096_ZA25B1XW0000C83025ZP_35000c5009538c473 (sde) 512 19532873728
Nov 18 01:28:03 Tower emhttpd: device /dev/sdu problem getting id
Nov 18 01:28:03 Tower emhttpd: WD4001FYYG-79SL3_WMC1F0582250_350000c0f01bfcf08 (sdb) 512 7814037168
Nov 18 01:28:03 Tower emhttpd: ST10000NM0096_ZA25B2360000C82959F1_35000c5009538bcd7 (sdr) 512 19532873728
Nov 18 01:28:03 Tower emhttpd: device /dev/sdf problem getting id
Nov 18 01:28:03 Tower emhttpd: device /dev/sdv problem getting id
Nov 18 01:28:03 Tower emhttpd: WD4001FYYG-79SL3_WMC1F0677098_350000c0f01c01870 (sdc) 512 7814037168
Nov 18 01:28:03 Tower emhttpd: CT4000P3PSSD8_2240E671E178 (nvme0n1) 512 7814037168
Nov 18 01:28:03 Tower emhttpd: ST18000NM000J-2TV103_ZR51J2MF (sds) 512 35156656128
Nov 18 01:28:03 Tower emhttpd: device /dev/sdn problem getting id
Nov 18 01:28:03 Tower emhttpd: WD4001FYYG-79SL3_WMC1F0611178_350000c0f01bfcf2c (sdq) 512 7814037168
Nov 18 01:28:03 Tower emhttpd: CT2000P3PSSD8_2236E66208FE (nvme3n1) 512 3907029168
Nov 18 01:28:03 Tower emhttpd: device /dev/sdo problem getting id
Nov 18 01:28:03 Tower emhttpd: ST18000NM000J-2TV103_ZR53BJBY (sdl) 512 35156656128
Nov 18 01:28:03 Tower emhttpd: ST10000NM0096_ZA27GE950000C845LGLY_35000c500a65a6ab7 (sdi) 512 19532873728
Nov 18 01:28:03 Tower emhttpd: device /dev/sdp problem getting id
I'm not a disk expert, so maybe @JorgeB can offer some insight to whether or not these messages are an issue.
As for UD, I do not understand how it could cause these problems.