I have been trying repeatedly to run one of the mirror-quickstart packages off of my drupal website with little luck. I have been working with the java and .NET versions and have gotten both to work great when I run them off of localhost. However, when I try to move it to a page on my site I get the following errors
for the java application I go to www.mywebsite.com/Glassjava. I get redirected to www.mywebsite.com/oauth2callback with the following error:
Page not found
The requested page "/oauth2callback" could not be found.
For the .NET application I go to www.mywebsite.com/DN_glass. I get redirected to www.mywebsite.com/DN_glass/auth and get the error:
Page not found
The requested page "/DN_glass/auth" could not be found.
I have had success running the java off of localhost from a machine running IIS express after specifying the absolute path of the oauth.properties file and following these java servlet instructions: http://www.helicontech.com/articles/deploying-java-servlet-applications-on-windows-with-iis/
However, I have not gotten it to work on my drupal site. I don't understand the errors /oauth2callback and /auth. I am pretty sure I don't need to create any such directories and I also think that the oauth.properties file is getting read in order to communicate with the google api console and find the redirect URI (at least in the case of the java error). Any help with this problem would be greatly appreciated. Any suggestions about using the quickstarts with drupal and iis would also be appreciated.
Related
I am trying the GMail API Node.js quickstart on Windows 10.
I do get the expected
.
However when I visit the url I get
for http://localhost/?code=4/xxxxxxxxxxxxxxxxxx&scope=https://www.googleapis.com/auth/gmail.radonly
I get this error after going through 'This app isn't verified'/'Advanced > Go to {Project Name} (unsafe)'. message.
No Proxy active and also tried with AntiVirus disabled.
Any ideas what the problem could be?
Thanks.
The issue you are having is that you are runing a Authorization credentials for a desktop application. Google made a change recently which deprecated the oob redirect. This means that now you need to use localhost or 127.0.0.1 as a redirect endpoint for installed applications.
Resulting them in returning the authorization code back to the browser showing site can not be reached because your not running a web app you are running an installed application.
If you check the url the authorization code you are looking for to add to your code can be found there. just take that code and submit it where it asks for it.
Enter the code from that page here:
There is currently no other option and no way to fix this unless you want to start up a web server in node. basicly its working as intended and Google is in the process of updating all the Javascript samples to reflect that.
I've been following this tutorial: https://cloud.google.com/solutions/mobile/mobile-firebase-app-engine-flexible
I reached the step titled "Deploying the service to the App Engine flexible environment", and initially could not get it to deploy due to dm:true being deprecated. Changing <dm>true</dm> to <env>flex</env> in "appengine-web.xml" fixed this, and it now appears in the App Engine console as "serving". However, when I go to access the printLogs URL as instructed in the tutorial (or any URL connected to the project for that matter) I run into a 404 error. I am deploying from Windows 10 through the command prompt, and have installed everything instructed by the tutorial. I cannot figure out what is causing the 404 despite being told that it is running correctly.
You can go to the version in cloud platform and check the logs - it might tell you something.
However, I can tell you from experience that a lot of those projects are out of date and you can get all sorts of errors without changing a single line of code and following the instructions exactly. I've some of them say that they deploy, only to have errors just like the one you are describing.
It is very likely that you are NOT doing something wrong - check out some of the other projects and look specifically at pom.xml (or build.gradle) and app.yaml. See which versions of libraries they are including, and look for any differences. Try deploying a very limited project, and then build upwards and see what is breaking the code.
I have created an web application. It runs perfectly in localhost. when i deployed to Google App Engine, it works but one particular page is not running. It does not throw any exceptions but shows ERROR : NOT FOUND (404)
I understand this is file not found error but don't know why is this is error shown. even when i deploy it shows "application deployed successfully!".
can anyone help me to fix it.
thanks in advance!
Be careful with which slashes you use in your code when using paths and links. In windows, the backslash '\' is used, meanwhile Linux uses forward slashes '/'. Often this isin't an issue but it does cause problems once in a while. Also this explains why it would work fine on your localhost, but not once you deploy it.
I have been successfully using Netbeans to develop and deploy an app to the Google App Engine for ages through various application versions. That is all working normally and fine.
However (the problem), through the same account I created a new application (at the Google end) and at the application end the correct application id is in appengine-web.xml with a version of 1. All runs locally perfectly. But as soo as I deploy to GAE it fails:
com.google.appengine.tools.admin.HttpIoException: Error posting to URL:
404 Not Found
This application does not exist
Unable to update app: Error posting to URL: https://appengine.google.com/api/appversion/create?app_id=
404 Not Found
This application does not exist (app_id=u
Why??????
I have spent hours looking through the web for a solution. Lots of people have a similar problem but what is the solution? How can one app upload fine and the second fails?
PLEASE can someone give me some suggestions on how to fix the problem and successfully deploy?
I use Netbeans and have tried 6.9, 7.1, and 7.2 (I even tried installing Eclipse to solve the problem but it was horrendous to get going so I'm back to Netbeans). JDK 1.6.
Help!
Of course it works this way. After finally seeking help (from you chaps), within minutes I solve the problem (blind luck).
In case it helps anyone else, the basic issue was Google's account authentication model...
I needed to generate an application-specific password in Google Accounts (https://accounts.google.com/IssuedAuthSubTokens#accesscodes - that is, the Authorized Access to your Google Account area) to be used with the new application.
Then I needed to clear the existing email/password in Netbeans. This is a bit messy as I did that by deleting the 'deployment.properties' file you eventually find in C:\Users\User.netbeans\7.1\config\Preferences\org\netbeans\modules\j2ee\appengine.
You'll note I went back to Netbeans 7.1 because Netbeans 7.2 seems to store it in a different place which I couldn't find.
Back to Netbeans and hit the 'Deploy to Google App Engine' menu choice. It starts then asks for authentication. I used my normal (account) emailid and then the NEW application specific password. Miracle of miracles, it worked and the app fired up live.
I went and got a coffee
Perhaps Google could provide a slightly more meaningful error code than 404 Not Found???
Hopefully that helps anyone else with a similar problem.
Today, I had kind of the same problem. After some trial and error I found the solution.
Basically, starting from Netbeans 7.2. up, username and password are stored in something called "keyring".
In Windows 8 I found it under my current users directory: AppData\Roaming\NetBeans\7.3.1\config\Preferences\org\netbeans\modules\keyring.
I had to delete the GAE password information from the configuration file there. Then I cleared some registry keys (that might not be mandatory) and restarted Netbeans IDE. Then got prompted for new credentials.
See the full HowTo under:
http://donkeytech.wordpress.com/2013/08/06/change-google-app-engine-deployment-userdata-in-netbeans-from-7-2/
Using Eclipse, I am experiencing an error when trying to deploy a rather basic web app with JAX-RS and JAXB. It runs okay locally, but when trying it on the remote servers I get the message shown below...
'Deploying to Google' has encountered a problem / This application does not exist
Below shows my appengine-web.xml
The XML file illustrates that I am using the same name in the xml as what's specified in the project properties...
The output window show...
------------ Deploying frontend ------------
Preparing to deploy:
Created staging directory at: '/var/folders/n8/6by626014jbfc0dwmxnb0ly00000gn/T/appcfg2754901216637807129.tmp'
Scanning for jsp files.
Scanning files on local disk.
Initiating update.
com.google.appengine.tools.admin.HttpIoException: Error posting to URL: https://appengine.google.com/api/appversion/create?app_id=hillingarincident&version=0&
404 Not Found
This application does not exist (app_id=u'hillingarincident').
Debugging information may be found in /private/var/folders/n8/6by626014jbfc0dwmxnb0ly00000gn/T/appengine-deploy447984481661870877.log
The referenced debug logs show...
Unable to update:
com.google.appengine.tools.admin.HttpIoException: Error posting to URL: https://appengine.google.com/api/appversion/create?app_id=hillingarincident&version=0&
404 Not Found
This application does not exist (app_id=u'hillingarincident').
at com.google.appengine.tools.admin.AbstractServerConnection.send1(AbstractServerConnection.java:293)
at com.google.appengine.tools.admin.AbstractServerConnection.send(AbstractServerConnection.java:253)
at com.google.appengine.tools.admin.AbstractServerConnection.post(AbstractServerConnection.java:232)
at com.google.appengine.tools.admin.AppVersionUpload.send(AppVersionUpload.java:644)
at com.google.appengine.tools.admin.AppVersionUpload.beginTransaction(AppVersionUpload.java:449)
at com.google.appengine.tools.admin.AppVersionUpload.doUpload(AppVersionUpload.java:124)
at com.google.appengine.tools.admin.AppAdminImpl.doUpdate(AppAdminImpl.java:371)
at com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:53)
at com.google.appengine.eclipse.core.proxy.AppEngineBridgeImpl.deploy(AppEngineBridgeImpl.java:433)
at com.google.appengine.eclipse.core.deploy.DeployProjectJob.runInWorkspace(DeployProjectJob.java:148)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Any answers will be appreciated. At one point my browser was not logged in to the target google account, so I swapped to the correct one a little later, Google does render the application name as expected.
Okay, this was simple in the end! Eclipse performs an auto-login to the Google account, unfortunately I created the Eclipse project whilst being logged in to one Google account and then tried to specify the application name afterwards.
You'll see in the bottom-right (or bottom-left in some versions) a Google icon with the name of the user that you are logged in as. If that's not the account where your application is defined, then simply logout of that account, then login as the correct Google account.
Now there's no error :-)
I know this question is super old but I had this issue all day and finally I found a solution. Maybe it will help someone out in the future.
After you create a project in Google Cloud Platform, you must go to google cloud shell in your project and run the command
gcloud beta app create
After you run this command, you will get prompted to choose a region. Then go back to eclipse and try deploying it. It worked for me.
There are not just 1 way can cause this problem. For me, I have this problem when I create the project using Maven. But I don't have the same issue if I directly create the project from the Google plugin.
There might be another issue, when you register with Google App Engine, you receive email indicating your activation. If you have not received the email yet, this problem could occur too.
Another issue could be to use the gmail account for the Google App Engine to avoid any such errors.