Skip to content
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

CORS on b2.authorize() #136

Open
Casal0x opened this issue Apr 29, 2024 · 3 comments
Open

CORS on b2.authorize() #136

Casal0x opened this issue Apr 29, 2024 · 3 comments

Comments

@Casal0x
Copy link

Casal0x commented Apr 29, 2024

Hi all I'm trying to set up Backblaze for a nextjs app, but I'm getting cors error, in the first instance I thought that it was the bucket and I set the custom cors rules but it was not because I'm getting this error on b2.authorize().
I'm using it from localhost:3000

Has anyone experienced this issue? Do I have to use the master key?

`
async function uploadToB2(file: Blob) {
const b2 = new B2({
applicationKeyId: process.env.NEXT_PUBLIC_APPLICATION_KEY_ID as string,
applicationKey: process.env.NEXT_PUBLIC_APPLICATION_KEY as string,
});
const auth = await b2.authorize();

console.log(auth);
}
`

image image
@iKreateCode
Copy link

The fix to this is to set a cors rule using the cli:

b2 update-bucket --cors-rules '[
    {
        "corsRuleName": "downloadFromAnyOriginWithUpload", 
        "allowedOrigins": [
           "*"                    
        ],
        "allowedHeaders": [
            "authorization",
            "content-type",
            "x-bz-file-name",
            "x-bz-content-sha1"
        ],
        "allowedOperations": [
            "b2_download_file_by_id",
            "b2_download_file_by_name",
            "b2_upload_file",
            "b2_upload_part"
        ],
        "maxAgeSeconds": 3600
    }
]' (your bucket name)

you need to authorise in the cli before you can run this command

@Casal0x
Copy link
Author

Casal0x commented May 3, 2024

i was already done, thing is it wasn't working as a helper, I created a separated endpoint and it started working. something strange, that it blocks if it is been called from client side and not from server-side with next.

@iKreateCode
Copy link

Would you know how to fix cors error for downloading_file_by_name?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants