Google Cloud Datastore Console - Service Unavailable 503 - google-app-engine

I am working on a Google Datastore integration and I have the following issue with Google's console. I have another Datastore project that is working correctly. I just dont understand why it returns 503 Service Unavailable. I created the project via my Google Accounts, so I am the owner of the account, it should be working. Any ideas?
Here is the issue:

Here is what worked for me. I added one project which was basically called something like my-project for production and my-project-dev for development. My project is working perfectly, but my-project-dev is not (refer to screenshots above).
So I created a new project and took the name that Google Datastore generated and that worked.

Related

Unable to create Google App Engine application

When I tried to create a Google App Engine application via gcloud app create at terminal on Ubuntu and on the web, it gives me the following error,
"ERROR: (gcloud.app.create) Error Response: [13] An internal error occurred while ensuring the default service account exists."
I guess the reason why I don't have the default service account because I deleted a default project on GCP which was made when I started using GCP, not sure though.
I made a service account at IAM & admin menu, but not work. Any idea?
Although I found this answer, it didn't work for me.
How to recover Google App Engine's "default service account"
But I didn't delete the default google app engine service account, it was missing at the first place. Maybe because I tried to create a GAE app on the web and left the page before it's done. I don't know.
Anyway, I make a new project and create a GAE app via gcloud cli, and now it's good to go.

AppEngine nodejs, random: The server encountered a temporary error and could not complete your request

I just deployed the helloworld app on Google App Engine Flexible Environment.
Randomly, let's say, one each 3-4 requests, I get this:
The only change I've made from the original helloworld code provided in google cloud docs was that I changed the automatic scaling to manual and set it to 1 instance.
Anyways, I deployed the same docker image in Container Engine, and it works perfect.
There is nothing on the app logs, the request does not reach the app.
Something is not working with GAE Flexible Env. load balancer, any ideas?
I destroyed all the instances and deleted the service. After 24hs tried to create it again and now it is working good.

Upload Data to Appspot Deployment "Authentication Failed"

I have created a python app on my local app engine dev server using the 1.7.1 SDK. I frequently load data into it using appcfg.py and upload_data with csv data files and remote_api. (It works great!)
I have now deployed the app to Google App Engine appspot.com under a gmail account without any errors and selected (Federated) OpenID to be used for end user login.
However, when I try to upload data to the deployed app using appcfg.py, I get an "[INFO ] Authentication Failed" error.
I have googled for several days now looking for solutions, but I'm finding conflicting suggestions. Nick Johnson has an old workaround on his blog, but more recently people have reported it does not work. The SDK's appcfg.py supports an --oauth2 option now, but I can not find concise instructions on how to use it from a command line batch file -- besides the documentation says it does not work with upload_data.
I have submitted this problem as a bug to the Google App Engine issue tracker.
I use the --no_cookies command line option. Per Google's suggestion, I tried again after switching my app from OpenID to the Google Accts API, but that failed too.
Does anyone know the current and preferred (working!) method to upload CSV data to a deployed python app? I don't think that uploading data to a deployed app is an "edge case", is it?!

Deploying PlayFramework Application to Google App Engine

For my new project I am planning to use PlayFramework and Google App-Engine. I was trying to create a sample application in playframework and tried to deploy it to app-engine.
it says the application is deployed successfully, but when I hit the url of my application
it shows a message "Your application is ready", But does not show the home page of my application.
I am using Play Framework 1.2 and GAE-1.4 plugin. I tried to deploy the application using the plugin and also using "appcfg".
The application works fine in local development mode but as soon as I deploy it to app-engine, the home page is replaced by "Your application is ready" message.
Can u guys tell me if I am doing anything wrong with the deployment of play-framework? I tried searching if anybody faced similar kind of issues in both google and SO but was not able to find any help.
Also, I read some post that GAE plugin does not work with Play-Framework 2.0(Note : I am using Play 1.2 in the above example) . I would like to know How can I deploy a play2.0 application in appengine.
Thanks a lot in advance!!!
Did you add application name and version number in appengine-web.xml before deploy?

Page not found on deploying Django-nonrel to Google App Engine

I'm a newbie to Google App Engine but have played around with Django in the past so I am trying to use Django-nonrel with GAE.
There's not much information online, but have followed these tutorials successfully:
http://blog.sidmitra.com/getting-up-and-running-with-django-nonrel
http://www.allbuttonspressed.com/projects/djangoappengine
I have managed to get setup fine and can get the 'It worked' page on local. However, when I upload my project to the Google App Engine Server I get a page with the following:
"Nonrel-testapp
The page you requested could not be found.
Powered by Django-nonrel"
I have used the following to upload:
python2.5 manage.py deploy
What am I doing wrong?
Are there any guides for uploading your Django app?
Thanks
You're not doing anything wrong. On the production server DEBUG is False, so you won't see that little "It worked" page. Since you're not the first one who was irritated by this I've just added a custom "It works!" page which also shows up on the production server. Just update your testapp source to see it.

Resources