I use google cloud storage connected to a google app engine in the same project. Recently, my google cloud storage was disabled after a billing failure with the message below:
AccountProblemYour Google account is not currently enabled for this operation.
Please check https://code.google.com/apis/console/#:billing to see if you have a past due balance or if the credit card (or other payment mechanism) on your account is expired. You can find additional information at https://developers.google.com/storage/docs/signup
Therefore, I have paid immediately with my other payment method. However, I am still getting the same message from google.
What else should I do to reactivate my google cloud storage?
I had the same issue.
Issue Description
Account was deactivated due to an expired credit card.
Cloud Storage started failing with the message...
<Error>
<Code>AccountProblem</Code>
<Message>
Your Google account is not currently enabled for this operation. Please check https://code.google.com/apis/console/#:billing to see if you have a past due balance or if the credit card (or other payment mechanism) on your account is expired. You can find additional information at https://developers.google.com/storage/docs/signup
</Message>
</Error>
Within my Cloud Console project, in Storage > Cloud Storage > Storage browser, I had a message like "You can use Cloud Storage after you enable billing", followed by a big Enable button.
I clicked the Enable button, it went away and seemed to work, but I got the same error when trying to view files, and after refreshing the Storage browser screen, the message was back.
Issue Resolution
I resolved the issue by disabling billing for the entire project (not just on the Cloud storage screen), then re-enabling it. Within the project, click Billing & settings, then Disable billing. Then re-enable.
Related
For example, if an instance uses too much memory, or due to the max instance limit no new instance can be started, or the app goes over some other limit due to too much traffic.
In those case does App Engine notify the admin automatically?
Or is it the app admin's job to keep an eye on the app and notice if it's overloaded?
There's no automatic way to do that with Google App Engine only.
However, you have the option to use Stackdriver in order to set alerts to be notified whenever some metrics exceed a threshold that you've set up. To do so:
Navigate to Monitoring > Alerting
Click on "Create policy" at the top of the page
Under the Add Condition button you can select GAE_APP as resource and then the Metrics you want to watch.
You can also edit the notification channels at the Monitoring > Alerting dashboard.
Here you will be able to find all the documentation on who to create Alerts.
The full list of metrics available for Google App Engine can also be found in the documentation.
My app engine is running in free quote. Today quota usage is exceeded (28 hours per day). All client requests are rejected with "Over quota" exception.
I enabled billing in my admin console (Settings -> Project billing status -> enable billing). I have valid credit card in billing settings, but still instances are not provisioned and client requests are rejected with same error.
What should I do to get the instances provisioned immediately.
Contacted google support and they mentioned that in addition to enabling billing, I need to set daily quota for my app engine.
In admin console on left side panel, under Compute -> AppEngine -> settings -> edit application settings and set daily budget.
I could see instances provisioned after this setting and client requests are getting processed.
I am trying to test out the Google App Engine. I have created an appspot domain, downloaded the sample project and put in all credentials required. I have also enabled Google Cloud Messaging for Android.
When I hit the send button (in the samples GuestBookActivity), I get the message:
"The backend is locked down. The administrator can change the authentication/authorization settings on [my appspot domain]".
Does anyone know about this issue and how to resolve it?
As #Peter Knego said, see point 8 here: https://developers.google.com/cloud/samples/mbs/deploy_backend
I had forgot to open my server for development use.
What happens if app deployed to GAE reach free quote limit (in case billing disabled)? Google will charge you for using resources above free quote or your app will become unavailable until free quota will be reset or billing will be enabled ?
According to Google App Engine documentation, Google will not charge you, they will disable the depleted resource.
You will see some kind of default 500 Server Error page with Google's Robot image.
Or you can build a custom static HTML error page as well, refer to the docs on configuring app.yaml -> custom error response
Even if billing is enabled, since you can set a daily budget, the above still stands when your budget is reached. Google say they will never charge anything above the budget you set.
We've exceeded the Max Daily Budget for our app, but we can't increase the budget due to a serious flaw in Google's billing system. Google App Engine and Google Wallet do not have very capable support for multiple sign-in. As a result, I went to change the budget, but it used the wrong Google Wallet account (a different Google Account I was signed in as). I had to go back and try again, but now our GAE app shows the following status:
Billing Status: Changing Daily Budget
Your account has been locked while we process your budget changes. If you were redirected to Google Checkout but did not complete the process, your settings will remain unchanged. (You will be able to make changes to your budget settings again once the outstanding payment is processed.)
Now I'm completely prevented from making any billing changes, our app is shut off (over quota), and I have NOTHING I can do to fix it. This is a seriously fundamental flaw in App Engine's billing system and Google Wallet integration.
Has anyone run into this before? Is there a workaround anyone is aware of?
Right now, our production app is completely down thanks to this issue.
Any help you can offer would be greatly appreciated?
If you're from Google and you might be able to help on the backend, our app id is "nhldraftpik".
Thanks!
Brian
This happens when you are connected to the wrong Google Wallet account.
If you have this issue again, please check that you are connected through the good Google Wallet.
If not, please click on logout, then login using the good account (without hitting the Back button).