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
Error: Bucket Policy Only #80
Comments
I just hit this too, I was able to upload a period ago (I don't remember, mine is a development server, so I can't place exactly when I last used the upload functionality). But, I know nothing has changed in terms of my GCP buckets, or my GCS integration. |
Possibly related to this? I see that The dates aren't exactly close (11 months) but might be something to start with. |
I found this problem too.
|
I got the same error, any thoughts guys? |
Thank you @LorenzoSapora for the prompt response. 🙂 Is it possible to make the bucket publicly accessible using I'm using Terraform to create the bucket this way, and by changing Do I need to change anything else on the bucket level to make it accessible publicly for everyone to read with fine-grained? 🤔 (i.e.: adding new role or something?)
|
Sorry my stupid mistake. 😄 |
@tao I believe this is the problem https://github.com/Superbalist/flysystem-google-cloud-storage/blob/f3ec295003c52502a33ef8b97ed1b184ffb89871/src/GoogleStorageAdapter.php#L148
|
Sorry, I can't confirm if this fixes the issue anymore. I find google cloud quite frustrating to use so I switched back to AWS. |
For new or buckets less than 90 days old the solution from @LorenzoSapora works. For existing buckets older than 90 days this isn't allowed by Google. Google themselves suggest creating a new bucket. From what I can see this is the only solutipon until Superbalist/flysystem-google-cloud-storage#114 is merged. |
Google Cloud Storage buckets have an option to define access control on the whole bucket instead of the per object approach:
Using such a bucket results in error:
Is this package compatible with these buckets?
The text was updated successfully, but these errors were encountered: