-
Notifications
You must be signed in to change notification settings - Fork 447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For some reason I keep getting 401 Authentication error after performing "Create your studio" action #50
Comments
I get this too, have you found solution to this? |
No, I haven't( |
I think I found solution, need to create bucket policy and cors policy on bucket |
What exact policy? I did it but it didn’t help. Could you share yours?
…On Mon, 17 Jul 2023 at 16:45, JustinMKY ***@***.***> wrote:
I think I found solution, need to create bucket policy and cors policy on
bucket
—
Reply to this email directly, view it on GitHub
<#50 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADYS7XWTL6JSUJWTPY3N3O3XQU6Y3ANCNFSM6AAAAAAZ54CWG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
My solution says the bucket is public though, I tried setting principals but for some reason it doesn't work and gives 401 error. Here is my set up though:
My bucket policy is
CORS policy on bucket
|
i get this error in browser POST https://last-vert.vercel.app/api/s3-upload 405 (anonymous) @ 226-1d6c8af1b9ec75f3.js:100 |
This seems like issues with s3 bucket permissions, check bucket permissions/CORS policies EDIT: I posted CORS policy above, maybe try that and see if it works. |
Nice , Thank You , It Worked |
One Last Help Man , |
I have not yet run into an issue like that, so wouldn't know, maybe check server logs and ensure replicate account have billing source added. |
I can't understand what causes this error, I've checked the S3 bucket permissions and policies and everything seems fine.
The text was updated successfully, but these errors were encountered: