[google-appengine] Re: Google App Engine Java deployment with gcloud skips almost all files

Per this article , currently the gcloud command-line tool does not deploy Java applications to production App Engine. So if you use the Cloud SDK to develop in Java on App Engine, you must use the

[google-appengine] Re: Google App Engine Endpoint Sample App Build issue

Hi, You may double check the steps you have taken for migrating to Endpoints Frameworks v2 for App Engine via this link and take a look at the common erratic behaviors

Re: [google-appengine] Re: Google App Engine end point App V1 to V2 Migration issue

The result of building your Java app is a *.war file. This should not be perceived as surprising, and should not prevent the deployment your endpoints. Have you attempted deployment, as yet? For reference, you may have a look at the "Deploying and Testing an API" online document

[google-appengine] Re: Google App Engine end point App V1 to V2 Migration issue

Your build.gradle file contains line "apply plugin: 'war' ", while you expect a jar file. More details related to your statement above: "Without jar file, I cannot proceed my work." are needed. What prevents you from proceeding with your work and in which way, exactly? What would you expect,

[google-appengine] Re: Google App Engine end point App V1 to V2 Migration issue

hi, Thank you for your communication. I am follow this document. *https://cloud.google.com/endpoints/docs/frameworks/java/migrating-android * and i am integrate with my project *Step 1: change my project app/

[google-appengine] Re: Google App Engine end point App V1 to V2 Migration issue

Hello Arunprasath, Which jar file is meant here, exactly? What steps have you followed, from those listed in the linked document? In particular, have you rebuild your project? This step is dealt with in the "Rebuild project" sub-chapter

[google-appengine] Re: google app engine slow and timing out

Thanks for your answer, In fact the issue was caused by the connection with mongodb, which however did not crash the app, but kept it working basically just for the /index.html request. It's now solved thanks you On Friday, May 18, 2018 at 8:16:54 PM UTC+1, Jordan (Cloud Platform Support)

[google-appengine] Re: google app engine slow and timing out

502 errors are often caused due to your application code being too busy to respond to nginx (the webserver that sits in front of your app that accepts and routes requests to and from your app). Nginx will return a 502 back to the load balancer which is returned back to the client if it is not

[google-appengine] Re: Google App Engine Standard - OSError: [Errno 28] No space left on device

It may be worthwhile checking some examples of everyday uses, intended for Cloud Shell, as detailed on the Cloud Shell "Examples" document . -- You received this message because you are subscribed to the Google Groups "Google App Engine" group.

[google-appengine] Re: Google App Engine Standard - OSError: [Errno 28] No space left on device

Hello Linh, You don't need CloudShell to use/deploy/run AppEngine. So the space running out on CloudShell has no effect on how/if the Google Appengine Standard application is running. Attila -- You received this message because you are subscribed to the Google Groups "Google App Engine"

[google-appengine] Re: Google App Engine Standard - OSError: [Errno 28] No space left on device

Hi Attilia, Thanks for your information. A quick look seems to indicate that the .NET framework installer had left > some big temporary files there. > Yes, i see it. But GAE standard, i use Python and i only deploy small code (Python Flask). And i only test ab benchmark from local (my laptop):

[google-appengine] Re: Google App Engine Standard - OSError: [Errno 28] No space left on device

Hello Linh, Thank you for the update. Do I understand correctly that the machine which is having problems with the free space is your cloud shell instance? (ie. a small virtual machine which is allocated for you to play around with different tools - https://cloud.google.com/shell/docs/) If

[google-appengine] Re: Google App Engine Standard - OSError: [Errno 28] No space left on device

Hi Attila, I re-send output (file attached) -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this

[google-appengine] Re: Google App Engine Standard - OSError: [Errno 28] No space left on device

Hi Attla, I use GAE Standard, screenshot from dashboard. Could you list the top 20 files for example (by size) from

[google-appengine] Re: Google App Engine Standard - OSError: [Errno 28] No space left on device

Hello, Just to clarify - you're using Google App Engine (GAE) Flexible, right? Because using GAE standard you can't SSH into the instances which are running your code. Could you list the top 20 files for example (by size) from your /tmp directory? Something like: du -a /tmp 2>/dev/null |

[google-appengine] Re: Google App Engine Standard - OSError: [Errno 28] No space left on device

Hi George, Thanks for reply! Does your disc belong to a compute engine instance? > No, i don't use compute engine. If you use the app engine, what is the output of the gcloud info command? > gcloud infoGoogle Cloud SDK [201.0.0]Platform: [Linux, x86_64] ('Linux', >

[google-appengine] Re: google app engine slow and timing out

forget to mention, it's node.js On Thursday, May 17, 2018 at 10:12:42 PM UTC+1, Valerio M wrote: > > Hey, > I deployed an app yesterday. First time on GAE. > Not sure what's going on. The same app works on heroku. > The / loads extremely slowly. the main js file may load in mins sometime. > I

[google-appengine] Re: Google App Engine Standard - OSError: [Errno 28] No space left on device

Does your disc belong to a compute engine instance? Do you make calls to the Datastore API? Do you actually use the G Suite? More information is needed on your disc and your app's architecture. If you use the app engine, what is the output of the gcloud info command? -- You received this

[google-appengine] Re: google app engine timing out without any error on flexible environement

It is worthwhile running the gcloud components update command before attempting deployment. What is the output of gcloud app deploy --verbosity=debug? If you would like us to examine your project in more detail, you may send the following information via private mail; this is done with the

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Still the same issue in april 2018. Deployment of a simple PHP Symfony application in the flex environment takes at least 5 minutes even when specifying the version number and --nopromote. gcloud app deploy --version 20180419t141737 --no-promote 4:56.09 total I've seen in the bugtracker

[google-appengine] Re: Google App Engine Migration from V1 to V2

I can see that you also posted this on StackOverflow which we also monitor, and already getting responses from the community. I encourage everyone experiencing the same issue to continue discussions on

[google-appengine] Re: Google App Engine Flexible get access to a folder dynamically created by a package?

Developers can use Stackdriver Debugger to view their app's source code including the local variables/call stack using debug snapshot. Please note, however, that GAE Flex on Node.js is on Beta

[google-appengine] Re: Google App Engine How to implement Profiling(Stack Tracing)?

I see that you have already created a duplicate threads about this question in Stack Overflow , though for general Google Cloud Platform-end discussions like what you mentioned, it is

[google-appengine] Re: Google App Engine 503 Error

You are seeing these errors because your requests are timing out. You can see from the picture that your requests are taking over 20 seconds to respond. If you click those errors in the Log Viewer you will most likely see the error "Request was aborted after waiting too long to attempt to

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Sames issues on flexible.. Not able to build and deploy anymore ! this a a simple Wordpress web site but Build time out after 10 minutes (deadlineexceedederrors ..) Let's go to a simple CAAS and forget about google bloated GAE -- You received this message because you are subscribed to the

[google-appengine] Re: Google App Engine Deployment Err Debug - Error Response: [4] Timed out waiting for the app infrastructure to become healthy.

Hello George. Thank you for quick reply. Yes, let's keep it in this thread. It is just that I couldn't find anywhere my posted issue that I reported it twice. Best, Alex On Tuesday, 20 February 2018 02:02:09 UTC+7, George (Cloud Platform Support) wrote: > > Hello Alex, > > You have just

[google-appengine] Re: Google App Engine Deployment Err Debug - Error Response: [4] Timed out waiting for the app infrastructure to become healthy.

Hello Alex, You have just opened issue 73583699 in the public issue tracker. That posting is richer in information and otherwise the issue tracker offers the advantage of easier follow-up, so I suggest we keep that posting active; all further developments will get reflected in that thread.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

> > > Just to add my own $0.02 Switched from the standard env to flexible and went from 30 second deploys to 5+ min. Super bad experience especially when this occurs on Google's own samples!! -- You received this message because you are subscribed to the Google Groups "Google App

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Hi Mike, response inline. On Tue, Feb 13, 2018 at 9:24 AM, Mike Hardy wrote: > DeWitt, thanks for informing us but I see a few potential problems. > > 1. we've been passing `--version` in our gcloud app deploy command for the > last 6 months to name the new release.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

As far as I remember this is caused by a slow startup. The app takes too long to start responding to load balancer requests, so the load balancer gives up on it. The app is still running fine, just not accessible from the outside world. You will be able to see the app logs in stack driver and

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

DeWitt, thanks for informing us but I see a few potential problems. 1. we've been passing `--version` in our gcloud app deploy command for the last 6 months to name the new release. Isn't this going to conflict with users like us who want to name the newest version? 2. I tested the solution

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

I can't make a new deployment and I can't event start a previously deployed (and working) version. The server appears to start, but it does not respond to web requests. On Monday, February 12, 2018 at 6:02:54 PM UTC-8, Justin Yip wrote: > > Hello, > > My team is not able to deploy anything to

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Hello, My team is not able to deploy anything to appengine since 4pm (PST). The following message spins forever: Updating service [] (this may take several minutes) Has anyone experienced similar problem? Justni On Monday, February 12, 2018 at 4:07:10 PM UTC-8, DeWitt Clinton wrote: > >

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Hi all, Thanks for being patient, everyone. I waited to reply here until the experiment was fully ramped-up and verified in prod, but all projects should now be eligible to start using the faster in-place version updates. To perform an in-place update, please pass the --version flag to the

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Same boat as Franck and others - this is unusable On Thursday, February 8, 2018 at 12:23:23 PM UTC-8, Franck Diédrich wrote: > > Hello, > > I'm experiencing serious latency too on a flexible env. > > Deployments used to last around 9 minutes (which is quite long) and now > they time out without

[google-appengine] Re: Google App Engine Cost

I would like to add that, here you could find all the Google Cloud Platform solutions to help you build on Cloud Platform. Keeping the balance with the free quotas , you won't be charged anymore. For specific technical

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Hello, I'm experiencing serious latency too on a flexible env. Deployments used to last around 9 minutes (which is quite long) and now they time out without explicit reason. When will deployement improvement flow be available? Le jeudi 29 septembre 2016 21:48:26 UTC+2, Kevin Lau a écrit : > >

[google-appengine] Re: Google App Engine Flexible Environment tmp folder is not writable

Yes Shaharia Azam, It is working fine now. Thanks for your valuable reply. It solved the problem. On Friday, February 2, 2018 at 5:03:57 PM UTC+5:30, Shaharia Azam wrote: > > So it's working good now? -- You received this message because you are subscribed to the Google Groups "Google App

[google-appengine] Re: Google App Engine Flexible Environment tmp folder is not writable

So it's working good now? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email

Re: [google-appengine] Re: Google App Engine Flexible Environment tmp folder is not writable

So it's working now? On Feb 2, 2018 11:49 AM, "Dhandapani Sattanathan" < dhandapani.sattanat...@ssomens.com> wrote: > Thanks, Kenworth & Shaharia Azam for your reply. > > > I tried with sys_get_temp_dir() function in GAE Flexible Environment, > > I changed like index.php and Cache.php in Mpdf.

[google-appengine] Re: Google App Engine Flexible Environment tmp folder is not writable

Thanks, Kenworth & Shaharia Azam for your reply. I tried with sys_get_temp_dir() function in GAE Flexible Environment, I changed like index.php and Cache.php in Mpdf. Now /tmp writable in GAE FE. index.php I did modification in mpdf Cache.php public function __construct($basePath,

[google-appengine] Re: Google App Engine Flexible Environment tmp folder is not writable

Did you try changing the temporary path with "/tmp"? This "/tmp" should be writable or use php sys_get_temp_dir() function in your GAE flexible environment so you will get a temporary directory file location that is writable. On Thursday, February 1, 2018 at 12:09:10 PM UTC+6, Dhandapani

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

I have noticed, deleting old image files (google storage) or deploying services into a clean project made things a bit faster. I don't know if it was a coincidence. They are probably trying to fix this. I ran into random timeout errors too. At one case, it said "server at .appspot.com could

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Same with us. Our deployment hangs at `updating service` and eventually fails. On Thursday, February 1, 2018 at 9:14:52 AM UTC-8, Yuri Bürger wrote: > > I've noticed huge decrease in deployment time today. It was not fast > before, but now it is very slow. Also, it seems randomly fail with

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

I've noticed huge decrease in deployment time today. It was not fast before, but now it is very slow. Also, it seems randomly fail with "time out" четвер, 1 лютого 2018 р. 15:58:40 UTC+2 користувач Dinçer Kavraal написав: > > I don't know about the experimentation but deployments are failing

[google-appengine] Re: Google App Engine Flexible Environment tmp folder is not writable

Directories for temporary files are documented on this mPDF Manual . Note that this library is not a Google product and we therefore can not support it due to our limited visibility. It is recommended to continue

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

I don't know about the experimentation but deployments are failing for the last a few days and taking hours. Has anyone noticed that? Also I am not on the whitelist. On Friday, 26 January 2018 04:17:32 UTC+3, DeWitt Clinton wrote: > > Hi all, > > I've whitelisted everyone who filled out the

[google-appengine] Re: Google App Engine Node.js TLS 1.2

For clarification purposes, what kind/extent of SSL policy control are we talking about? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Hi all, I've whitelisted everyone who filled out the form, and the experiment is going well so far. I hope to see it rolled out to all projects and publicly documented in the next several weeks. Thanks for your help and feedback! -DeWitt On Tue, Jan 23, 2018 at 1:04 PM AntoineA

Re: [google-appengine] Re: Google App Engine Node.js TLS 1.2

Thanks. That make sense. Now my follow up question. Can we control the ssl policy on the load balancer? On Jan 25, 2018 20:40, "'Kenworth (Google Cloud Platform)' via Google App Engine" wrote: > SSL is terminated at the load balancer. Then the load balancer

[google-appengine] Re: Google App Engine Node.js TLS 1.2

SSL is terminated at the load balancer. Then the load balancer creates a new secure connection to NGINX server. You can verify this by SSHing to your VM. AFAIK there is no need to control the SSL policy of the NGINX server. -- You received this message because you are subscribed to the Google

[google-appengine] Re: Google App Engine Node.js TLS 1.2

Thank @Yannick for the response. After more investigation, I found out that in app engine flex the HTTPS requests are terminated on an NGINX server. So the node server receives only HTTP requests. Is there a way to control the ssl policy of the NGINX server? like you can do with compute engine

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

+1 - Also interested On Thursday, 18 January 2018 09:03:39 UTC-5, Ivan Aguirre wrote: > > Hi DeWitt, > > Do you have updates on this? Is there an issue tracker I can follow? > > best regards!! > > Em terça-feira, 19 de dezembro de 2017 07:59:08 UTC-2, Filipe Caldas > escreveu: >> >> Hi DeWitt,

[google-appengine] Re: Google App Engine Node.js TLS 1.2

Hello Alex, I found this Stack Overflow question which explains how you can enforce the use of TLS 1.2 and of specific ciphers using NodeJS. Regarding Google's stance on TLS and ciphers, please read this

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Thanks DeWitt! I just signed up using that form for my app - is this still slated for release this month? Cheers! Tom On Tuesday, December 12, 2017 at 7:37:43 AM UTC-10, DeWitt Clinton wrote: > > Hi all, > > I’m on the App Engine team and I agree, flexible deployments are currently > too

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Hi DeWitt, Do you have updates on this? Is there an issue tracker I can follow? best regards!! Em terça-feira, 19 de dezembro de 2017 07:59:08 UTC-2, Filipe Caldas escreveu: > > Hi DeWitt, > > Will this also impact the deploy time on managed Appengine applications? > > Best, > > On Tuesday,

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Hi DeWitt, Will this also impact the deploy time on managed Appengine applications? Best, On Tuesday, 12 December 2017 17:37:43 UTC, DeWitt Clinton wrote: > > Hi all, > > I’m on the App Engine team and I agree, flexible deployments are currently > too slow. The observations in this thread

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Hi all, I’m on the App Engine team and I agree, flexible deployments are currently too slow. The observations in this thread generally match our own: Deploying a new version of an app takes around six minutes median (50th percentile), with tail spikes several times that (99th percentile).

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

I am seeing the same issue. Did you resolve this? Den torsdag 12 oktober 2017 kl. 09:51:53 UTC+2 skrev Marco Galassi: > > Hi Jordan, thank you for your detailed response. > > Node.js is a single threaded runtime, this means that your code must be > properly >> coded to take full advantage of

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Speaking from experience here. Just move on. Google App Engine (esp. Flexible Engine) is not worthy of your time. Take care, @gunar On Tue, Nov 21, 2017 at 1:24 AM, Vijay M wrote: > I have been struggling with the same issue. I tried deploying a very > simple app and

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

I have been struggling with the same issue. I tried deploying a very simple app and waited for several minutes before the process timed out. I even ran into the same timeout issue with Google's own samples from https://github.com/GoogleCloudPlatform/python-docs-samples/

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

I am experiencing deploy times of 9 minutes, for every deploy, without code changes. All I have done is following a hello world tutorial for a Spring Boot app with Maven. I have searched without finding a solution, unfortunately. I think people get a bad first impression of the App Engine when

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Happenned to me on the AppEngine Standard. Cleaning the staging.PROJECTNAME bucket on GCS fixed it. It appears the folder gets bigger and bigger and it really slows the deploy. On Nov 16, 2017 01:35, wrote: > From limited testing with Java Flexible, it happens with > >

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

>From limited testing with Java Flexible, it happens with server: jetty9 Significantly less issues with standard Java, though we want to user the jetty built in container. What we see is that initial deployment is OK, and every consecutive deployment slows down exponentially, until above

[google-appengine] Re: Google App Engine and Cloud a.i machine learning

Hello Marcello, I understand you want to host your PHP Webapp on App Engine and use the Cloud ML Engine as part of your application. You can do this by using projects.predict method of

[google-appengine] Re: Google App Engine Clou A.I learn machine

Hello Marcello, It is definitely possible to deploy your app in the app engine and use the offered machine learning facilities. You can find more detail on the "Cloud AI" documentation page . Information related to virtual machines that

[google-appengine] Re: Google App engine deploy python project 502 bad gateway error

Google Groups is meant for general product discussions and not for technical support. The correct place to seek technical support is indeed Stack Overflow as you have already done

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Experiencing the same issue with google-appengine :(. I was trying to migrate from AWS; however, after banging my head for the past few hours. I'll probably quit if it can't complete by tomorrow. On Thursday, August 24, 2017 at 3:19:11 PM UTC-4, Samuel Cousin wrote: > > Thanks for the debug

[google-appengine] Re: Google app engine unable to use python 3

The app.yaml holds the configuration settings for your application. Setting it to 'python_version: 3' tells your app to use version 3 for your application. Your development environment, however, may have a different version of Python running (or none at all). Example: To run Python 3 in

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

Hi Jordan, thank you for your detailed response. Node.js is a single threaded runtime, this means that your code must be properly > coded to take full advantage of Node.js's event loop > in > order to be asynchronous. >

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

So just for completeness and clarity, the error you are seeing on your backend service "upstream prematurely closed connection while reading response header from upstream" strictly means that the nginx proxy on that specific instance of your backend service fails to contact the webserver (aka

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

Hello Jordan, we are back because we have found the problem again. We have deleted the custom health check handler, disabled the health check in the *app.yaml* configuration file, but the problem is still there. Just to recap, what we keep seeing is the following. - From the proxy

[google-appengine] Re: Google App Engine - Region

The previous answer is a workaround available for GAE and it is not without issues. This route is usually taken by developers who wants to mimic the load balancing capability of Compute Engine into App Engine apps. The real solution is for your application to use Google Compute Engine

[google-appengine] Re: Google App Engine - Region

@Hossein Yes correct. Since you can only have one App Engine project per Google Cloud project, the current workaround is to indeed copy your App Engine application to multiple Google Cloud projects in different regions. Then using Cloud Load Balancer with multiple Compute Engine instances in a

[google-appengine] Re: Google App Engine - Region

@Jordan, For Cloud Load Balancer , this would mean deploying multiple instances of project in different regions?? On Friday, September 29, 2017 at 6:43:58 PM UTC-4, Jordan (Cloud Platform Support) wrote: > > There are currently no updates on the

[google-appengine] Re: Google App Engine - Region

We need this too for GAE Standard Environment... basically a GAE Std in EU going to backend databases hosted on VMs in EU, and GAE Std in US going to backend databases hosted on VMs in US. We need both in the same project to share services accounts, datastore tables, storeage buckets, etc. On

[google-appengine] Re: Google App Engine multiple regions

We need this too for GAE Standard Environment... basically an GAE in EU going to backend databases hosted on VMs in EU, and GAE in US going to backend databases hosted on VMs in US. On Monday, June 20, 2016 at 5:13:12 AM UTC-4, Yon Dev wrote: > > I am evaluating whether GAE would be a good fit

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

If properly responding to the health check with a message body *res.status(200).send('');* as the documentation states causes the health checks to fail, that would indeed warrant an issue to be reported in the PIT (public issue tracker). Note that responding to health checks is not required

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

Hi Jordan, we would like to share with you what we have found. We have delete our custom health check that was an handler responding with 200 OK as follows: app.get('/_ah/health', function (req, res) { res.sendStatus(200); }); It looks like this has solved the problem as we *do not* see any

[google-appengine] Re: Google App Engine - Region

There are currently no updates on the release date. Until there is a production solution released, creating your own proxy to load balance between regions is the only workaround. One workaround would be to setup a Cloud Load Balancer that accepted

[google-appengine] Re: Google App Engine - Region

@Jordan, The last response was on August 28, a month ago. Any updates on this? This is really urgent. THANKS On Friday, September 29, 2017 at 5:32:26 PM UTC-4, Jordan (Cloud Platform Support) wrote: > > Our engineering team is working on a solution to cross-region load balance > for App

[google-appengine] Re: Google App Engine - Region

Our engineering team is working on a solution to cross-region load balance for App Engine Flexible and Standard. There is no ETA for the release but you can follow the Public Feature Request for updates. -- You received this message because you are

[google-appengine] Re: Google App Engine - Region

@Kenworth, So we have to deploy/manage another instance of project for Europe region?? Where does the loadbalancing come in play? Is it possible to somehow setup loadbalance which directs traffic to proper region? Thanks On Sunday, September 24, 2017 at 5:50:12 PM UTC-4, Kenworth (Google Cloud

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

If you have tested turning the nginx health checks off and you still see these 502 errors, then I highly suggest you report this in the Public Issue Tracker

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

So, we took a step back in our project and deployed an Hello World application to see if the problem would still happen. We used the hello-world example in the Google App Engine code examples and edited it (our file is attached): there are no differences, but the fact that we don't have a

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

You are very correct, as described in the previously linked Stack Exchange answer, nginx health checks are indeed the same health checks that are configurable via your

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

Attaching a graphic description or current backend. On Monday, September 25, 2017 at 10:00:13 AM UTC+2, Marco Galassi wrote: > > We are performing a migration to a new backend hosted on Google App Engine > and based on Node.js. > > Before performing the switch from the old to the new backend,

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

You are very correct in your design pattern for testing a new backend. Duplicating live production requests and testing them against your new backend is actually the preferred way of testing before performing a migration. Having an App Engine proxy act like the actual client is also correct

[google-appengine] Re: Google App Engine - Region

On Sunday, September 24, 2017 at 11:04:16 AM UTC-4, Hossein Amerkashi wrote: > > Hello, > > I am using GAE and have deployed an app. The performance seems to be > pretty good for USA east-coast. I'm getting complaints from UK users that > performance, during certain times, is very slow. How do

[google-appengine] Re: Google App Engine apps blocked by an organization, any suggestions?

You might want to try some of the alternative cnames for ghs.googlehosted.com, such as ghs46.googlehosted.com which resolves to a different IP for me at least. See https://support.google.com/a/answer/112038?hl=en at the bottom. Obviously no guarantees that works everywhere or stays working.

[google-appengine] Re: Google App Engine apps blocked by an organization, any suggestions?

Perhaps set up a minimal proxy server on a VPS (or even a GCE instance with a static IP) and use that to forward requests to GAE? Such a server would require minimal setup and upkeep. Not the ideal solution, but a potential work-around. Attila -- You received this message because you are

[google-appengine] Re: Google App Engine apps blocked by an organization, any suggestions?

GAE used to have a feature called VIP (virtual IP) which was mainly meant for setting up SSL if you wanted to support clients which didn't support SNI, but I guess that was deprecated :( Attila -- You received this message because you are subscribed to the Google Groups "Google App Engine"

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Thanks for the debug info! I'm experiencing the exact same issue but with a nodejs 8.x environment. This inertia to deploy a mere 100 lines of JS is really testing my limit... On Monday, August 21, 2017 at 8:06:19 PM UTC+1, Adrien Di Pasquale wrote: > > Hi ! I'm experiencing the same slowness :

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Hi ! I'm experiencing the same slowness : the "Update service ...|" step is taking anywhere from 5 to 30 minutes. Here is what I've tried so far to fix it, without success: - use a different region (I've switched from europe-west to us-central) - deploy the hello_world app from the sample

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Hi ! I'm experiencing the same slowness : the "Update service ...|" step is taking anywhere from 5 to 30 minutes. Here is what I've tried so far to fix it, without success: - use a different region (I've switched from europe-west to us-central) - deploy the hello_world app from the sample

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Hi ! I'm experiencing the same slowness with GAE. The `Updating service ...|` step takes anywhere from 5 to 30 minutes, every single time. So far, I've tried mitigating the issue without success by : - deploying the hello_world app from the official github sample repo - deploying on a different

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

Hi Nick, thank you for the information. Are there any updates on decreasing GCLB configuration push times? Is there a way for me to bypass it if using "manual_scaling: instances: 1"? Thank you, Gunar. On Wednesday, April 5, 2017 at 8:28:11 PM UTC-3, Nick (Cloud Platform Support) wrote: > > Hey

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

I experience the same slowness. It makes sense that it the problematic part is GCloud's Load Balancer, as pushing code and building the container seems relatively fast. Are there any updates on this on Google's part? On Thursday, May 4, 2017 at 8:07:31 PM UTC-3, E EE wrote: > > From my

[google-appengine] Re: Google App Engine with Local mysql server showing error.

Based on your logs, it seems that you are trying to connect to Cloud SQL instance [izen-tech:asia-east1:myinstance] while trying to run locally. Were you able to start and run your local MySQL server as documented here [1]? Are you using local credentials? [1]

[google-appengine] Re: Google App Engine standard now supports Java 8

Again, I think you are mixing GAE standard and flexible here. Article [2] you posted is for GAE Flexible, not standard. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send

<    1   2   3   4   5   6   7   8   9   >