blocks|key|3209214|text|本地计算机上的时间与当前时间不同步。同步你的系统时钟，这个问题就会消失。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3209215|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The time on your local box is out of sync with the current time. Sync up your system clock and the problem will go away.

blocks|key|284684|text|对于那些使用Vagrant的人来说，后面跟着vagrant+up的vagrant+halt对我来说很有效。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|284685|entityMap^0|M|A|X|C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

For those using Vagrant, a <code>vagrant halt</code> followed by <code>vagrant up</code> worked for me.

blocks|key|2995954|text|时钟不同步。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2995955|我按照this+post中的步骤让它再次工作，但还必须运行以下命令。|offset|length|2995956|sudo+ntpdate+ntp.ubuntu.com
sudo+apt-get+install+ntp|code-block|syntax|javascript|2995957|如果您在任何时候收到一条消息，指出NTP套接字仍在使用中，请使用sudo+/etc/init.d/ntp+stop将其停止并重新运行您的命令。|style|CODE|2995958|entityMap|0|LINK|mutability|MUTABLE|url|http://www.howtogeek.com/tips/how-to-sync-your-linux-server-time-with-network-time-servers-ntp/^0|0|3|9|0|0|0|W|P|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|12|8|@$D|13|E|14|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

The clock is out of sync. 

I followed the steps in <a href="http://www.howtogeek.com/tips/how-to-sync-your-linux-server-time-with-network-time-servers-ntp/">this post</a> to get it working again, but also had to run the following command.

<pre><code>sudo ntpdate ntp.ubuntu.com
sudo apt-get install ntp
</code></pre>

If at any time you get a message saying the NTP socket is still in use, stop it with <code>sudo /etc/init.d/ntp stop</code> and re-run your command.

blocks|key|284757|text|我也遇到了同样的错误，我正在使用Docker+for+Mac。简单地重新启动Docker对我来说是有效的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|284758|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same error and I'm using Docker for Mac. Simply restarting Docker worked for me.

blocks|key|2996234|text|对于那些在Windows中使用Docker的用户，尝试在Setting->Reset->Restart+Docker中重新启动Docker引擎。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2996235|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For those using Docker in Windows try restarting the Docker Engine in Setting->Reset->Restart Docker.

blocks|key|287021|text|如果有人使用Laravel和Homestead发现了这一点，只需运行|type|unstyled|depth|inlineStyleRanges|entityRanges|data|287022|homestead+halt|code-block|syntax|javascript|287023|紧接着是|287024|homestead+up|287025|你就可以再来一次了。|287026|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

In case anyone finds this using Laravel and Homestead, simply running

<pre><code>homestead halt
</code></pre>

followed by

<pre><code>homestead up
</code></pre>

And you're good to go again.

blocks|key|3209575|text|正如其他人所说，您的本地时钟与AWS不同步。你可以使用NTP将它直接同步到亚马逊的服务器上，这样你就不必担心现在或将来的时钟漂移了。。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3209576|注意:以下说明适用于*nix用户。我已经添加了一条评论，告诉你如何在Windows中做到这一点，但作为一个非Windows用户，我不能验证他们的准确性。|3209577|3209578|blockquote|3209579|3209580|3209581|要安装NTP，只需根据您的发行版选择以下选项之一：|ordered-list-item|3209582|3209583|apt-get安装ntp|3209584|或|3209585|yum安装ntp|3209586|等。|3209587|配置NTP以使用亚马逊服务器，如下所示：|unordered-list-item|3209588|3209589|vim+/etc/ntp.conf|3209590|在其中，注释掉默认服务器并添加以下内容：|3209591|服务器0.amazon.pool.ntp.org+iburst服务器1.amazon.pool.ntp.org+iburst服务器2.amazon.pool.ntp.org+iburst服务器3.amazon.pool.ntp.org+iburst|3209592|，然后重新启动ntp服务：|3209593|3209594|sudo服务ntp重启|3209595|来源：https://www.allcloud.io/how-to/how-to-fix-amazon-s3-requesttimetooskewed/|3209596|还有一篇关于保持时间与NTP同步的更一般的文章：https://www.digitalocean.com/community/tutorials/how-to-set-up-time-synchronization-on-ubuntu-12-04|3209597|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Network_Time_Protocol|1|https://www.allcloud.io/how-to/how-to-fix-amazon-s3-requesttimetooskewed/|2|https://www.digitalocean.com/community/tutorials/how-to-set-up-time-synchronization-on-ubuntu-12-04^0|1U|1|R|3|0|0|0|24|0|0|0|0|0|0|P|0|0|0|C|0|0|1|0|0|8|0|0|2|0|0|K|0|0|0|H|0|0|K|0|0|3G|0|0|D|0|0|0|B|0|0|24|3|21|1|0|0|3F|O|2R|2|0^^$0|@$1|2|3|4|5|6|7|1T|8|@$9|1U|A|1V|B|C]]|D|@$9|1W|A|1X|1|1Y]]|E|$]]|$1|F|3|G|5|6|7|1Z|8|@$9|20|A|21|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|22|8|@]|D|@]|E|$]]|$1|I|3|-4|5|J|7|23|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|24|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|25|8|@]|D|@]|E|$]]|$1|M|3|N|5|O|7|26|8|@$9|27|A|28|B|C]]|D|@]|E|$]]|$1|P|3|-4|5|6|7|29|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|2A|8|@$9|2B|A|2C|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|2D|8|@$9|2E|A|2F|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|2G|8|@$9|2H|A|2I|B|C]]|D|@]|E|$]]|$1|W|3|X|5|6|7|2J|8|@$9|2K|A|2L|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|10|7|2M|8|@$9|2N|A|2O|B|C]]|D|@]|E|$]]|$1|11|3|-4|5|6|7|2P|8|@]|D|@]|E|$]]|$1|12|3|13|5|6|7|2Q|8|@$9|2R|A|2S|B|C]]|D|@]|E|$]]|$1|14|3|15|5|6|7|2T|8|@$9|2U|A|2V|B|C]]|D|@]|E|$]]|$1|16|3|17|5|6|7|2W|8|@$9|2X|A|2Y|B|C]]|D|@]|E|$]]|$1|18|3|19|5|10|7|2Z|8|@$9|30|A|31|B|C]]|D|@]|E|$]]|$1|1A|3|-4|5|6|7|32|8|@]|D|@]|E|$]]|$1|1B|3|1C|5|6|7|33|8|@$9|34|A|35|B|C]]|D|@]|E|$]]|$1|1D|3|1E|5|6|7|36|8|@$9|37|A|38|B|C]]|D|@$9|39|A|3A|1|3B]]|E|$]]|$1|1F|3|1G|5|6|7|3C|8|@$9|3D|A|3E|B|C]]|D|@$9|3F|A|3G|1|3H]]|E|$]]|$1|1H|3|-4|5|6|7|3I|8|@]|D|@]|E|$]]]|1I|$1J|$5|1K|1L|1M|E|$1N|1O]]|1P|$5|1K|1L|1M|E|$1N|1Q]]|1R|$5|1K|1L|1M|E|$1N|1S]]]]

As other's have said, your local clock is out of sync with AWS. You can keep it sync'd to Amazon's servers directly using <a href="https://en.wikipedia.org/wiki/Network_Time_Protocol" rel="noreferrer">NTP</a> so you won't have to worry about clock drift now or in the future.

Note: The below instructions are for *nix users. I've added a comment with how you might do it in Windows, but as a non-Windows user I can't verify their accuracy.

<blockquote>
 <ol>
 <li>To install NTP, simply choose one of the following, depending on your distribution:

<pre><code>apt-get install ntp
</code></pre>
 
 or 

<pre><code>yum install ntp 
</code></pre>
 
 etc.</li>
 <li>Configure NTP to use amazon servers, like so:

<pre><code>vim /etc/ntp.conf
</code></pre>
 
 And in it, comment out the default servers and add these:

<pre><code>server 0.amazon.pool.ntp.org iburst
server 1.amazon.pool.ntp.org iburst
server 2.amazon.pool.ntp.org iburst
server 3.amazon.pool.ntp.org iburst
</code></pre></li>
 <li>And then restart ntp service:

<pre><code>sudo service ntp restart
</code></pre></li>
 </ol>
</blockquote>

Source: <a href="https://www.allcloud.io/how-to/how-to-fix-amazon-s3-requesttimetooskewed/" rel="noreferrer">https://www.allcloud.io/how-to/how-to-fix-amazon-s3-requesttimetooskewed/</a>

And a more general article on keeping your time synchronized with NTP:
<a href="https://www.digitalocean.com/community/tutorials/how-to-set-up-time-synchronization-on-ubuntu-12-04" rel="noreferrer">https://www.digitalocean.com/community/tutorials/how-to-set-up-time-synchronization-on-ubuntu-12-04</a>

blocks|key|283522|text|在WSL+2或任何基于Deb的Linux+(Ubuntu、Mint...)上：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|283523|检查日期：|283524|date|code-block|syntax|javascript|283525|现在运行：|283526|sudo+apt+install+ntpdate+
sudo+ntpdate++time.nist.gov|283527|输出示例：|283528|18+Feb+14:27:36+ntpdate[24008]:+step+time+server+132.163.97.4+offset+1009.140848+sec|283529|再次检查日期：|283530|283531|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|X|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Y|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Z|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|10|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|11|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|12|8|@]|9|@]|A|$]]|$1|S|3|E|5|F|7|13|8|@]|9|@]|A|$G|H]]|$1|T|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|U|$]]

On WSL 2 or any Deb-based Linux (Ubuntu, Mint ...):
Check date:
<pre><code>date
</code></pre>
Now run:
<pre><code>sudo apt install ntpdate 
sudo ntpdate time.nist.gov
</code></pre>
Output example:
<pre><code>18 Feb 14:27:36 ntpdate[24008]: step time server 132.163.97.4 offset 1009.140848 sec
</code></pre>
Check date again:
<pre><code>date
</code></pre>

blocks|key|2996472|text|2021答案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2996473|AWS.config.update({
++++accessKeyId:+'xxx',
++++secretAccessKey:+'xxxx',
++++correctClockSkew:+true
});|code-block|syntax|javascript|2996474|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

2021 answer:
<pre class="lang-js prettyprint-override"><code>AWS.config.update({
 accessKeyId: 'xxx',
 secretAccessKey: 'xxxx',
 correctClockSkew: true
});
</code></pre>

blocks|key|287028|text|这会在OSX上正确地重置我的系统时钟。使用JS上传的S3现在在本地开发环境中可以正常工作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|287029|ntpdate+us.pool.ntp.org|code-block|syntax|javascript|287030|Read+more+about+this+here|offset|length|287031|entityMap|0|LINK|mutability|MUTABLE|url|http://www.tech-problems.com/requesttimetooskewed-the-difference-between-the-request-time-and-the-current-time-is-too-large/^0|0|0|0|P|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

This reset my system clock correctly on OSX. S3 uploads using the JS SDK works for me now in local dev

<pre><code>ntpdate us.pool.ntp.org
</code></pre>

<a href="http://www.tech-problems.com/requesttimetooskewed-the-difference-between-the-request-time-and-the-current-time-is-too-large/" rel="noreferrer">Read more about this here</a>

blocks|key|287084|text|这也可能是由于使用async/await在任务外部构造请求对象以及在任务内部实际调用AWS造成的。如果有许多任务正在运行，并且任务没有及时调度，或者有一些其他操作延迟了对AWS的实际调用，则可能会抛出此异常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|287085|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This can also be caused by using async/await with the construction of the request object outside the task and the actual call to AWS inside the task. If there are lots of tasks running and the task isn't scheduled in time, or there is some other operation delaying the actual call to AWS, this exception may be thrown.

blocks|key|3209642|text|如果此问题出现在windows+10的本地主机上|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3209643|在上自动设置时间和自动设置时区这解决了我的问题。|offset|length|style|BOLD|3209644|​|3209645|📷|atomic|3209646|3209647|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/9c285ac44086d2567d1f01989ffcc3bd.png|imageAlt^0|0|2|M|0|0|1|0|0|1|0|1|0|0|0|1|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@$D|14|E|15|F|G]]|9|@$D|16|E|17|1|18]]|A|$]]|$1|M|3|I|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U|V|-4]]]]

if this problem in you localhost for windows 10 

set time automatically ON and set time zone automatically ON 
this solve my problem.

<a href="https://i.stack.imgur.com/b3PfW.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/b3PfW.png" alt="enter image description here"></a>

blocks|key|2996198|text|如果您在windows中遇到此错误，请按照以下步骤解决问题。更改您的本地时间设置：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2996199|第1步:单击change+date++time+settings|2996200|step+2:在弹出的日期和时间窗口中单击+Time选项卡|2996201|第3步：下一步单击Change+|2996202|check+step+4:check从服务器下拉列表中选择time.nist.gov或check+this+website|2996203|第5步：单击OK|2996204|重新启动控制台并进行检查。它起作用了..。|2996205|entityMap|0|LINK|mutability|MUTABLE|url|https://tf.nist.gov/tf-cgi/servers.cgi^0|4|7|0|0|I|0|0|7|L|8|0|0|G|0|0|1P|1D|C|0|0|0|8|0|0|L|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@$9|1G|A|1H|1|1I]]|E|$]]|$1|N|3|O|5|6|7|1J|8|@$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1M|8|@$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1P|8|@]|D|@]|E|$]]]|S|$T|$5|U|V|W|E|$X|Y]]]]

If you get this error in windows follow these steps to solve your problem.. Change your local time setting: 
step 1: click on change date and time settings 
step 2: from the popup Date and Time window click on Internet Time Tab 
step 3: next Click on Change Settings 
step 4: from the Server drop down select time.nist.gov or check <a href="https://tf.nist.gov/tf-cgi/servers.cgi" rel="nofollow noreferrer">this website</a> 
step 5: click on OK

Restart your console and check. It works...

blocks|key|2996558|text|对于那些在微软WLS2+Ubuntu上遇到同样问题的人，目前唯一的解决办法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2996559|sudo+hwclock+-s|code-block|syntax|javascript|2996560|或|2996561|wsl+--shutdown+|2996562|将Windows从睡眠状态唤醒后发生时钟偏移。请关注微软的https://github.com/microsoft/WSL/issues/5324修复程序。|offset|length|2996563|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/microsoft/WSL/issues/5324^0|0|0|0|0|T|18|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|10|8|@]|9|@$M|11|N|12|1|13]]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

For those facing same problem on Microsoft WLS2 Ubuntu, the only workarounds right now are:
<pre><code>sudo hwclock -s
</code></pre>
Or
<pre><code>wsl --shutdown 
</code></pre>
Clock offset is occurring after waking up Windows from sleep. Keep an eye on <a href="https://github.com/microsoft/WSL/issues/5324" rel="nofollow noreferrer">https://github.com/microsoft/WSL/issues/5324</a> for fix from microsoft.

blocks|key|3209305|text|要解决此问题，您必须调整客户端的计时，以便存在最大15分钟的时间戳差异。还要为您的系统设置标准时间和区域。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3209306|Check+the+full+Detail+here.|offset|length|3209307|entityMap|0|LINK|mutability|MUTABLE|url|http://www.bucketexplorer.com/documentation/amazon-s3--difference-between-requesttime-currenttime-too-large.html^0|0|0|R|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

To get rid of this problem, you have to adjust the client's timing so that there is a maximum time stamp difference of up to 15 minutes. Also set the standard time and zone for your system.

<a href="http://www.bucketexplorer.com/documentation/amazon-s3--difference-between-requesttime-currenttime-too-large.html" rel="nofollow">Check the full Detail here.</a>

blocks|key|2996081|text|如果您使用的是virtualbox，则进入虚拟机的时间与真实机器的时间同步。只是将时间固定到虚拟机中并不能解决问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2996082|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you are using a virtualbox, the time into virtual machine is sync with the time of the real machine. Just fix the time into the virtual machine will not fix the problem.

blocks|key|2996370|text|我出现这个错误是因为我的本地机器的时间和时区设置不正确。将它们更改为正确的时间和时区对我很有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2996371|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this error because my local machine's time and timezone were set incorrectly. Changing them to the correct time and timezone worked for me.

blocks|key|281293|text|我在Windows10和Docker上也遇到了同样的问题。您应该一步一步地运行以下命令|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|281294|docker+run+--rm+--privileged+alpine+hwclock+-s|code-block|syntax|javascript|281295|再一次|281296|docker+run+--rm+--privileged+alpine+hwclock+-s|281297|最后一个命令don't+forget+to+set+your+username+and+password+and+your+timezone，用于在Docker处于|CODE|281298|docker+run+-p+9000:9000+-e+"MINIO_ACCESS_KEY=yourUserName"+-e+"MINIO_SECRET_KEY=YourPassword"+-e+"TZ=Europe/Berlin"+-v+/etc/localtime:/etc/localtime:ro++minio/minio+server+/data|281299|entityMap^0|2|9|C|6|0|0|0|0|6|1S|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|10|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|11|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|13|8|@$9|14|A|15|B|Q]]|D|@]|E|$]]|$1|R|3|S|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|T|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|U|$]]

I had same problem in Windows 10 with Docker. You should run this commands step for step
<pre><code>docker run --rm --privileged alpine hwclock -s
</code></pre>
again
<pre><code>docker run --rm --privileged alpine hwclock -s
</code></pre>
and last command , <code>don't forget to set your username and password and your timezone</code>, to run minIO while Docker is
<pre><code>docker run -p 9000:9000 -e &quot;MINIO_ACCESS_KEY=yourUserName&quot; -e &quot;MINIO_SECRET_KEY=YourPassword&quot; -e &quot;TZ=Europe/Berlin&quot; -v /etc/localtime:/etc/localtime:ro minio/minio server /data
</code></pre>

blocks|key|283307|text|使用ntp可能无法在基于Linux的服务器的所有版本上工作(例如，不再支持的过期Ubuntu服务器版本，这将阻止您下载ntp+(如果尚未安装))。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|283308|如果这是您的情况，可以为您的Linux设置独立的时区：https://community.rackspace.com/products/f/25/t/650|offset|length|283309|执行此操作后，您可能需要重置时间/日期。执行此操作的说明在本文中：http://codeghar.wordpress.com/2007/12/06/manage-time-in-ubuntu-through-command-line|283310|entityMap|0|LINK|mutability|MUTABLE|url|https://community.rackspace.com/products/f/25/t/650|1|http://codeghar.wordpress.com/2007/12/06/manage-time-in-ubuntu-through-command-line^0|0|R|1F|0|0|X|2B|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

Using ntp may not work on all version of your Linux based server (e.g. an out of date Ubuntu server version that is no longer supported which will block you from downloading ntp if it is not already installed). 

If this is your situation, you can set independent time zones for your Linux VM:
<a href="https://community.rackspace.com/products/f/25/t/650" rel="nofollow">https://community.rackspace.com/products/f/25/t/650</a> 

After you do this you may need to reset the time/date. Instructions for doing this are in this article:
<a href="http://codeghar.wordpress.com/2007/12/06/manage-time-in-ubuntu-through-command-line" rel="nofollow">http://codeghar.wordpress.com/2007/12/06/manage-time-in-ubuntu-through-command-line</a>

blocks|key|287092|text|如果你在2016年，在伊斯坦布尔，这里有一个奇怪的情况，土耳其决定无论如何都不切换到冬季标准，将你的当地时区设置为莫斯科，然后重新启动你的机器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|287093|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If u are in 2016 and in Istanbul here is a weird situation that Turkey decided not to switch to winter time standards anyway set your local timezone to Moscow then restart your machine.

blocks|key|281242|text|我在MacOS上使用Docker+for+Mac+Beta+channel+1.13.1-beta42运行Jet+(Codeship)和Terraform时遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|281243|Failed+to+read+state:+Error+reloading+remote+state:+RequestTimeTooSkewed:+The+difference+between+the+request+time+and+the+current+time+is+too+large.
status+code:+403,+request+id:+9D32BA2A5360FC18|code-block|syntax|javascript|281244|已通过重新启动Docker解决此问题。|281245|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I ran into this issue running Jet (Codeship) and Terraform on MacOS using Docker for Mac Beta channel 1.13.1-beta42.

<pre><code>Failed to read state: Error reloading remote state: RequestTimeTooSkewed: The difference between the request time and the current time is too large.
status code: 403, request id: 9D32BA2A5360FC18
</code></pre>

This was resolved by restarting Docker.

blocks|key|281261|text|我刚刚开始收到这个错误，同步我的时钟没有帮助。(我花了2个小时将它同步到我能找到的每一个时间服务器上，包括AWS服务器，但没有什么是不同的。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|281262|同样的事情也发生在一年前的2017年12月31日。在这种情况下，重新启动我的系统，并重建我的服务器(使用aws+java+sdk)来修复它。我也不知道原因。我假设AWS有一些年终时区的特性。也有可能在我做这些事情的时候，AWS的时间服务器自己修复了。我没有办法验证这个假设。|281263|现在，同样的事情在2018年12月30日突然开始发生。这在年底是不正确的，但足够接近，看起来很可疑。(除了在这些日期之外，从未收到过此错误。)重新启动和重建这次没有帮助。|281264|我在这台机器上的开发环境是Parallels下的Windows+10。我的系统上的其他东西都没有改变-因为我已经通过回滚到之前的Parallels快照进行了双重检查。我的主机MacOS和虚拟Windows10上的时钟都是正确的。|281265|我怀疑这是AWS的bug。|281266|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I've just started getting this error, and syncing my clock doesn't help. (I've spent 2 hours syncing it to every timeserver I can find, including the AWS servers, but nothing makes a difference.)

Exactly the same thing started happening a year ago on Dec 31 2017. In that case, rebooting my system, and rebuilding my server (that uses the aws java sdk) fixed it. I don't know why. I assumed that AWS had some end-of-year timezone peculiarity. It's also possible that while I was doing these things, AWS timeservers fixed themselves. I have no way to test that hypothesis.

Now, the same thing has suddenly started to happen on Dec 30, 2018. It's not right at year-end, but close enough to seem suspicious. (Never got this error except on these dates.) Rebooting and rebuilding isn't helping this time.

My dev environment on this box is Windows 10 under Parallels. Nothing else on my system has changed - as I've double-checked by rolling back to prior Parallels snapshots. The clocks on both my host MacOS and the virtual Windows 10 are correct.

I'm suspecting an AWS bug.

blocks|key|287186|text|重新启动我的windows服务器为我修复它|type|unstyled|depth|inlineStyleRanges|entityRanges|data|287187|该时间与站点time.in的时间约为1秒，因此没有关闭。|287188|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Rebooting my windows server fixed it for me
The time was identical to ~1 second to the site time.in, so it wasn't off.

blocks|key|287260|text|如果您使用的是虚拟机，那么重启虚拟机也可以在我的虚拟机上运行|type|unstyled|depth|inlineStyleRanges|entityRanges|data|287261|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you're working with a VM, restarting the VM just works on mine

blocks|key|283635|text|%2B1+@sompnd+-在运行wsl+--shutdown之后，我能够在容器中执行命令行界面命令|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|283636|entityMap^0|F|E|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

+1 @sompnd - I was able to execute CLI commands in a container after running <code>wsl --shutdown</code>

blocks|key|2996664|text|我在我的Mac上也遇到了同样的问题。当我移动到一个不同的时区(PST到IST)时，OSX不知何故没有自动选择时区和时间更改。所以我不得不手动设置这两个参数，这导致我的笔记本电脑出现了大约15-20秒的延迟。设置自动同步后，时间得到同步，S3复制命令开始工作：For+reference|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2996665|entityMap|0|LINK|mutability|MUTABLE|url|https://i.stack.imgur.com/Wn8bk.png^0|3L|D|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I was running into the same issue on my Mac. When I moved to a different timezone(PST to IST), somehow OSX was not picking timezone and time change automatically. So I had to set the two manually and that caused a lag of some 15-20 seconds on my laptop. After setting the automatic sync, the time got synched and the S3 copy command started working: <a href="https://i.stack.imgur.com/Wn8bk.png" rel="nofollow noreferrer">For reference</a>

blocks|key|3209960|text|这有点粗糙，但这对我很有效|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3209961|3209962|对s3服务器执行了curl|ordered-list-item|3209963|3209964|curl+s3.amazonaws.com+-v|offset|length|style|CODE|3209965|然后得到了这个|3209966|*+Trying+52.216.141.158...
*+TCP_NODELAY+set
*+Connected+to+s3.amazonaws.com+(52.216.141.158)+port+80+(#0)
>+GET+/+HTTP/1.1
>+Host:+s3.amazonaws.com
>+User-Agent:+curl/7.64.1
>+Accept:+*/*
>
<+HTTP/1.1+307+Temporary+Redirect
<+x-amz-id-2:+q2wUOf5ZC7iu2ymbRWUpZaM6GpPLLf/irrntuw/JNB7QYxDzQvcLHQbsbF2dp5zT8rBrGwqnOz0=
<+x-amz-request-id:+T4H1W4WKBE3F39RM
<+Date:+Sat,+09+Oct+2021+19:21:24+GMT
<+Location:+https://aws.amazon.com/s3/
<+Server:+AmazonS3
<+Content-Length:+0
<
*+Connection+#0+to+host+s3.amazonaws.com+left+intact
*+Closing+connection+0|code-block|syntax|javascript|3209967|3209968|得到了这个日期Sat,+09+Oct+2021+19:21:24+GMT|3209969|3209970|在ubuntu+sudo+date+--set+"Sat,+09+Oct+2021+19:21:24+GMT"中|3209971|设置日期|3209972|3209973|我的代码停止了抛出异常，现在我有了一个每个月定期抛出异常的脚本|3209974|entityMap^0|0|0|0|0|0|O|0|0|0|0|7|T|0|0|8|1B|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|18|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1A|8|@$I|1B|J|1C|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1D|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1E|8|@]|9|@]|A|$R|S]]|$1|T|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|U|3|V|5|E|7|1G|8|@$I|1H|J|1I|K|L]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1K|8|@$I|1L|J|1M|K|L]]|9|@]|A|$]]|$1|Z|3|10|5|E|7|1N|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1P|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|15|$]]

It is a little crude but this worked for me
<ol>
<li>Did a curl to s3 server
<code>curl s3.amazonaws.com -v</code>
</li>
</ol>
Then got this
<pre><code>* Trying 52.216.141.158...
* TCP_NODELAY set
* Connected to s3.amazonaws.com (52.216.141.158) port 80 (#0)
&gt; GET / HTTP/1.1
&gt; Host: s3.amazonaws.com
&gt; User-Agent: curl/7.64.1
&gt; Accept: */*
&gt;
&lt; HTTP/1.1 307 Temporary Redirect
&lt; x-amz-id-2: q2wUOf5ZC7iu2ymbRWUpZaM6GpPLLf/irrntuw/JNB7QYxDzQvcLHQbsbF2dp5zT8rBrGwqnOz0=
&lt; x-amz-request-id: T4H1W4WKBE3F39RM
&lt; Date: Sat, 09 Oct 2021 19:21:24 GMT
&lt; Location: https://aws.amazon.com/s3/
&lt; Server: AmazonS3
&lt; Content-Length: 0
&lt;
* Connection #0 to host s3.amazonaws.com left intact
* Closing connection 0
</code></pre>
<ol start="2">
<li>Got this date
<code>Sat, 09 Oct 2021 19:21:24 GMT</code>
</li>
<li>Set the date in ubuntu
<code>sudo date --set &quot;Sat, 09 Oct 2021 19:21:24 GMT&quot;</code>
</li>
</ol>
My code stopped throwing exceptions
Now I have a script that does this periodically every month

I have error The difference between the request time and the current time is too large when call method amazons3.ListObjects

<pre><code>ListObjectsRequest request = new ListObjectsRequest() {
 BucketName = BucketName, Prefix = fullKey 
}; 
using (ListObjectsResponse response = s3Client.ListObjects(request))
{
 bool result = response.S3Objects.Count &gt; 0;

 return result;
}
</code></pre>

What it could be?

S3 Error: The difference between the request time and the current time is too large

当调用方法amazons3.ListObjects时，我有错误请求时间和当前时间的差太大ListObjectsRequest request = new ListObjectsRequest() {    BucketName = BucketName, Prefix = fullKey }; using (ListObjectsResponse response = s3Client.ListO

问S3错误:请求时间与当前时间相差太大
EN

回答 27

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问S3错误:请求时间与当前时间相差太大EN

回答 27

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问S3错误:请求时间与当前时间相差太大
EN