1 Resposta
- Mais recentes
- Mais votos
- Mais comentários
0
With these kind of errors, it's always useful to check:
- CloudTrail for any API calls and returned errors
- The browser console to see what call failed Both can help diagnose the problem.
Conteúdo relevante
- Como personalizo a configuração do nginx para modificar “client_max_body_size” no Elastic Beanstalk?AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há 4 anos
- AWS OFICIALAtualizada há 10 meses
- AWS OFICIALAtualizada há 2 anos
Continued trying to work through this to get the application to upload for deployment to my Elastic Beanstalk applications. Zip file size is under 150MB, I have cleared out all local storage and cookie values. I have also removed all but the last 10 versions of my application ensuring they were in sync, and after "freeing" up space in S3.
Watching the browser network traffic in the Web Developer Tools and part of the way through the upload, a number of angular script requests start coming back as 401 errors. These errors occur whether the session has been used, a new login, or if in parallel another AWS page refreshes to update any security token timeouts while the upload is progressing.
Any assistance would be appreciated.
Has it ever worked? If so, has anything changed between deploys? Bucket permissions look okay?
Hi! I had the same problem. And the only way I found to get around this problem is to connect via aws(eb) cli, create an application version&deploy through it. This does not solve the problem but allows you to continue working. Links that helped me a lot: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3-getting-started.html https://stackoverflow.com/questions/60139095/how-to-upload-and-deploy-zip-file-to-aws-elastic-beanstalk-via-cli