Re: [google-appengine] Re: subdomain is not working through cloudflare for google appengine

[Rajesh Gupta]

Hello Aref,

Yes, I have done the settings as per that link.

I am able to successfully setup for another domain registered at 'eapps',
but it is not going through cloudflare. That domain and subdomain is fine
and routing properly

However, I am not able to route a subdomain through cloudflare

Is attaching screenshots from appengine console and cloudflare console help
you in further supporting me.


On Wed, Mar 11, 2020 at 6:02 PM 'Aref Amiri (Cloud Platform Support)' via
Google App Engine  wrote:

> Can you confirm that you've followed the steps provided here
> 
> to Map your custom domain and subdomain?
>
> --
> 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/abf6715b-7946-42c7-a20f-ec3413da6183%40googlegroups.com
> 
> .
>


-- 
Rajesh
www.servicefolder.com
*Field Service Software on Google Cloud Platform and Mobile*

-- 
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/CA%2BS7ijZWnf2%3D8DOVK%3D1c_fC%3DCMXmD8%3DR2kbahPGbWc9nc_jcNg%40mail.gmail.com.

[google-appengine] Re: connect from a node server in app engine to mysql in another project

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

Hello Emanuel, 

Even though it requires project ids and Cloud SQL instance name to 
investigate the issue further, on a best effort basis I have done some 
research.

If I have understood it correctly you have MySQL database at projectA and 
App Engine application at projectB.

In that case I believe you have not done the permission part correctly as 
described by third party in this StackOverflow thread 
. As described at the StackOverflow 
thread , you need to go to the Cloud 
SQL Console and Click Edit. After that you need to select “Connections” 
from the left menu and need to add the Project where App Engine application 
is located following the instructions outlined at Console. In this case the 
Project is projectB. 

So after going to projectB, you need to select the App Engine default 
service account which will be “proje...@appspot.gserviceaccount.com”. After 
that you need to add the “proje...@appspot.gserviceaccount.com” at projectA 
with the role “Cloud SQL Client” as described at the StackOverflow thread 
. 

In addition to that in this StackOverflow thread, 
it
 
is suggested by a third party to enable both Cloud SQL API and the Cloud 
SQL Admin API in both projects. 

If still the issue is not resolved or If you have any technical queries or 
think your issue is related to code, you can post at the Stack Overflow 
 or Server Fault  and 
a community of developers will assist you.

In case there are any technical issues or you would like to request any 
feature you can report it at the Public Issues by selecting the right 
component here 
. 

Please also note that Google Groups forum is meant for general discussion 
of the platform, not specific technical issues. You can find more info 
about Community Support Overview on Google Groups here 
.


On Wednesday, March 11, 2020 at 11:24:16 AM UTC-4, Emanuel Allen wrote:
>
>
> environment setup logic: two projects one name projectA and another name 
> projectB. projectA contain the mysql database and projectB contain the app 
> engine node server.  
>
> what i have tried is setting the right permission within projectB in I Am 
> with projectA being the sql client 
> projectA @ appspot.gserviceaccount.com App Engine default service 
> accountCloud SQL Client
>
> i also add this to my *app.yaml* file:
>
>   *DB_CONNECTION*: mysql
>   *DB_HOST*: localhost
>   *DB_DATABASE*: xx
>   *DB_USERNAME*: xxx
>   *DB_PASSWORD*: 
>   *DB_SOCKET*: /cloudsql/::
>
> *beta_settings:*
>   # for Cloud SQL, set this value to the Cloud SQL connection name,
>   *cloud_sql_instances*: ::
>
> here how i tried connecting in my database javascript file:
>
>   con = mysql.createConnection({
> socketPath: "",
> host: "",
> user: "",
> password: ""
>   });
>
> with trying to switch between socketPath and host. the socketpath being: 
>
> socketPath: `/cloudsql/${process.env.CLOUD_SQL_CONNECTION_NAME}`
>
> format.
>
> I tried and struggle with this but refuse to fail, can anyone give me a 
> solution to this?
>
>

-- 
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/33a6f2a0-b7df-4149-9835-b343b0fb30eb%40googlegroups.com.

[google-appengine] Re: Connecting from app engine instance to compute engine instance directly

['yananc' via Google App Engine]

Hello Vishnu,

The documentation ‘app.yaml Configuration File - Network settings’ 

 
provides information on how to configure network settings in the app.yaml 
file for App Engine Flexible. You may also navigate to similar pages for 
other supported language you desire for your specific use case.

And also please make sure that firewall rules for the VPC network are 
properly configured so the communication between App Engine and Compute 
Engine is not blocked. The link 
 offers details about firewall 
settings for VPC network.

Hope the information above is helpful to answer your question.


On Wednesday, March 11, 2020 at 11:24:16 AM UTC-4, Vishnu Mohan wrote:
>
> Hey Hussein,
>
> How did you manage network configurations in app.yaml file for App Engine. 
> I have an App Engine Flex and an Elasticsearch on Compute Engine under same 
> VPC. But i am not able to connect my app engine to the internal ip of 
> compute engine to access elasticsearch.
>
> Thanks.!
>
> On Friday, May 8, 2015 at 3:03:09 AM UTC+5:30, Hussein Vastani wrote:
>>
>> Hi,
>> At my current gig we've been grappling with the same problem, and there 
>> seems to be a solution in the 1.9.19 SDK release (finally!). 
>>
>> So my context is: my java frontend instances need to hit my elasticsearch 
>> cluster hosted on GCE. The only way to reach the cluster was via a reverse 
>> proxy exposed through a GCE public IP address. I was using basic auth to 
>> authenticate my App Engine frontend instances. As you would expect the 
>> latency has been hurting. Search queries that should take 10ms, instead 
>> come back in 150ms (10x slow). After additional processing in my frontend 
>> request, that adds up pretty quickly to noticeable latency user-side. 
>>
>> I posted about the problem some time ago in this group here 
>>  
>> and 
>> the issue tracker here 
>> . I 
>> got an acknowledgement from Google and the fix appeared in the 1.9.19 
>> release, a bit quietly (the issue is still open).
>>
>> So the solution for me is to run a managed VM on the same network as my 
>> elasticsearch cluster, and that way I should be able to access my cluster 
>> "directly" using internal network addresses, without going out of the 
>> Google network. The 1.9.19 SDK allows you to specify a network in the 
>> configuration for your managed vm, that defaults to the default GCE network 
>> of your project. Thus I either directly route my search requests to my 
>> managed VM or have my front end instances talk to my managed VM over http. 
>>
>> (For my particular case, I expect additional latency savings because I 
>> can run a full elasticsearch client on the managed VM that knows the 
>> cluster state, instead of using the naked elasticsearch REST API, as I do 
>> now, from my front end instances. That saves me an additional network hop 
>> that is needed to figure out which nodes in my cluster to hit.)
>>
>> I guess, the same should work for you no?
>>
>> I'll post next week about the results of migrating to a managed VM setup.
>>
>> Good luck!
>> H
>>
>>
>> On Thursday, May 7, 2015 at 1:52:39 PM UTC-4, Ian Childress wrote:
>>>
>>> We (our Go dev team) want to connect our app engine apps to our compute 
>>> engine apps directly using internal IP address. From my understanding 
>>> through documentation and exhaustive searching, the solution is to use a 
>>> public IP address. This solution requires whitelisting an entire ip block 
>>> (Google's ip block for app engine). This both increases security risk as 
>>> well as charges additional bandwidth. The other solution is to use a 
>>> messaging service PubSub. This is fine for submitting tasks to be performed 
>>> by the back end app, but it prevents the app engine from receiving the 
>>> response from the compute engine. 
>>>
>>> Have I missed the solution somewhere that allows for internal 
>>> communication between app engine and compute engine? Using a job queue or 
>>> public IP is not a replacement for an internal socket connection.
>>>
>>

-- 
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/fb98a5ad-bbce-4cc1-a7e4-c13324bc0c75%40googlegroups.com.

[google-appengine] connect from a node server in app engine to mysql in another project

[Emanuel Allen]

environment setup logic: two projects one name projectA and another name 
projectB. projectA contain the mysql database and projectB contain the app 
engine node server.  

what i have tried is setting the right permission within projectB in I Am 
with projectA being the sql client 
projectA @ appspot.gserviceaccount.com App Engine default service 
accountCloud SQL Client

i also add this to my *app.yaml* file:

  *DB_CONNECTION*: mysql
  *DB_HOST*: localhost
  *DB_DATABASE*: xx
  *DB_USERNAME*: xxx
  *DB_PASSWORD*: 
  *DB_SOCKET*: /cloudsql/::

*beta_settings:*
  # for Cloud SQL, set this value to the Cloud SQL connection name,
  *cloud_sql_instances*: ::

here how i tried connecting in my database javascript file:

  con = mysql.createConnection({
socketPath: "",
host: "",
user: "",
password: ""
  });

with trying to switch between socketPath and host. the socketpath being: 

socketPath: `/cloudsql/${process.env.CLOUD_SQL_CONNECTION_NAME}`

format.

I tried and struggle with this but refuse to fail, can anyone give me a 
solution to this?

-- 
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/a0c42ca4-cf03-4c63-a7ce-68e02e7bca87%40googlegroups.com.

[google-appengine] Re: Connecting from app engine instance to compute engine instance directly

[Vishnu Mohan]

Hey Hussein,

How did you manage network configurations in app.yaml file for App Engine. 
I have an App Engine Flex and an Elasticsearch on Compute Engine under same 
VPC. But i am not able to connect my app engine to the internal ip of 
compute engine to access elasticsearch.

Thanks.!

On Friday, May 8, 2015 at 3:03:09 AM UTC+5:30, Hussein Vastani wrote:
>
> Hi,
> At my current gig we've been grappling with the same problem, and there 
> seems to be a solution in the 1.9.19 SDK release (finally!). 
>
> So my context is: my java frontend instances need to hit my elasticsearch 
> cluster hosted on GCE. The only way to reach the cluster was via a reverse 
> proxy exposed through a GCE public IP address. I was using basic auth to 
> authenticate my App Engine frontend instances. As you would expect the 
> latency has been hurting. Search queries that should take 10ms, instead 
> come back in 150ms (10x slow). After additional processing in my frontend 
> request, that adds up pretty quickly to noticeable latency user-side. 
>
> I posted about the problem some time ago in this group here 
>  
> and 
> the issue tracker here 
> . I got 
> an acknowledgement from Google and the fix appeared in the 1.9.19 release, 
> a bit quietly (the issue is still open).
>
> So the solution for me is to run a managed VM on the same network as my 
> elasticsearch cluster, and that way I should be able to access my cluster 
> "directly" using internal network addresses, without going out of the 
> Google network. The 1.9.19 SDK allows you to specify a network in the 
> configuration for your managed vm, that defaults to the default GCE network 
> of your project. Thus I either directly route my search requests to my 
> managed VM or have my front end instances talk to my managed VM over http. 
>
> (For my particular case, I expect additional latency savings because I can 
> run a full elasticsearch client on the managed VM that knows the cluster 
> state, instead of using the naked elasticsearch REST API, as I do now, from 
> my front end instances. That saves me an additional network hop that is 
> needed to figure out which nodes in my cluster to hit.)
>
> I guess, the same should work for you no?
>
> I'll post next week about the results of migrating to a managed VM setup.
>
> Good luck!
> H
>
>
> On Thursday, May 7, 2015 at 1:52:39 PM UTC-4, Ian Childress wrote:
>>
>> We (our Go dev team) want to connect our app engine apps to our compute 
>> engine apps directly using internal IP address. From my understanding 
>> through documentation and exhaustive searching, the solution is to use a 
>> public IP address. This solution requires whitelisting an entire ip block 
>> (Google's ip block for app engine). This both increases security risk as 
>> well as charges additional bandwidth. The other solution is to use a 
>> messaging service PubSub. This is fine for submitting tasks to be performed 
>> by the back end app, but it prevents the app engine from receiving the 
>> response from the compute engine. 
>>
>> Have I missed the solution somewhere that allows for internal 
>> communication between app engine and compute engine? Using a job queue or 
>> public IP is not a replacement for an internal socket connection.
>>
>

-- 
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/efaaad11-3098-44b8-9f3b-1f1e8d29fc22%40googlegroups.com.

[google-appengine] Re: subdomain is not working through cloudflare for google appengine

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

Can you confirm that you've followed the steps provided here 

 
to Map your custom domain and subdomain?

-- 
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/abf6715b-7946-42c7-a20f-ec3413da6183%40googlegroups.com.

Re: [google-appengine] Re: gcloud app deploy error: Service not available?

[Scott White]

Thanks for the reply. It started working again. The annoying issue (besides
the outage for most of the day), was that the status page showed no issues,
so we had no idea if the issue was being fixed or it was just related to us.

https://issuetracker.google.com/issues/151085629

Scott

On Tue, Mar 10, 2020 at 10:02 AM 'David (Cloud Platform Support)' via
Google App Engine  wrote:

> Hello,
>
> By the error you are receiving, it looks like it was a transient issue at
> the moment you attempted this deployment. Could you try again and see if
> it’s still happening?
>
> --
> 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/57a21fc9-7997-4150-a8ec-ab78d533954e%40googlegroups.com
> 
> .
>


-- 
Scott White | VP of Engineering
HUVR
+1.512.745.1455

Visit us at:  www.huvrdata.com

-- 
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/CAP6MNxdN1dXwkYzVGJzvqc%2BOsCFrQXC3GwuXBdScr415ubCpmA%40mail.gmail.com.