放大init-无效的签名Exception：签名尚未当前

发布于 2025-02-02 15:57:41 字数 2708 浏览 2 评论 0原文

遇到并解决了这个问题。为后代发布，因为我的情况与通常的情况有所不同。

重要的：我在刚安装的Windows主机上的虚拟盒VM中运行了Ubuntu的衍生物。

问题

使用Create-react-app创建新的React Amplify项目时的

$ amplify init
...
For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html

? Please choose the profile you want to use default

InvalidSignatureException: Signature not yet current: 20220528T081112Z is still later than 20220528T051608Z (20220528T051108Z + 5 min.)
    at Object.extractError (/snapshot/node_modules/aws-sdk/lib/protocol/json.js:52:27)
    at Request.extractError (/snapshot/node_modules/aws-sdk/lib/protocol/rest_json.js:49:8)
    at Request.callListeners (/snapshot/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/snapshot/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
...
    at IncomingMessage.EventEmitter.emit (domain.js:483:12)
    at endReadableNT (_stream_readable.js:1241:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  code: 'InvalidSignatureException',
  time: 2022-05-28T08:11:12.872Z,
  requestId: 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX',
  statusCode: 403,
  retryable: false,
  retryDelay: 35.74742577991159
}

，Amplify INIT在选择一个配置文件后，InvelidSignature Exception：我还经历了amplify的错误。按下和放大拉力抱怨诸如“ time Skew”和“ timeouts”之类的内容，而AWS控制台投掷“列表应用程序” call call失败：网络错误”。

类似的帖子

Here are a sample of posts discussing similar problems.

'amplify init'保持失败

https://github.com/aws-aws-amplify/amplify-js/issues/2014

https://github.com/concourse/s3-resource/s3-resource/34

https://github.com/aws-aws-amplify/amplify/amplify/amplify-hosting/amplify-hosting/issues/issues/2417

失败。

Sample of failed ideas:

我尝试创建第二个项目，以查看问题是否持续做到了。
我尝试通过ntp，ntpdate，ntpd同步时间。相同的错误。
我尝试通过GUI设定时间。未能设置。相同的错误。

在这一点上，我注意到解决方案的故事

，我注意到我的时间偶尔会与ntpd同步。实际时间是01:40；在同步时，它跳至04:40，然后返回01:40。这将间歇性地发生在同步时。时带正确设置了。反复试验会耗尽我的想法，所以我回到主人。主机时间为01:40，但不和谐消息是在10:40的时间戳。等待。

原文

Encountered and solved this problem. Posting for posterity since my situation differed from the usual.

Important: I am running a derivative of Ubuntu in a VirtualBox VM on a freshly installed Windows host.

The Problem

When creating a new react amplify project using create-react-app, amplify init fails with an InvalidSignatureException after selecting a profile:

$ amplify init
...
For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html

? Please choose the profile you want to use default

InvalidSignatureException: Signature not yet current: 20220528T081112Z is still later than 20220528T051608Z (20220528T051108Z + 5 min.)
    at Object.extractError (/snapshot/node_modules/aws-sdk/lib/protocol/json.js:52:27)
    at Request.extractError (/snapshot/node_modules/aws-sdk/lib/protocol/rest_json.js:49:8)
    at Request.callListeners (/snapshot/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/snapshot/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
...
    at IncomingMessage.EventEmitter.emit (domain.js:483:12)
    at endReadableNT (_stream_readable.js:1241:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  code: 'InvalidSignatureException',
  time: 2022-05-28T08:11:12.872Z,
  requestId: 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX',
  statusCode: 403,
  retryable: false,
  retryDelay: 35.74742577991159
}

I also experienced errors with amplify push and amplify pull complaining about things such as "Time skew" and "Timeouts", and AWS Console threw "List apps call failed: Network Error".

Failed ideas

Sample of failed ideas:

I tried creating a second project to see if problem persisted. It did.
I tried syncing my time via ntp, ntpdate, ntpd. Same error.
I tried setting time via GUI. Failed to set. Same error.

Story leading to solution

At this point, I noticed my time occasionally jumps on sync with ntpd. Actual time was 01:40; on sync, it jump to 04:40, then back to 01:40. This would occur intermittently on sync. Timezones were set correctly. Trial and error exhausts my ideas, so I return to my host. Host time is 01:40, but discord messages are timestamping at 10:40. Wait.

分享到QQ

分享到微博