help with cloud enpoint... cannot access in local testing...

Trez Ertzzer

unread,

Feb 3, 2016, 6:14:05 AM2/3/16

to Google App Engine

Hello.
I have a project created with the GPE.
this project contains Endpoints services that I can see when deployed on google app engine server.

BUT
when I launch the webapp locally through eclipse, and user chrome to go to http://localhost:8888/_ah/api/explorer
-->I do not see the endpoint services:

I clicked on the shield (in the adress bar), then I allow the scripts to be loaded... but no services endpoint appears.

I have to say that the worst is that IT WAS WORKING.... and now it's not and I have no idea why...

I created a new project from scratch...using this:
http://rominirani.com/2014/01/10/google-cloud-endpoints-tutorial-part-1/
--> SAME thing: cannot see the services.

I also tried to launch chrome using the "

--disable-web-security" option.
--> did not change anything...


really I need help...

thanks in advance.

Miguel Santos

unread,

Feb 4, 2016, 9:02:02 AM2/4/16

to Google App Engine

Hi, Trez.

I'm having this same problem. My best guess for now is that the problem is the Google Chrome current version (48).

I was using the version #47 and it was working. After updating chrome to #48, I'm facing this same problem.

Zeehad (Cloud Platform Support)

unread,

Feb 4, 2016, 1:29:16 PM2/4/16

to Google App Engine

Looks like it's a known issue in Chrome 48.x as it works fine on Firefox. Feel free to 'star' this issue in Chromium issue tracker to receive further updates.

Clément Prévot

unread,

Feb 5, 2016, 5:01:28 AM2/5/16

to Google App Engine

Hi!

It's indeed an issue related to the last version (48) of Chrome. I've met this problem as soon as it was released in the dev channel. I've not check if it has been solved with v50.

There is workaround that is a little bit 'dangerous' and that implies to allow Chrome to load any insecure content, without asking you to.

To do this, simply launch chrome using the flag "--allow-running-insecure-content" and you should be good to go.

But be aware of the implications of this flag and be extremely careful when using your "tweaked" browser.

Regards

Clément Prévot

unread,

Feb 10, 2016, 3:25:32 AM2/10/16

to Google App Engine

Good news, there is a new and better solution : https://developers.google.com/explorer-help/#hitting_local_api

Reply all

Reply to author

Forward