dotnet eb deploy-environment command timeout

[burakiskender]

Getting a timeout issue when deploying my netcore app to EB. Here are the details :

Uploading to S3. (Bucket: elasticbeanstalk-ap-southeast-2-043897850050 Key: Pavoni/AWSDeploymentArchive_636847158216790790.zip)
... Progress: 10%
... Progress: 20%
... Progress: 30%
... Progress: 40%
... Progress: 50%
... Progress: 60%
... Progress: 70%
Error uploading application bundle to S3: Error uploading to App/AWSDeploymentArchive_App_636847158216790790.zip in bucket elasticbeanstalk-ap-southeast-2-043897850050: A task was canceled.

[klaytaybai]

Do you happen to be using a VPC for EB? That could explain it. You might not have access to your S3 bucket from your VPC, in which case you would need to set up a VPC endpoint (bucket policy examples)

[burakiskender]

Do you happen to be using a VPC for EB? That could explain it. You might not have access to your S3 bucket from your VPC, in which case you would need to set up a VPC endpoint (bucket policy examples)

Thanks klaytaybai. I confirmed that the EB account has full access to S3 bucket. Still no luck

[klaytaybai]

@burakiskender, I don't think should be the limiting factor, but how large is your file? Is your connection typically reliable?

[burakiskender]

@burakiskender, I don't think should be the limiting factor, but how large is your file? Is your connection typically reliable?

Nothing special my friend. 15 MB dotnetcore application. Upload via Ethernet . Cheers

[ashishdhingra]

Hi @burakiskender,

Good afternoon.

I was going through the backlog issues and came across this one. Please advise if this is still an issue or could be closed.

Thanks,
Ashish

[github-actions]

This issue has not recieved a response in 2 weeks. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.

[augustoproiete]

Do not close. We experience this timeout at least a couple of times a month.

[burakiskender]

@ashishdhingra
Hi Ashish, a bit odd but this issue happens on certain networks. If I switch to my phone hotspot , works fine. Corporate networks, other wifis fail time to time. Other commands works however.

[ashishdhingra]

Hi @augustoproiete @burakiskender,

As @burakiskender pointed out, the issue happens on certain networks. Not sure if this has something to do with the network configuration, corporate security policies, etc. and how we could troubleshoot the issue given this scenario. Not sure if you would want to do network monitoring and work with network team to do some kind of tracing for failed responses.

Thanks,
Ashish

[augustoproiete]

Hi @ashishdhingra, that has not been my experience so far. When dotnet eb deploy-environment fails for me, I cannot get it to work regardless of the network I'm using, for several minutes... Eventually it starts working again by itself.

Can we get dotnet eb deploy-environment to give us a detailed log of the URL(s) that it cannot reach (and payload being sent) when it happens?

[ashishdhingra]

@augustoproiete I don't see any command switch to turn on the verbose logging. You may try using Fiddler to monitor network traffic when you execute dotnet eb deploy-environment command and see which URL(s) are timing out. Hope this helps.

Thanks,
Ashish

[github-actions]

This issue has not recieved a response in 2 weeks. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.

[augustoproiete]

Hey @ashishdhingra, given that this timout only happens a couple of times a month it's not really possible to "predict" when it will happen (and then turn on Fiddler)... It's also not reasonable to have Fiddler (or similar tool) running 24/7 for several weeks on end.

Instead, can we use this issue as a feature request for dotnet eb deploy-environment to implement a more detailed diagnostic of any failures of the URL(s) that it cannot reach (and payload being sent) when an exception happens?

[ashishdhingra]

@augustoproiete Thanks got your reply. I have added feature-request label.

[github-actions]

We have noticed this issue has not received attention in 1 year. We will close this issue for now. If you think this is in error, please feel free to comment and reopen the issue.

[augustoproiete]

Feature request remains valid. Please keep it open.