Stuck with the RequestTimeTooSkewed error? We can help you.

Here, at Bobcares, we assist our customers with several AWS errors as part of our AWS Support Services.

Today, let us see how our Support Techs fix this error for our customers.

RequestTimeTooSkewed error

Most often, we come across this error, when we configure an Amazon S3 backup server under CPanel backup configuration to upload backup files.

At some point it will show the following error message:

warn [cpbackup_transport_file] Path creation failed: RequestTimeTooSkewed: The difference between the request time and the current time is too large.

Now that we know the error, let us see how our Support Techs go ahead and resolve it in an easy method.

Initially, we need to know if the Amazon S3 uses an NTP system clock.

Because mostly this error means our server time and Amazon clocks time are out of sync.

We also need to know that, this error can appear in any of the following locations:

/usr/local/cpanel/logs/error_log
/usr/local/cpanel/logs/cpbackup_transporter/*
/usr/local/cpanel/logs/cpbackup_transporter.log

Generally, the issue is that the time on the local server is out of sync with the current time and we need to correct it.

To do so, we sync up the system clock and the problem should resolve.

Any of the following commands should work:

ntpdate us.pool.ntp.org
rdate -s rdate.cpanel.net
ntpclient -s -h pool.ntp.org

[Stuck in between? We are available 24*7]

Conclusion

In short, we see the error when we configure an Amazon S3 backup server under CPanel backup configuration to upload backup files. In this article, we saw how our Support Techs fix the same.