amplify-cli: Amplify push fails with Connection timed out after 120000ms

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the Amplify Console GitHub Issue Tracker

Describe the bug I just upgraded amplify cli to 4.30.0, from a few versions back, and now I am unable to perform an amplify push that I was able to do prior to the upgrade.

The following error is thrown:

Connection timed out after 120000ms
An error occurred during the push operation: Connection timed out after 120000ms

Amplify CLI Version 4.30.0

To Reproduce Upgrade to v 4.30.0 Run and amplify push

Expected behavior It should push without an error

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: Windows 10 (PowerShell)
  • Node Version: v12.18.3

Additional context I’m gonna start rolling back to old versions, but it would be nice to know how to resolve this; thanks.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 3
  • Comments: 17 (4 by maintainers)

Most upvoted comments

Hi @kaustavghosh06 and @kimfucious

I’m facing the same issue right now… I did a bash script to build my Node.js lambda, once they were coded using Typescript I needed to do it. But when I run “amplify push -y” I’m always getting the error below:

Connection timed out after 120000ms
An error occurred during the push operation: Connection timed out after 120000ms

image

But the weird thing is that if I just update one resource like my API Gateway, so then I don’t get any error, and it works fine!

Amplify CLI Version Screen Shot 2021-03-30 at 18 44 51

Any help guys ?

So this problem is still persisting for me. The issue for me is that my project has a lot of lambda functions. When I use amplify push on a newly created environment i get timeouts because my upload speed is not the greatest. Maybe increase the timeout threshold?

I get this same issue as well. I have to use amplify push several times before cli gets passed “uploading files…” state. I am pretty sure it is a network / firewall issue since I never get this issue at Home, but when I am at my friends house I do. Not sure how to fix though