Thank you for the clarification. I have successfully connected to the same compute engine via both flexible environment and my own development machine. Therefore, I do not think that the issue lies on the firewall on my compute engine as the rest do not face the issue at all.
On Sunday, 1 July 2018 01:58:55 UTC+8, Jason Collins wrote: > > Hi Brian - if your question is about Node.js on App Engine Standard: > currently you cannot connect to private Compute Engine IP addresses, though > this is something we're working on (sorry, no timeline, I just want to let > you know it's on our radar). You should be able to connect to a public IP > address just fine. I've not done this with Mongo specifically, but I have > with Redis running on Compute Engine. > > Perhaps your Compute Engine firewall is preventing the connection? > > > On Thursday, 28 June 2018 07:12:14 UTC-6, BRIJQ Brian Oh wrote: >> >> I am coming from NodeJs App Engine Flexible Environment and we do know >> that the burning issue with this configuration is the price. >> As most of us do not really require the amount of minimum size of >> resources and instances CPU power in flexible environment, I believe that >> it does not really suit us. >> >> As a result, I did the switch over to standard environment as I >> understand that it is still in beta version. >> >> The following are the two concerns and question I have, >> >> 1. Networking ports aren really able to be set by us? >> 2. We cannot connect to our other instances for example in compute engine >> via our private Ip-address used within Google Cloud Platform. (For example >> connection with other databases servers) >> >> A little more information to point 2, the concern is that I have been >> trying to connect to my MongoDB database that is being hosted in Compute >> Engine. All the while, it have been communicating via the internal private >> ip-address across GCP. That is a very good feature and we do know that. >> It have been working well with Flexible Environment. >> >> However, the moment that I launch it over to standard environment, it >> stopped working. As a result, I tried to connect via public ip-address and >> it stills fails to work. >> >> Please note that the application and same configurations to the same >> mongodb server on compute engine connection have been successfully >> establish using my own development machine with the same nodejs8 version >> and similar environment based on the standard environment. >> >> 1. Development Machine on my Mac (public ipaddress) >> 2. App Engine Flexible Environment (public and internal IP address) >> >> All have been successful. >> >> However both ways failed in standard environment. >> >> Does anyone have or faces the same issue? >> >> Please advise >> >> Thank you 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/7f0e7107-996c-462f-9253-86bed818d92d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.