Hello Ridha, If you are using GAE standard environment the behavior you have observed is expected because the app is deployed in a sandbox and doesn't use GCE network. Moreover, you can cannot choose the network when deploying the standard app. The only option to connect your GAE standard app to GCE is using external IP.
With that said, you can deploy your app using GAE flexible environment which give you an option to choose the network for your app. You need to make sure your GCE Redis VM and flex app are in the same network in order to use the internal IP to connect. For more information you can refer to network setting <https://cloud.google.com/appengine/docs/flexible/python/configuring-your-app-with-app-yaml#network_settings> in app.yaml for GAE python flexible environment. I hope that helps. Faizan On Wednesday, August 9, 2017 at 5:52:21 AM UTC-4, Ridha El Bekri wrote: > > Hello Faizen, > > Thank you for your answer. I did already did put in place a firewall rule > but I didn't think about going with a test from another GCE instance. But > talking about the connexion to Redis, I 'm not using a GAE flex app but a > GAE standard python app ! Does that change anything ? > > Le mercredi 9 août 2017 01:32:46 UTC+2, Faizan (Cloud Platform Support) a > écrit : >> >> Hello Ridha, >> >> Make sure you have GCE firewall rules configured to allow traffic on port >> 6379 for internal IP. As a test can you try to connect to the Redis server >> from another GCE VM using internal IP? Can you provide me with the steps >> you use to connect to Redis VM from GAE flex app? >> >> Faizan >> >> On Tuesday, August 8, 2017 at 4:53:50 AM UTC-4, Ridha El Bekri wrote: >>> >>> Hi Yannick, thank you for your answer. We didn't go with the Redis Lab >>> Cloud because we dont want to have our Redis exposed to the internet but >>> profit from the "internal network" of the google cloud solutions. We could >>> just go with the external IP of the GCE instance of redis we have, it would >>> be almost the same thing than the Redis Lab Cloud solution and we got that >>> working already with the external IP but its not what we want :/ >>> >>> Le lundi 7 août 2017 18:33:19 UTC+2, Yannick (Cloud Platform Support) a >>> écrit : >>>> >>>> Hello Ridha, have you tried configuring your App Engine application >>>> according to our guide on using Redis with App Engine Flexible >>>> <https://cloud.google.com/appengine/docs/flexible/python/using-redislabs-redis> >>>> ? >>>> >>>> On Monday, August 7, 2017 at 11:12:58 AM UTC-4, Ridha El Bekri wrote: >>>>> >>>>> Hi there, >>>>> >>>>> I dont know know if I'm searching for the solution in the right place >>>>> so please pardon me if I'm not. >>>>> >>>>> I'm deploying Redis on with Google Compute Engine (GCE) through the >>>>> Cloud Launcher of Google. I'm needing the Redis solution to do some >>>>> "sensitive" work for my Google App Engine (GAE) service (a python backend >>>>> service). >>>>> >>>>> I need my GAE service to communicate with redis through the internal >>>>> IP of the GCE instance. They are of course on the same network and >>>>> sub-network and region. >>>>> >>>>> I get a beautiful : " ConnectionError: Error 13 connecting >>>>> someIP:6379. Permission denied. " whenever I try to run commands on redis >>>>> through my service and through the internal IP. It runs fine on the >>>>> external IP of the GCE instance. >>>>> Redis is running with a default config file >>>>> >>>>> If you have any ideas I would be glad to try. >>>>> 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 post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/74684b65-b2b3-497a-99f5-013ac6183346%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
