Google Cloud Storage Bucket won't let me share files - google-cloud-storage

I'm trying to host files on a Google Cloud Bucket. I've used the service before, but now it's acting up on me with a new bucket for a different client.
For some reason, when I click the "Share Publicly" checkbox, it instantly unchecks itself and refuses to share the file.
Can anyone tell me how to fix this?
Update: After more experimentation, I've found that my client's account completely refuses to allow sharing for some unexplained reason. He's entered his billing information and is still on Trial time, but I don't know if that has anything to do with the issue. I've tried creating other buckets and modifying permissions with GSUTIL but no luck.

Related

Can't add application as super admin

I am attempting to add the "Amazon Web Services" Application to Google Workspaces.
I have been assigned the super admin role, in the admin dashboard. So, to the best of my knowledge, I should have permissions to add an application. But I keep getting the error message "Can't add Amazon Web Services. Please try again.". Which unfortunately is not particularly helpful in trying to understand what the problem is. I have tried different browsers, signing out/in etc. all to no avail.
However I must be missing something as the organisation owner is able to add the application with no issues, does anyone have any idea what could be preventing me from doing this?
Just to add, I have confirmed that I have the same roles attached as the organisation owner.
If your account has been assigned the role recently it is expected as it usually takes up to 24hrs for a role to fully propagate. After that you should be able to add it with no issues.
That is documented here

Access Changed on Google Cloud storage

I had a simple Google Cloud Storage Account (for the last 5 years) that I had a small online backup service offering for my clients.
About a month or so ago I began getting messages about my "Trial" was expiring ... I ignored it mostly since I had not setup a trial anything. Then about a couple of weeks ago, my backup service quite working with the message I had no cloud account.
I went back and found the emails and clicked and "Upgraded" the account (which again I have no idea why since I have been paying Google Cloud Storage for years) and the backup began to work again.
But now when I go to look at the Project it states I have no permission for anything. I had access until this garbage happened ... of course there is absolutely no way to get support from Google.
I have tried to see how to give me admin access again, but there does not seem to be any way to do this ...
BTW ... I am the only login
Help please
about a year ago, some requirements were changed with GCP and storage. as such, you will need to ensure you have an attached billing account and manager access on the accounts that you are using to back up with. Typically these are service accounts with service credentials.
You can find the IAM roles here: https://console.cloud.google.com/iam-admin/iam
you will have to ensure you are in the correct project, then select the user that you are using to authorize with the backup service (or potentially create one).
Then you will want to edit the roles this account has with any of the following, or their subset permissions:
Storage Admin
Storage Transfer
Storage Object Admin
I also highly recommend getting a Google/Firebase technician to look at your GCP project, you can contact them through support here as they can debug if there are any backend issues. Just clarify that your project may not be a Firebase project. They are often more helpful than typical Google Support.
https://firebase.google.com/support/troubleshooter/contact
Update:
If for some reason your account was hijacked or migrated to an account you don't have access to when you should. contacting GCP support is your best option, they are able to restore access, roll back changes, and otherwise assist with any potential lockouts you have.

Azure Devops "You do not have permission to attach files to work items in the current area path."

I am trying to add an attachment to a work item in Azure Devops. I am an administrator for the project and Area path. When I attempt to add an attachment I get the error "You do not have permission to attach files to work items in the current area path." I have searched and searched but can't figure out which permission I am missing. Does anyone know which permission I should give myself?
I figured it out this morning. One of my coworkers had a theory to try. It appears it is not being allowed when connected to our VPN. When I attempt it with out being connected to the VPN it works as expected. Hope this says someone hours of research.
I can't reproduce same issue like yours, but I think it's may not a simple permission-related issue.
Check the project configuration page and make sure all related permissions for specific user are allowed.
Search the user name and try allowing all permissions here and do the test again:
Then use a edge/chrome browser(after cleaning the cache), sign-out and sign-in the web portal again to check if the issue disappears.

Google Cloud Storage "upload cannot be completed" w/ error: "storage.objects.create"

Been using the Google Cloud Storage to upload archives of my files weekly, until suddenly this error now appears.
Upload cannot be completed
You don't have permission to upload files to this bucket. Contact the bucket or project owner to be given the "storage.objects.create" permission.
I have tried to grant myself the storage.objects.create permission, even when on the very same page I can verify I have that very permission it still complains that I do not have it.
This is a typical U.I. internal issue on GCP. More people had this issue and it was solved. You can use the upload button as a workaround, but in order to solve it you have 2 options. In case you are entitled to have support you can open a support ticket, stating your context. The other option, in case you are not entitled for support is creating a public issue tracker.
To investigate this issue further, the entitled teams will need you to record a HTTP Archive HAR while
recreating the steps that led to the error, then attach the saved HAR file to
the issue description. HAR files contain header and request information for a browsing
session and are useful for troubleshooting a variety of problems. Detailed
instructions can be found here.
A HAR file can contain sensitive information including, but not limited to,
passwords, cookies, private keys and credit card numbers. As such, it is better that you review the generated HAR file, and sanitize it of any such
information.
Additionally, it is advised that you sign out of any sessions that were active
during the time that the HAR file was generated in order to invalidate them.
Incognito mode is not enough to guarantee this, as the session may still be
active, even after closing the incognito window.

Unable to create buckets

After following https://developers.google.com/storage/docs/signup step by step, I'm unable to create any buckets.
Expected results:
Follow Guide, activate cloud storage, enter billing information
Reality:
When clicking on the Cloud console, I see "Invalid Credentials"
When I click create new bucket, once again I receive "Invalid Credentials"
I've logged off and on, waited a couple of days, tried different applications, but have not been able to use the cloud service.
Billing Screenshot 1
Billing Screenshot 2
API Enabled Screenshot
Credential Failure Screenshot
I'm currently using the file service which is to be discontinued at some point, so I need to get this working.
The account I'm using with app engine has been working well since the app engine beta many years ago, and I'm still being billed on other applications so I don't see a rhyme or reason why this isn't working properly. I did go ahead and logged out of google, cleared cookies, cache etc and created a fresh account and still received same error message. Tried a couple of different credit cards as well. Using firefox, but did try chrome as well.
Thanks!
2014-03-30 Turned out I needed to use Chrome, unknown why Chrome didn't work on first attempt.