I have a golang program running on my local laptop. I had a previous Google Cloud account that I used to upload images to a bucket (using gcloud local context). It worked.
I created another company branded Google Cloud account and linked our company card to it.
Ever since then I get the error in the title.
I contacted support and got this:
Hi,
Unfortunately we are not able to identify any abuse related actions taken on your project. To resolve this issue, please reach out to the Google Cloud Platform community support.
Sincerely,
Google Cloud Platform/API Trust & Safety Team
Do you guys have any ideas? Any help would be much appreciated.
The problem turned out to be that the JWT json file being used by my project for authentication was out-of-date.
I had to re-download a new JWT json file from the cloud console and put it in the root of my project folder.
Related
I just started Google Messaging APIs 3-5 days ago and couldn't figure out what did I go wrong. I already sent/asked this issue to Google's Support page.
Project is under my generic google account. I created a Service Account under this project for info#ourdomain.com and added it as a Project > Editor role. Got this Json keys, uploaded them together with my python Echo Bot files.
Done registering my partner account as well (info#ourdomain.com) and got verified with the Project Number connected that's in my generic google account. I don't know if this is the right setup where my partner account and project ID are from different Google Accounts (info#ourdomain.com and generic#gmail.com, respectively).
Echo bot sample I used: https://github.com/google-business-communications/bm-python-echo-bot/tree/master/full_sample
Logs:
I'm very familiar with programming Google's services but was unaware of Business Messages until I saw your question (it's interesting, thanks).
There are a couple of references to "select the project that you registered for Business Messages".
Often Google enable non-GA|non-public APIs and other functionality (sometimes by injecting service accounts into the project's policy) by having users register Project IDs and Google accounts. I suspect that's what's happening here and the functionality is either blocked or not working entirely by your use of a different Project.
You may be able to gain more insight from the problem by checking logs. IIUC, an App Engine app is deploy and you should be able to gcloud app logs read --project=[[YOUR-PROJECT-ID]] (or gcloud app logs tail --project=[[YOUR-PROJECT-ID]])
I am currently working on an application where I would like to upload videos and images to a Wasabi s3 bucket in Flutter. I first attempted to use amplify_flutter, but this did not work because as detailed in their setup guide I am required to log into Amazon Web Services in order to configure the package.
I did find another stack overflow answer describing how to upload to AWS with an https request. copying this code did give me the ability to connect with https://s3.wasabisys.comm, but when using a POST request to upload the files, the url returns this error message:
<Error><Code>MethodNotAllowed</Code><Message>The specified method is not allowed against this
resource.</Message><RequestId>9E0DDF6269E6C862</RequestId>
<HostId>rLX8KeJ9ZPbk6+Zy+GvXUgG1f8ffJ8cNK92KUBnd8DLruqbWbX7dWyKy37N4IoHtqp41+ctRVEBC</HostId></Error>
I did find a post on the AWS forums describing the same issue, and they stated that a "CloudFront Origin Access Identity" needs to be enabled, but since I am not using CloudFront either, enabling this option is not possible for me.
In Wasabi, is there an option similar to "CloudFront Origin Access Identity" that I can enable in order to allow POST requests to a bucket, or is there a better option in Flutter to upload to Wasabi s3 buckets?
Update: I was able to solve this by using the Minio flutter package. We have been using this package for a couple weeks now without any issue to connect to Wasabi.
I imported an old project into Firebase when I joined.
On the https://console.firebase.google.com/project/project-name/overview page, when I try to grab the code snippet to initialize my Firebase, the storage bucket shows up with empty URL.
Today, I started a new project, this time, using the Firebase console. After creating the project, the StorageBucket URL showed up in the initialization code snippet automatically.
When I check both project's storage rules, I see the URL pointing to the right places, however, the imported project gives this error under the Storage > Files tab:
It has been like this since day one I imported the project.
When I went to https://console.cloud.google.com/storage/browser to see if the new project I created would show, it did.
Are there any extra steps on my part to get the storage bucket URL to show for the imported project?
Who's this answer for?
If you imported your project into Firebase and having the above issue specifically with your Firebase Storage.
After back and forth with Firebase Support, if you're facing similar problems as mine, here's the approach you can try. I'm trying to replay the conversation and steps given by the Firebase Support
Make sure that you are the owner of the project you are accessing.
If you have multiple Google accounts signed in, Firebase Database can't
seem to connect to the server. Sign into incognito mode
Check in your API Manager if the following are enabled
a) App Engine admin API
b) Firebase Rules API
c) Google Cloud Storage
Check if you have an App Engine app is enabled https://console.developers.google.com/project/_/appengine
Go to Firebase Storage AppManager tab
https://console.cloud.google.com/storage/
a) Add the service account firebase-storage#system.gserviceaccount.com as an owner on the storage bucket: .appspot.com.
b) Additionally, you need to edit the "object default permissions" to allow for similar access.
Now, if you have all the above in place, next step is this:
Add new Server Credentials
In credentials page, ( https://console.developers.google.com/apis/credentials ),
click Create credentials, select API key
Select server key
Put name as "Server key (auto created by Google Service)"
At the time of writing this, creating the Server Key was what got it to work.
A few words:
The issue of not able to use Firebase properly when two accounts are logged in the same browser doesn't plague me anymore. Logged into two accounts, and both Firebase projects are up and running without any issue.
I fixed mine by using the command to work on it using
firebase init storage
This would create the storage after that it would add a storage.rule in which you can update to your liking in your project .
Then you run this command
firebase deploy --only storage
This would initialize the Storage
If you are still having issues check out this link https://stackoverflow.com/a/74750337 which was also provided by firebase for me to fix the error
This is how i fixed mine
I generated Access & Secret Key put it into Bucket Explorer just as I saw on their screenshots but I get an error that Keys are not recognized on AWS, so it keeps trying to connect to AWS. I have latest version for OS X.
Looking at the Bucket Explorer website, it sounds like you need a special version of their software -- however, the download link does not actually seem to have that version available. Have you contact the developers of Bucket Explorer about it?
Alternatively, you can use the Google Cloud Console to upload and access your data in Google Cloud Storage without depending on a particular client application.
I have an old GAE application (in production since 2011) that use Cloud Storage service since it is available in beta. I have not touched this apps for almost 1 year now.
I have to do some administrative task and want to create new buckets in Cloud Storage.
I have activated
- the application in Google Cloud Console
- the billing for this application in Google Cloud Console
I see the Google Cloud Storage tab, when I click on it it is empty, and when I try to create a new bucket I see the error message:
The account for the specified project has been disabled.
How can I fix that?
Why I do not see my existing bucket? (created long time ago using the old Web interface)
Thanks!
This can happen when the Cloud Storage service isn't turned on for your project. Do the following:
Visit http://cloud.google.com/console
Select your project
Visit the APIs & Auth tab
Find Google Cloud Storage in the list of services
Turn on Google Cloud Storage
I was facing the same issue .While every API was enabled after deep diving i realized there is some problem relating to my billing.