[google-appengine] Re: How can I make Google cloud support h3-29?

[pingping chen]

I have used the google cloud  platform HTTP(S) Load Balancers  and enable 
quic. Is there anything wrong? 

Or the google cloud platform is not supported for h3-29 (IETF） by now ?


[image: 微信图片_20210312104522.png]
在2021年3月12日星期五 UTC+8 上午4:09:55 写道：

>
> Hi, 
>
> Currently those are the only supported versions of QUIC in GCP HTTP(S) 
> Load Balancers, and any other version of QUIC should make the connection 
> fall back to HTTPS or HTTP/2 instead of negotiating QUIC.
> On Thursday, March 11, 2021 at 11:32:22 AM UTC-5 apple...@gmail.com wrote:
>
>> I deploy my project with app engine , then configure my own load balancer 
>> and enable quic .
>> But when I send  request, it only support h3-Q050,h3-Q046,h3-Q043, not 
>> support h3-29=":443" (ietf).
>>
>> How can I make it support h3-29? 
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/32f08e14-cbf2-4897-9adc-64ad40680d77n%40googlegroups.com.

[google-appengine] Thank you for taking the time to submit your verification information. We were unable to verify billing instrument ownership using the documents you submitted. Please submit a ph

[BRONZE esports]

I dont know what happen but i sign up for google cloud verify by show last 
4 number and google said it not verify

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0d586364-e3b4-4285-9e5d-6923a7f0e299n%40googlegroups.com.

[google-appengine] Re: Custom Domain Name

['Elliott (Cloud Platform Support)' via Google App Engine]

Hello Harsha,

I understand that you are receiving a security alert when accessing your 
App Engine application that has your custom domain 
[

To narrow down the focus and to find a common issue, when did this behavior 
begin? Did it work before? 

I was able to find some documentation here 
 that I’d like to offer. 
It describes how to make a site secure with SSL. You did not mention if you 
made your site secure with SSL. If you did, there may be a small chance 
that the document changed after you went through it. To be certain, I ask 
you to review it.

Are you the administrator of the account you’re using?

Are you the owner of the account?

Have you added the domain to  the account?

Assuming that all the steps were followed and to make sure your application 
is working otherwise, are you able to visit the non-secure web address of 
your application? 

I hope this helps.


On Wednesday, March 10, 2021 at 4:11:32 PM UTC-5 harshava...@gmail.com 
wrote:

> Hi,
>
> I have mapped my custom domain name to app engine, but when visit the 
> domain name, it says "connection is not secure", i have bought the domain 
> name from Google only.
>
>   Please help me resolve this.
>
> Thanks,
> Harsha
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8045c69d-56d7-4561-9ef2-b2a03b783aaan%40googlegroups.com.

[google-appengine] Re: How can I make Google cloud support h3-29?

['Nicholas Elkaim' via Google App Engine]

Hi, 

Currently those are the only supported versions of QUIC in GCP HTTP(S) Load 
Balancers, and any other version of QUIC should make the connection fall 
back to HTTPS or HTTP/2 instead of negotiating QUIC.
On Thursday, March 11, 2021 at 11:32:22 AM UTC-5 apple...@gmail.com wrote:

> I deploy my project with app engine , then configure my own load balancer 
> and enable quic .
> But when I send  request, it only support h3-Q050,h3-Q046,h3-Q043, not 
> support h3-29=":443" (ietf).
>
> How can I make it support h3-29? 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e119ad8c-b3ce-4a3a-8080-908610e5f558n%40googlegroups.com.

[google-appengine] Re: Google App Engine: Request was aborted after waiting too long

['wokmou' via Google App Engine]

You might be experiencing latency from reloading instances. This can result 
in loading requests and additional latency as explain here[1].

You can also visit this link to know more about instance life cycle[2].

[1]https://cloud.google.com/appengine/docs/standard/java/how-instances-are-managed
[2]https://cloud.google.com/compute/docs/instances/instance-life-cycle

On Thursday, March 11, 2021 at 11:32:25 AM UTC-5 nem...@cacotec.com wrote:

> I have a small NodeJS application backend running in a standard GAE 
> environment which has no real world load - it only serves my personal 
> requests when I am testing stuff.
>
> So I was clicking through the app last night and this error message popped 
> up:
> ```
> Request was aborted after waiting too long to attempt to service your 
> request.
> ```
>
> These are my logs:
> ```
> 2021-03-11 06:30:06.228 CET GET /l/data 200
> Api call succeeded. Returning data.
>
> 2021-03-11 06:30:52.859 CET
> [start] 2021/03/11 05:30:52.858446 Quitting on terminated signal
>
> 2021-03-11 06:31:25.997 CET OPTIONS /l/orders 500
> Request was aborted after waiting too long to attempt to service your 
> request.
>
> 2021-03-11 06:31:41.132 CET OPTIONS /l/orders 500
> Request was aborted after waiting too long to attempt to service your 
> request.
>
> 2021-03-11 06:31:46.629 CET OPTIONS /l/orders 500
> Request was aborted after waiting too long to attempt to service your 
> request.
>
> 2021-03-11 06:34:44.566 CET GET /l/users 200
> 2021-03-11 06:34:44.736 CET
> [start] 2021/03/11 05:34:44.735240 No entrypoint specified, using default 
> entrypoint: /serve
> [start] 2021/03/11 05:34:44.736120 Starting app
> ```
>
> From the logs I see that my previous instance was stopped prior to the 
> requests that triggered the error and that for the new OPTIONS requests GAE 
> did not even attempt to start an instance. Next start was triggered almost 
> 3 minutes later.
>
> I am still not sure what happened here and would like to understand it 
> because I have some production services running on GAE and this makes me a 
> bit worried.
>
> Thanks in advance!
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ce624825-700f-4bca-88fe-dd7e43b4ede1n%40googlegroups.com.

[google-appengine] Re: Google app engine not distributing requests properly

['wokmou' via Google App Engine]

>From what I understand , your instance is overloaded during spikes. My 
suggestion is to set target_concurrent_requests [1] parameter to limit the 
number of concurrent requests per instance. This will trigger the creation 
of a new instance as soon as the limit is reached.

There is also the max_concurrent_requests [2] use to specify when a new 
instance is started due to concurrent requests.

[1]
https://cloud.google.com/appengine/docs/flexible/python/reference/app-yaml?hl=en#automatic_scaling

[2]https://cloud.google.com/appengine/docs/standard/nodejs/config/appref#scaling_elements


On Friday, February 19, 2021 at 2:06:13 PM UTC-5 
she...@digitalmediasolutions.com.au wrote:

> Hello!
> We have a dockized PHP Nginx application running on google app engine 
> flex. 
> We have automatic scaling and minimum 1 instance is always running. 
> As soon as traffic spikes, users receive 50x gateway errors for some time. 
> The autoscaler works as intended but after checking the logs,  all errors 
> originate from the idle instance due to app engine sending most of the 
> requests received to the first instance overloading it.
>
> Why is app engine not distributing requests evenly? What can we do to make 
> sure the service is available during high traffic bursts?
>
> Thank you for your time!
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8414c627-7ffb-4d50-81fb-a910bbe2eb7en%40googlegroups.com.

[google-appengine] How can I make Google cloud support h3-29?

[pingping chen]

I deploy my project with app engine , then configure my own load balancer 
and enable quic .
But when I send  request, it only support h3-Q050,h3-Q046,h3-Q043, not 
support h3-29=":443" (ietf).

How can I make it support h3-29? 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/082f20f3-5418-4122-bba1-3cb158cbaa4cn%40googlegroups.com.

[google-appengine] Re: Cron jobs not getting executed

[Andrés Kammerath]

Hi guys, we are experimenting this issue with a cronjob that runs every 
30'. It has been running normally up to 2 days ago. Does anybody have the 
same problem? greetings, Andres.
p.d: I apologize for my english.
El jueves, 11 de noviembre de 2010 a la(s) 15:53:33 UTC-3, dzwiedziu 
escribió:

> My one minutes jobs also doens't work.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c757edc3-c08c-4185-9230-1a3423e73b3an%40googlegroups.com.

[google-appengine] Google App Engine: Request was aborted after waiting too long

[Nemanja Patrnogic]

I have a small NodeJS application backend running in a standard GAE 
environment which has no real world load - it only serves my personal 
requests when I am testing stuff.

So I was clicking through the app last night and this error message popped 
up:
```
Request was aborted after waiting too long to attempt to service your 
request.
```

These are my logs:
```
2021-03-11 06:30:06.228 CET GET /l/data 200
Api call succeeded. Returning data.

2021-03-11 06:30:52.859 CET
[start] 2021/03/11 05:30:52.858446 Quitting on terminated signal

2021-03-11 06:31:25.997 CET OPTIONS /l/orders 500
Request was aborted after waiting too long to attempt to service your 
request.

2021-03-11 06:31:41.132 CET OPTIONS /l/orders 500
Request was aborted after waiting too long to attempt to service your 
request.

2021-03-11 06:31:46.629 CET OPTIONS /l/orders 500
Request was aborted after waiting too long to attempt to service your 
request.

2021-03-11 06:34:44.566 CET GET /l/users 200
2021-03-11 06:34:44.736 CET
[start] 2021/03/11 05:34:44.735240 No entrypoint specified, using default 
entrypoint: /serve
[start] 2021/03/11 05:34:44.736120 Starting app
```

>From the logs I see that my previous instance was stopped prior to the 
requests that triggered the error and that for the new OPTIONS requests GAE 
did not even attempt to start an instance. Next start was triggered almost 
3 minutes later.

I am still not sure what happened here and would like to understand it 
because I have some production services running on GAE and this makes me a 
bit worried.

Thanks in advance!

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ef87f6ad-2c0e-4dc5-8bd7-a689c464afb2n%40googlegroups.com.

[google-appengine] Deployment fails with error

['nibrass' via Google App Engine]

Hello,

I understand that you are getting the following error [1] when deploying to 
App Engine. 

Could you please update your Cloud SDK using the next command [2] , restart 
your Cloud Shell and try again?

- gcloud components update

Best Regards,

Nibrass



[1]: ERROR: gcloud crashed (ValueError): invalid literal for int() with 
base 10

[2]: https://cloud.google.com/sdk/gcloud/reference/components/update
On Thursday, March 11, 2021 at 4:19:03 AM UTC+1 duynhan bui wrote:

>
> @jstsetinin, sorry for late response.
> i have checked gcloud sdk version i am using
> + gcloud version
> Google Cloud SDK 324.0.0
> alpha 2021.01.19
> app-engine-go 1.9.71
> app-engine-java 1.9.84
> app-engine-python 1.9.91
> app-engine-python-extras 1.9.91
>
> i also added verbosity=debug [2] flag. This is what I got
> + gcloud app deploy build/gcloud_staging.yaml --project=project-id --quiet 
> --version=2021121112 --verbosity=debug
> DEBUG: Running [gcloud.app.deploy] with arguments: [--project: 
> "project-id", --quiet: "True", --verbosity: "debug", --version: 
> "2021121112", DEPLOYABLES:1: "['build/gcloud_staging.yaml']"]
> DEBUG: Loading runtimes experiment config from 
> [gs://runtime-builders/experiments.yaml]
> INFO: Reading 
> [ 0x7f39b0084c50>]
> DEBUG: Response content was invalid (invalid literal for int() with base 
> 10: 'c010:101:5476:1c02:2::51]:3128'), retrying
> DEBUG: Retrying request to url 
> https://storage.googleapis.com/storage/v1/b/runtime-builders/o/experiments.yaml?alt=media
>  
> after exception invalid literal for int() with base 10: 
> 'c010:101:5476:1c02:2::51]:3128'
> DEBUG: Response content was invalid (invalid literal for int() with base 
> 10: 'c010:101:5476:1c02:2::51]:3128'), retrying
> DEBUG: Retrying request to url 
> https://storage.googleapis.com/storage/v1/b/runtime-builders/o/experiments.yaml?alt=media
>  
> after exception invalid literal for int() with base 10: 
> 'c010:101:5476:1c02:2::51]:3128'
> DEBUG: Response content was invalid (invalid literal for int() with base 
> 10: 'c010:101:5476:1c02:2::51]:3128'), retrying
> DEBUG: Retrying request to url 
> https://storage.googleapis.com/storage/v1/b/runtime-builders/o/experiments.yaml?alt=media
>  
> after exception invalid literal for int() with base 10: 
> 'c010:101:5476:1c02:2::51]:3128'
> DEBUG: Response content was invalid (invalid literal for int() with base 
> 10: 'c010:101:5476:1c02:2::51]:3128'), retrying
> DEBUG: Retrying request to url 
> https://storage.googleapis.com/storage/v1/b/runtime-builders/o/experiments.yaml?alt=media
>  
> after exception invalid literal for int() with base 10: 
> 'c010:101:5476:1c02:2::51]:3128'
> DEBUG: Response content was invalid (invalid literal for int() with base 
> 10: 'c010:101:5476:1c02:2::51]:3128'), retrying
> DEBUG: Retrying request to url 
> https://storage.googleapis.com/storage/v1/b/runtime-builders/o/experiments.yaml?alt=media
>  
> after exception invalid literal for int() with base 10: 
> 'c010:101:5476:1c02:2::51]:3128'
> DEBUG: Response content was invalid (invalid literal for int() with base 
> 10: 'c010:101:5476:1c02:2::51]:3128'), retrying
> DEBUG: Retrying request to url 
> https://storage.googleapis.com/storage/v1/b/runtime-builders/o/experiments.yaml?alt=media
>  
> after exception invalid literal for int() with base 10: 
> 'c010:101:5476:1c02:2::51]:3128'
> DEBUG: invalid literal for int() with base 10: 
> 'c010:101:5476:1c02:2::51]:3128'
> Traceback (most recent call last):
>   File "/usr/lib/google-cloud-sdk/lib/googlecloudsdk/calliope/cli.py", 
> line 982, in Execute
> resources = calliope_command.Run(cli=self, args=args)
>   File "/usr/lib/google-cloud-sdk/lib/googlecloudsdk/calliope/backend.py", 
> line 809, in Run
> resources = command_instance.Run(args)
>   File "/usr/lib/google-cloud-sdk/lib/surface/app/deploy.py", line 111, in 
> Run
> self._ServerSideExperimentEnabled()):
>   File "/usr/lib/google-cloud-sdk/lib/surface/app/deploy.py", line 137, in 
> _ServerSideExperimentEnabled
> runtimes_builder_root)
>   File 
> "/usr/lib/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/runtime_builders.py",
>  
> line 518, in LoadFromURI
> with _Read(uri) as f:
>   File "/usr/lib/python3.7/contextlib.py", line 112, in __enter__
> return next(self.gen)
>   File 
> "/usr/lib/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/runtime_builders.py",
>  
> line 269, in _Read
> with contextlib.closing(storage_client.ReadObject(object_)) as f:
>   File 
> "/usr/lib/google-cloud-sdk/lib/googlecloudsdk/api_lib/storage/storage_api.py",
>  
> line 311, in ReadObject
> self.client.objects.Get(get_req, download=download)
>   File 
> "/usr/lib/google-cloud-sdk/lib/googlecloudsdk/third_party/apis/storage/v1/storage_v1_client.py",
>  
> line 1081, in Get
> download=download)
>   File 
> "/usr/bin/../lib/google-cloud-sdk/lib/third_party/apitools/base/py/base_api.py",
>  
> line 709, in _RunMethod
>