Describe the bug
Server clock is said to be wrong when NTP server cannot be reached.
- Have a server in China or any part of the world limiting access to Google NTP
- Go to "MEDIA CLOUD SYSTEM COMPATIBILITY TEST" page
Your server's system clock is wrong by over 130 years 8 months 2 weeks 4 days 1 hour 44 minutes 2 seconds. This will cause errors with cloud storage services. You may need to contact your hosting provider to correct the situation.
and in error log (using Query Monitor plugin):
message: "unpack(): Type N: not enough input, need 4, have 0"
stack: (5) ["unpack()", "ILAB\M\T\D\S\SystemCompatibilityTool->calcTimeDrift()", "ILAB\M\T\D\S\SystemCompatibilityTool->testEnvironment()", "ILAB\M\T\D\S\SystemCompatibilityTool->startTroubleshooting()", "do_action('wp_ajax_ilab_media_cloud_start_troubleshooting')"]
component: "Plugin: ilab-media-tools"
An error message stating NTP server could not be reached, and a setting or WordPress filter to customize the hardcoded 'time.google.com'.