- 최신
- 최다 투표
- 가장 많은 댓글
I had the same issue today. I needed to disable/override content-security-policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) in my browser to be able to upload my application zip file using the AWS Console.
That is the issue. Turning off CSP did not work for me unfortunately.
turning off CSP did not work for me either. Did you ever figure out another way to make it work?
I have been having the same issue. Disabling CSP headers using the chrome extension has helped https://www.ibm.com/support/pages/disabling-content-security-policy-csp
Thanks - this allowed the uploads to work again. Really hacky way to get around an AWS bug.
March 20, 2023. I have the same error. "Could not upload file: unknown exception" Disabling CSP headers using the chrome extension has not helped. In my case, after enabling the VPN <chrome extension>, the jar file was loaded without any errors on the first try. <I changed my IP from Ukraine to U.S.>
I also have the same issue periodically. This bug seems to reappear once every couple of months. It's happening today again (Aug-31-2022) on US-West-2 for me. @AWS, can this please be fixed for good?
(To clarify, as others answered, the issue is that CSP is misconfigured, so the only way to upload an application version in the AWS Console is to disable CSP in my browser)
관련 콘텐츠
AWS 공식업데이트됨 7달 전
I think that there are two AWS errors here.
The correct CSP headers are not being sent. This from the console. Refused to send form data to 'https://elasticbeanstalk-ap-southeast-2-197548791511.s3.ap-southeast-2.amazonaws.com/' because it violates the following Content Security Policy directive: "form-action 'self' https://console.aws.amazon.com/feedback/submit-feedback https://ap-southeast-2.signin.aws.amazon.com/oauth https://signin.aws.amazon.com/switchrole https://us-east-1.console.aws.amazon.com/feedback/submit-feedback https://ap-southeast-2.signin.aws.amazon.com/switchrole".
The error is not monitored and reported to the user leaving impression the upload is working when in fact it has died/failed
Yes I'm having the same issues. AP-SOUTHEAST-2 as well. Happened for me on the 27/9/21 aswell and was resolved by AWS in 24-48hrs. Glad you were able to post this issue.
Same here. Yesterday it worked, but I get this "Refused to send form data" today.
Same here on ap-northeast-1. Yesterday it worked, but not now.
Looks like the issue has been resolved again as of today.