bump - any idea here?
On Monday, June 24, 2019 at 5:08:34 PM UTC-4, Robert Dyas wrote:
>
> We are using a custom domain... PCI security check flagged this issue. We
> need to disable TLS1.0, DES, 3DES, SSLv3, SSLv3.
> How do we do this?
>
--
You received this message because you
We are using a custom domain... PCI security check flagged this issue. We
need to disable TLS1.0, DES, 3DES, SSLv3, SSLv3.
How do we do this?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop
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
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
Is there any chance I will be able to have GAE std deployed to multiple
regions within the same project? We want a GAE std in US accessing
databases in the US, with a European GAE std accessing databases in the EU.
We want them on the same project so all of the security keys, and
especially
The Good Cloud Status dashboard says all problems are resolved, but we are
in us central 1c and still having issues with App Engine accessing some of
our Google Cloud SQL gen 1 instances. We can access the directly, but not
via app engine. Also, some are accessible and some are not.
--
You
With GAE std and java8, when the 60 second time limit is exceeded and your
process is killed (or whatever) it does not appears that this timeout is
shown in the logs? Am I missing something or is this a bug?
--
You received this message because you are subscribed to the Google Groups
"Google
Also using the native java8 https request, it throws an exception if you
call conn.getInputStream() and the response code is 400 series. That code
worked fine in java7 and java8 with urlfetch, but in java8 native you have
to call conn.getErrorStream() after testing the response code to know
to check in which ways
> they differ? There might be some platform-specific differences that the
> card processor is not accounting for or handling poorly for some reason.
>
> On Thursday, July 13, 2017 at 3:07:20 PM UTC-4, Robert Dyas wrote:
>>
>> On further research
*Glitches*: Main glitch so far is that we needed to set
urlfetch
in our appengine-web.xml file for some reason. Still trying to figure out
why we can make the request on java7 and 8 via urlfetch, but it doesn't
work on native on java8. We could be doing something stupid but can't
figure
compatibility settings).
Now the remaining question is: why when using native does it not work?
On Thursday, July 13, 2017 at 11:40:28 AM UTC-4, Robert Dyas wrote:
>
> We have GAE std app that has been running for a coupe of years on java7
> making some https requests out to our cr
We have GAE std app that has been running for a coupe of years on java7
making some https requests out to our credit card processor. Works fine.
When we switched to java8 runtime those same https requests are getting a
400 response code from the credit card processor.
Any ideas as to what
Now that GAE Std Java 8 is in beta, is there any update on when this might
become available for testing?
On Wednesday, January 4, 2017 at 1:25:40 PM UTC-5, Lorne Kligerman wrote:
>
> As Adam mentioned, this is only possible right now with the flex. However
> we do know this is a problem and
Still waiting here too.
On Wednesday, June 21, 2017 at 2:45:20 PM UTC-4, David Grant wrote:
>
> Any update on 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,
Since we don't use JDO at all, can I assume just deleting the jdoconfig.xml
file is safe?
App Engine doesn't need it if JDO isn't used, correct?
On Monday, June 5, 2017 at 8:36:39 PM UTC-4, Robert Dyas wrote:
>
> I just upgraded from the Eclipse plugin to Cloud Tools for Eclipse and now
9 PM UTC-4, Robert Dyas wrote:
>
> I just upgraded from the Eclipse plugin to Cloud Tools for Eclipse and now
> my project is a mess.
>
> I did this: https://cloud.google.com/eclipse/docs/converting
>
> I now have a ton of bad imports... for example I have ton of
>
Thanks - that did help a lot. I thought I already tried that but I
mistakenly added Google API Libraries not Google App Engine.
Now I have some other issues... in my web.xml it doesn't like the following
section because com.google.api.server.spi.SystemServiceServlet still can't
be resolved.
I just upgraded from the Eclipse plugin to Cloud Tools for Eclipse and now
my project is a mess.
I did this: https://cloud.google.com/eclipse/docs/converting
I now have a ton of bad imports... for example I have ton of
com.google.appengine.api.datastore references that are now broken.
What
We've seen very short lived (works on retry) intermittent problems on GAE
std today.
Anybody else?
--
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
-4, Lorne Kligerman wrote:
>
> More details to come, however we will provide a mechanism to be sure that
> only your App Engine app can connect to your own GCE VMs.
>
> On Mon, Apr 24, 2017 at 1:41 PM, Robert Dyas <rober...@parasql.com
> > wrote:
>
>> Question: wi
, April 22, 2017 at 7:15:31 AM UTC-7, Robert Dyas wrote:
>>
>> Yep, that helps. Thank you. I also bet that if you ran a test connecting
>> over a 7 day period you would see lots of times where that ~200-400ms
>> becomes ~1,000 to ~2,000+ms. When I run this same test machine-2-
uld the Compute Engine instances also be scaled?
>>- What solutions have you tried? Any of the ones posted above?
>>
>>
>> On Tuesday, April 18, 2017 at 11:32:37 PM UTC-4, Robert Dyas wrote:
>>>
>>> Has there been any progress on this?
>>>
>>>
> I'll be sure to send a note here. Stay tuned!
>
> Cheers,
> Lorne.
> Product Manager - App Engine
>
> On Saturday, April 22, 2017 at 7:15:31 AM UTC-7, Robert Dyas wrote:
>>
>> Yep, that helps. Thank you. I also bet that if you ran a test connecting
>>
e TLS handshake (I'm
> guessing this adds ~50 ms, looking at the traces).
>
> Hope that helps!
>
>
>
> On Friday, April 21, 2017 at 5:56:55 PM UTC-4, Robert Dyas wrote:
>>
>> Do you have any idea how much slower creating a new connection is? This
>> is probably o
ience with JDBC on App Engine standard, so I can't really
> help there.
>
> Good luck,
>
> Evan
>
>
> On Wednesday, April 19, 2017 at 2:50:28 PM UTC-4, Robert Dyas wrote:
>>
>> I need to connect App Engine Std (AES) to GCE via an internal IP address.
>&g
I need to connect App Engine Std (AES) to GCE via an internal IP address.
- Would GAE being issuing request and GCE, responses? The other way
around? Both?
- AES would issue the requests only
- Are requests and responses tightly coupled like HTTP
requests/responses or more
Has there been any progress on this?
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
Being able to have App Engine standard access my GCE instances via their
internal IP addresses would help us greatly. Hopefully this will also solve
some of the speed/latency issues between App Engine standard and GCE
resources.
On Wednesday, January 4, 2017 at 1:25:40 PM UTC-5, Lorne
The docs say "You can use sockets to connect Google App Engine apps to
Google Compute Engine instances."
Is the limitation still that it can't communicate on the same network and
must go through the external IP of the compute engine instance?
Can app engine Felxible connect to the internal ip
://stackoverflow.com/questions/33902417/google-managed-vm-error-app-engine-service-account-has-insufficient-permissions/33923292#33923292
On Wednesday, November 25, 2015 at 3:42:16 PM UTC-5, Robert Dyas wrote:
>
> When I try to deploy a Managed VM I get this error:
>
> App Engine service
-
What did you find most difficult about the first-time user experience? Where
did you get stuck?
No so much the first time experience, but the follow on experience if
you ever run into a problem (often a security glitch, like when an App
Engine service account goes
Also, just wanted to reiterate points 3 and 4 from Karl's earlier post:
3. Stack Overflow - the whole notion of pushing all of the questions from
> this mailing list to stack overflow is really off putting to me. I
> understand what you are trying to do but a) stack overflow seems to be
>
Can I +100 this?
On Monday, April 20, 2015 at 11:44:58 AM UTC-4, Karl MacMillan wrote:
>
> Katie,
>
> I feel compelled to point out that how this discussion going is a good
> example of some of the things that I - and it seems others - are frustrated
> about. You’ve asked for and received
at tool you use
> for upload.
>
> Cheers!
>
> On Wednesday, November 25, 2015 at 3:42:16 PM UTC-5, Robert Dyas wrote:
>>
>> When I try to deploy a Managed VM I get this error:
>>
>> App Engine service account has insufficient permissions for p
When I try to deploy a Managed VM I get this error:
App Engine service account has insufficient permissions for project
Any suggestions on what to look at to fix this?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from
When I edit my .xml file to include the requisite settings to deploy my app
engine app as a managed vm, I get this error:
App Engine service account has insufficient permissions for project.
Developer or owner required. Version: 30.388785162679429162
Rolling back the update.
Project is
Also When I try to do a deploy via gcloud (instead of Eclipse) I get an
internal error.
--
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
37 matches
Mail list logo
